base-rpc-health-map · x402.dailyelo.com
Which Base public RPCs serve a stale chain tip. Every 30s we ask all…
Which Base public RPCs serve a stale chain tip. Every 30s we ask all major public RPCs for eth_blockNumber in parallel and record how many blocks behind the fastest peer each was, plus latency and error rate. An RPC never reports its own lag, so an agent reading a balance from a lagging endpoint cannot tell. Omit ?rpc for the full map; ?rpc=<host> for one.
Input
Sample response
Published by the provider. Your run returns a fresh response.
response5 keys
endpoints1 item
0{ behind_1plus_rate, error, error_rate, … }9 keys
network"eip155:8453"
schema"rpchealth/v1"
updated_at1719500000
window4 keys
endpoints_compared10
hours24
probe_interval_s30
probe_rounds2880
responseobject, 5 keysYour agent can do this on its own
Add the MCP URL in Claude Code, Cursor or Codex. Your agent can run Tools within its spending limits, or ask for approval each time. Connect your agent
Connect your agent
Add one MCP URL and your agent can find and run this tool within its spending limits. Choose “Ask each time” if you want to approve every Call.
MCP URL
https://app.aecon.ai/mcpTerminalbash
In Claude Code, open /mcp, select agentic-economy, then choose Authenticate.
Track record
- Paid calls, last 30 days
- 3
- Buyers, last 30 days
- 1
- Last paid call
Reported by the x402 directory.