Remote MCP · Endpoint

WebRead MCP server

No. WebRead answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.youraitools.co/webread/mcp

The last check completed an MCP handshake.

Registry name
co.youraitools/webread
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
315 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Turn any public web page into clean Markdown for LLMs; respects robots.txt. By Crypto Money Maker
Listing
From the official MCP registry (active).
Recent checks of WebRead
CheckedResultHandshake
1 hour agoHandshake completed315 ms
3 days agoHandshake completed60 ms
12 days agoHandshake completed312 ms
13 days agoHandshake completed116 ms
15 days agoHandshake completed130 ms
15 days agoHandshake completed80 ms
17 days agoHandshake completed155 ms
18 days agoHandshake completed59 ms
18 days agoHandshake completed248 ms
20 days agoHandshake completed244 ms
22 days agoHandshake completed162 ms
25 days agoHandshake completed188 ms
27 days agoHandshake completed168 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.