Remote MCP · Endpoint

io.github.webberdesign/webbersites-x402-data-api MCP server

No. io.github.webberdesign/webbersites-x402-data-api answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://api.webbersites.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.webberdesign/webbersites-x402-data-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
54 ms
Tools exposed
78 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
45 pay-per-call AI agent tools: scraping, SEO, crypto data, lint, agent memory. x402 USDC on Base.
Listing
From the official MCP registry (active).
Recent checks of io.github.webberdesign/webbersites-x402-data-api
CheckedResultHandshake
5 hours agoHandshake completed54 ms
2 days agoHandshake completed184 ms
4 days agoHandshake completed89 ms
5 days agoHandshake completed66 ms
7 days agoHandshake completed56 ms
8 days agoHandshake completed57 ms
9 days agoHandshake completed66 ms
12 days agoHandshake completed50 ms
13 days agoHandshake completed43 ms
15 days agoHandshake completed74 ms
16 days agoHandshake completed42 ms
17 days agoHandshake completed39 ms
18 days agoHandshake completed42 ms
19 days agoHandshake completed40 ms
20 days agoHandshake completed53 ms
21 days agoHandshake completed56 ms
22 days agoHandshake completed46 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.webberdesign/webbersites-x402-data-api and makes no claim about it beyond what these checks measured.