Remote MCP · Endpoint
read_url MCP server
No. read_url answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://mm-read-url.pradooskee.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.workers.pradooskee.mm-read-url/read-url
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 206 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- One public web page as clean markdown, with title, language and a SHA-256. Obeys robots.txt.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 206 ms |
| 1 day ago | Handshake completed | 441 ms |
| 2 days ago | Handshake completed | 183 ms |
| 3 days ago | Handshake completed | 217 ms |
| 4 days ago | Handshake completed | 145 ms |
| 5 days ago | Handshake completed | 218 ms |
| 6 days ago | Handshake completed | 591 ms |
| 8 days ago | Handshake completed | 341 ms |
| 11 days ago | Handshake completed | 176 ms |
| 13 days ago | Handshake completed | 192 ms |
| 15 days ago | Handshake completed | 221 ms |
| 18 days ago | Handshake completed | 198 ms |
| 20 days ago | Handshake completed | 364 ms |
| 22 days ago | Handshake completed | 171 ms |
| 24 days ago | Handshake completed | 195 ms |
| 26 days ago | Handshake completed | 435 ms |
| 27 days ago | Handshake completed | 205 ms |
| 29 days ago | Handshake completed | 549 ms |
| 30 days ago | Handshake completed | 378 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 read_url and makes no claim about it beyond what these checks measured.