Remote MCP · Endpoint

x402 Web Tools MCP server

No. x402 Web Tools answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://x402-web-tools.onrender.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.iparadise71/x402-web-tools
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
140 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Pay-per-call tools for agents: web page to Markdown, tech stack, email domain check (x402 USDC)
Listing
From the official MCP registry (active).
Recent checks of x402 Web Tools
CheckedResultHandshake
2 hours agoHandshake completed140 ms
1 day agoHandshake completed257 ms
4 days agoHandshake completed132 ms
6 days agoHandshake completed300 ms
8 days agoHandshake completed138 ms
9 days agoHandshake completed140 ms
10 days agoHandshake completed301 ms
11 days agoHandshake completed121 ms
13 days agoHandshake completed255 ms
16 days agoHandshake completed138 ms
17 days agoHandshake completed251 ms
19 days agoHandshake completed144 ms
20 days agoHandshake completed123 ms
21 days agoHandshake completed258 ms
22 days agoHandshake completed131 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 Web Tools and makes no claim about it beyond what these checks measured.