Remote MCP · Endpoint

x402 Web Tools MCP server

Yes, as of 34 minutes ago: the server returned an HTTP error.

DownLast checked 34 minutes ago

Server URL

https://x402-web-tools.microtools-x402.workers.dev/mcp

The last check failed: the server returned an HTTP error.

Registry name
dev.workers.microtools-x402.x402-web-tools/web-tools
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
9 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Web/PDF to Markdown, transcription, paper search and citation checks. Pay per call in USDC via x402.
Listing
From the official MCP registry (active).
Recent checks of x402 Web Tools
CheckedResultHandshake
34 minutes agoFailed - the server returned an HTTP error—
9 days agoHandshake completed918 ms
10 days agoHandshake completed593 ms
11 days agoHandshake completed839 ms
12 days agoHandshake completed581 ms
14 days agoHandshake completed723 ms
14 days agoHandshake completed493 ms
15 days agoHandshake completed1.13 s
17 days agoHandshake completed1.62 s
19 days agoHandshake completed945 ms
21 days agoHandshake completed931 ms
24 days agoHandshake completed914 ms
26 days agoHandshake completed1.40 s

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

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.