Remote MCP · Endpoint

WebRead MCP server

No. WebRead answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://webread.agentgate.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.agentgate-builder/x402-url-to-markdown
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
174 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read any public web page as clean Markdown for LLMs. Respects robots.txt. Free tier; x402 paid API.
Listing
From the official MCP registry (active).
Recent checks of WebRead
CheckedResultHandshake
44 minutes agoHandshake completed174 ms
3 days agoHandshake completed167 ms
12 days agoHandshake completed387 ms
13 days agoHandshake completed73 ms
14 days agoHandshake completed174 ms
15 days agoHandshake completed182 ms
16 days agoHandshake completed162 ms
17 days agoHandshake completed195 ms
18 days agoHandshake completed279 ms
19 days agoHandshake completed413 ms
22 days agoHandshake completed262 ms
25 days agoHandshake completed121 ms
27 days agoHandshake completed236 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 WebRead and makes no claim about it beyond what these checks measured.