Remote MCP · Endpoint

AgentRead MCP server

Yes, as of 17 hours ago: the server returned an HTTP error.

DownLast checked 17 hours ago

Server URL

https://agentread.omar-cv.workers.dev/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.omarhassanatef/agentread
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
3 tools
Uptime, last 30 days
91.7% from 12 checks
Described by its publisher as
Web pages to clean Markdown for AI agents. 5 free calls/day, then pay per call via x402 on Base.
Listing
From the official MCP registry (active).
Recent checks of AgentRead
CheckedResultHandshake
17 hours agoFailed - the server returned an HTTP error—
11 days agoHandshake completed296 ms
12 days agoHandshake completed233 ms
12 days agoHandshake completed301 ms
14 days agoHandshake completed296 ms
15 days agoHandshake completed247 ms
16 days agoHandshake completed222 ms
17 days agoHandshake completed184 ms
18 days agoHandshake completed404 ms
20 days agoHandshake completed501 ms
22 days agoHandshake completed169 ms
25 days agoHandshake completed320 ms

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

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 AgentRead and makes no claim about it beyond what these checks measured.