Remote MCP · Endpoint

x402-snap MCP server

No. x402-snap answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://x402-snap.zaden-gaming.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.ZadenGG/x402-snap
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
105 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Pay-per-call browser rendering and x402 marketplace ranking for AI agents, billed via USDC.
Listing
From the official MCP registry (active).
Recent checks of x402-snap
CheckedResultHandshake
1 hour agoHandshake completed105 ms
9 days agoHandshake completed228 ms
10 days agoHandshake completed118 ms
11 days agoHandshake completed180 ms
12 days agoHandshake completed206 ms
14 days agoHandshake completed110 ms
14 days agoHandshake completed244 ms
15 days agoHandshake completed107 ms
17 days agoHandshake completed145 ms
19 days agoHandshake completed157 ms
21 days agoHandshake completed148 ms
24 days agoHandshake completed144 ms
26 days agoHandshake completed154 ms
28 days agoHandshake completed126 ms

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

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 x402-snap and makes no claim about it beyond what these checks measured.