Discover / tempo-name-resolver.vercel.app
Tempo Name Resolver
■ Challenge detectedA service whose listing advertises MPP on Tempo, in USDC.
- Challenge detected
- 3 of the last 3 checks
- Median response
- 973 ms
- Last checked
- 9 Oct, 18:22 UTC
- In our index since
- 7 Oct 2026
Endpoint
curl -i https://tempo-name-resolver.vercel.app/api/reverse # 402 Payment Required: pay with a MPP client, then send the request again.
Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/tempo-name-resolver.vercel.app
Recent checks
7 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.9 Oct 2026
All 3 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 9 Oct, 18:22 UTC | Challenge detected | 402 | 973ms |
| 8 Oct, 09:20 UTC | Challenge detected | 402 | 915ms |
| 7 Oct, 00:22 UTC | Challenge detected | 402 | 993ms |
Questions
Did our last probe detect a payment challenge?
At our last probe on 9 Oct, 18:22 UTC, it returned HTTP 402 or another detected payment-challenge signal. This check did not test payment, delivery or compatibility with the Superstables client.
What payment terms does Tempo Name Resolver advertise?
The listing advertises MPP, Tempo and USDC. Check the seller's current payment challenge and authentication requirements before paying.
Where is Tempo Name Resolver listed?
In mppscan. Superstables first indexed it on 7 Oct 2026.
Something wrong on this page? Tell us.