Remote MCP · Endpoint

io.github.89rat/x402-checks MCP server

No. io.github.89rat/x402-checks answered an MCP handshake 54 minutes ago.

UpLast checked 54 minutes ago

Server URL

https://api.code402.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.89rat/x402-checks
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
224 ms
Tools exposed
24 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Machine-payable deterministic identifier checks + signed XDR-1 receipts for agents.
Listing
From the official MCP registry (active).
Recent checks of io.github.89rat/x402-checks
CheckedResultHandshake
54 minutes agoHandshake completed224 ms
1 day agoHandshake completed421 ms
2 days agoHandshake completed210 ms

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

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 io.github.89rat/x402-checks and makes no claim about it beyond what these checks measured.