Remote MCP · Endpoint

x402 Doctor MCP server

No. x402 Doctor answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://x402-doctor.fizzl.eu/mcp

The last check completed an MCP handshake.

Registry name
io.github.Fizzl13/x402-doctor
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
153 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Is this x402/MPP API safe to pay? $0.001 preflight, fixes, a $0.25 test purchase. Free quick check.
Listing
From the official MCP registry (active).
Recent checks of x402 Doctor
CheckedResultHandshake
6 hours agoHandshake completed153 ms
2 days agoHandshake completed141 ms
4 days agoHandshake completed142 ms
6 days agoHandshake completed149 ms
8 days agoHandshake completed136 ms
10 days agoHandshake completed250 ms
12 days agoHandshake completed128 ms
13 days agoHandshake completed301 ms
14 days agoHandshake completed123 ms
15 days agoHandshake completed268 ms
18 days agoHandshake completed279 ms
20 days agoHandshake completed107 ms
21 days agoHandshake completed124 ms
22 days agoHandshake completed124 ms

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

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