Remote MCP · Endpoint

AgentRead — bounded web context MCP server

No. AgentRead — bounded web context answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://agentread-json-api.army20160422.chatgpt.site/agent/mcp

The last check completed an MCP handshake.

Registry name
site.chatgpt.army20160422.agentread-json-api/agentread
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
263 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Free HTML parsing; static web context at 0.01 USDC via x402. Paid reads need a wallet adapter.
Listing
From the official MCP registry (active).
Recent checks of AgentRead — bounded web context
CheckedResultHandshake
2 days agoHandshake completed263 ms
3 days agoHandshake completed958 ms
3 days agoHandshake completed170 ms
5 days agoHandshake completed816 ms
6 days agoHandshake completed956 ms
7 days agoHandshake completed129 ms
8 days agoHandshake completed237 ms
9 days agoHandshake completed1.12 s
11 days agoHandshake completed262 ms
13 days agoHandshake completed232 ms
16 days agoHandshake completed1.17 s
18 days agoHandshake completed126 ms
20 days agoHandshake completed1.06 s
22 days agoHandshake completed947 ms
24 days agoHandshake completed904 ms
26 days agoHandshake completed782 ms
28 days agoHandshake completed1.10 s
30 days agoHandshake completed214 ms
31 days agoHandshake completed958 ms

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

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