Remote MCP · Endpoint

io.github.scrape402/scrape402 MCP server

Yes, as of 1 hour ago: the hostname does not resolve.

DownLast checked 1 hour ago

Server URL

https://x402.shizu.me/mcp/rpc

The last check failed: the hostname does not resolve.

Registry name
io.github.scrape402/scrape402
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
89.5% from 19 checks
Described by its publisher as
Pay-per-call agent tools via x402 (USDC on Base): chat, prices, funding, RNG. No account or keys.
Listing
From the official MCP registry (active).
Recent checks of io.github.scrape402/scrape402
CheckedResultHandshake
1 hour agoFailed - the hostname does not resolve—
1 day agoFailed - the hostname does not resolve—
2 days agoHandshake completed347 ms
3 days agoHandshake completed351 ms
4 days agoHandshake completed356 ms
5 days agoHandshake completed344 ms
6 days agoHandshake completed350 ms
8 days agoHandshake completed331 ms
11 days agoHandshake completed411 ms
13 days agoHandshake completed327 ms
15 days agoHandshake completed345 ms
18 days agoHandshake completed337 ms
20 days agoHandshake completed348 ms
22 days agoHandshake completed327 ms
24 days agoHandshake completed590 ms
26 days agoHandshake completed337 ms
27 days agoHandshake completed338 ms
28 days agoHandshake completed343 ms
29 days agoHandshake completed328 ms

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

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