Remote MCP · Endpoint

Agent Ready MCP server

No. Agent Ready answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://agentready.sneeze.it/mcp

The last check completed an MCP handshake.

Registry name
it.sneeze.agentready/agent-ready
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
21 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Score any website out of 100 for how well AI agents can find, understand and use it.
Listing
From the official MCP registry (active).
Recent checks of Agent Ready
CheckedResultHandshake
4 days agoHandshake completed21 ms
7 days agoHandshake completed21 ms
16 days agoHandshake completed25 ms
17 days agoHandshake completed29 ms
19 days agoHandshake completed26 ms
19 days agoHandshake completed50 ms
21 days agoHandshake completed20 ms
22 days agoHandshake completed31 ms
22 days agoHandshake completed31 ms
24 days agoHandshake completed20 ms
26 days agoHandshake completed22 ms
29 days agoHandshake completed136 ms

The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 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 Agent Ready and makes no claim about it beyond what these checks measured.