Remote MCP · Endpoint

x402 Doctor MCP server

No. x402 Doctor answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://x402-doctor.onrender.com/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
258 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Check x402 endpoints like a paying agent: diagnose, fix plans, pre-payment checks. Free quick check.
Listing
From the official MCP registry (active).
Recent checks of x402 Doctor
CheckedResultHandshake
1 hour agoHandshake completed258 ms
2 days agoHandshake completed270 ms
4 days agoHandshake completed135 ms
6 days agoHandshake completed143 ms
7 days agoHandshake completed125 ms
9 days agoHandshake completed151 ms
10 days agoHandshake completed107 ms
11 days agoHandshake completed780 ms
14 days agoHandshake completed136 ms
15 days agoHandshake completed255 ms
17 days agoHandshake completed257 ms
18 days agoHandshake completed246 ms
20 days agoHandshake completed251 ms
21 days agoHandshake completed130 ms
22 days agoHandshake completed176 ms

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

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.