Remote MCP · Endpoint

Web Intel (x402) MCP server

No. Web Intel (x402) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://web-intel-x402.x402-web-intel-api.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.mcpspro/web-intel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
284 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Pay-per-call web extraction, SEO audits and text analysis. USDC on Base via x402, no API keys.
Listing
From the official MCP registry (active).
Recent checks of Web Intel (x402)
CheckedResultHandshake
1 hour agoHandshake completed284 ms
9 days agoHandshake completed276 ms
10 days agoHandshake completed338 ms
11 days agoHandshake completed194 ms
12 days agoHandshake completed218 ms
14 days agoHandshake completed209 ms
14 days agoHandshake completed252 ms
15 days agoHandshake completed282 ms
17 days agoHandshake completed316 ms
19 days agoHandshake completed542 ms
21 days agoHandshake completed531 ms
24 days agoHandshake completed453 ms
26 days agoHandshake completed309 ms
28 days agoHandshake completed211 ms

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

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 Web Intel (x402) and makes no claim about it beyond what these checks measured.