Remote MCP · Endpoint

io.github.digitalweb33333-creator/x402-endpoints MCP server

No. io.github.digitalweb33333-creator/x402-endpoints answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://x402-endpoints.onrender.com/mcp/

The last check completed an MCP handshake.

Registry name
io.github.digitalweb33333-creator/x402-endpoints
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
163 ms
Tools exposed
52 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
x402 paid API tools for AI agents on Base: EU/global registries, crypto, wallet & agent trust.
Listing
From the official MCP registry (active).
Recent checks of io.github.digitalweb33333-creator/x402-endpoints
CheckedResultHandshake
2 hours agoHandshake completed163 ms
2 days agoHandshake completed255 ms
4 days agoHandshake completed156 ms
5 days agoHandshake completed154 ms
7 days agoHandshake completed320 ms
8 days agoHandshake completed300 ms
9 days agoHandshake completed310 ms
12 days agoHandshake completed159 ms
13 days agoHandshake completed156 ms
15 days agoHandshake completed396 ms
17 days agoHandshake completed315 ms
18 days agoHandshake completed305 ms
19 days agoHandshake completed146 ms
20 days agoHandshake completed139 ms
20 days agoHandshake completed303 ms
21 days agoHandshake completed135 ms
23 days agoHandshake completed310 ms

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

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