Remote MCP · Endpoint

Agent Docs MCP server

No. Agent Docs answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://agent-docs-mcp.onrender.com/mcp/

The last check completed an MCP handshake.

Registry name
io.github.KonstantinStarovoytov/agent-docs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
170 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search the official docs of Claude Code, Cursor, OpenAI Codex and MCP, refreshed daily.
Listing
From the official MCP registry (active).
Recent checks of Agent Docs
CheckedResultHandshake
5 hours agoHandshake completed170 ms
9 days agoHandshake completed169 ms
10 days agoHandshake completed191 ms
11 days agoHandshake completed189 ms
12 days agoHandshake completed310 ms
14 days agoHandshake completed176 ms
14 days agoHandshake completed173 ms
15 days agoHandshake completed147 ms
17 days agoHandshake completed339 ms
19 days agoHandshake completed139 ms
21 days agoHandshake completed156 ms
24 days agoHandshake completed318 ms
26 days agoHandshake completed311 ms
28 days agoHandshake completed328 ms

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

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