Remote MCP · Endpoint

USDC & RPC Reference (free) MCP server

Yes, as of 2 days ago: the server returned an HTTP error.

DownLast checked 2 days ago

Server URL

https://x402-preflight-grokbot.netlify.app/mcp

The last check failed: the server returned an HTTP error.

Registry name
app.netlify.x402-preflight-grokbot/usdc-rpc-reference
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
3 tools
Uptime, last 30 days
80.0% from 10 checks
Described by its publisher as
Free read-only data: verified USDC addresses and EIP-712 domains, measured RPC eth_getLogs limits.
Listing
From the official MCP registry (active).
Recent checks of USDC & RPC Reference (free)
CheckedResultHandshake
2 days agoFailed - the server returned an HTTP error—
6 days agoFailed - the server returned an HTTP error—
16 days agoHandshake completed137 ms
17 days agoHandshake completed110 ms
18 days agoHandshake completed134 ms
19 days agoHandshake completed778 ms
21 days agoHandshake completed92 ms
21 days agoHandshake completed194 ms
22 days agoHandshake completed220 ms
23 days agoHandshake completed147 ms

The last 10 checks. Full history is kept for 30 days; the all-time counter stands at 8 responding of 10.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with USDC & RPC Reference (free) and makes no claim about it beyond what these checks measured.