Discover / rpc.tempo.xyz
Tempo RPC
□ No challenge detectedTempo blockchain JSON-RPC access (mainnet and testnet).
- Challenge detected
- 0 of the last 9 checks
- Last checked
- 17 Oct, 09:26 UTC
- In our index since
- 26 Sept 2026
Endpoint
curl -i https://rpc.tempo.xyz # 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/rpc.tempo.xyz
Recent checks
4 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.17 Oct 2026
All 9 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 17 Oct, 09:26 UTC | No challenge detected | 400 | 144ms |
| 16 Oct, 08:13 UTC | No challenge detected | 400 | 40ms |
| 14 Oct, 19:26 UTC | No challenge detected | 400 | 128ms |
| 12 Oct, 22:31 UTC | No challenge detected | 400 | 74ms |
| 11 Oct, 00:15 UTC | No challenge detected | 400 | 90ms |
| 9 Oct, 15:32 UTC | No challenge detected | 400 | 79ms |
| 8 Oct, 09:33 UTC | No challenge detected | 400 | 42ms |
| 7 Oct, 03:32 UTC | No challenge detected | 400 | 414ms |
| 4 Oct, 17:05 UTC | No challenge detected | 400 | 27ms |
Questions
Did our last probe detect a payment challenge?
No. At our last probe on 17 Oct, 09:26 UTC, we detected no payment challenge.
What payment terms does Tempo RPC advertise?
The listing advertises MPP, Tempo and USDC. It names stripe as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.
Where is Tempo RPC listed?
In mpp.dev. Superstables first indexed it on 26 Sept 2026.
Something wrong on this page? Tell us.