Remote MCP · Endpoint

AgentReady MCP server

No. AgentReady answered an MCP handshake 29 minutes ago.

UpLast checked 29 minutes ago

Server URL

https://api.youraitools.co/agentready/mcp

The last check completed an MCP handshake.

Registry name
co.youraitools/agentready
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
34 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Is your website ready for AI agents? 0-100 score, A-F grade and fixes. By Crypto Money Maker
Listing
From the official MCP registry (active).
Recent checks of AgentReady
CheckedResultHandshake
29 minutes agoHandshake completed34 ms
3 days agoHandshake completed253 ms
13 days agoHandshake completed244 ms
14 days agoHandshake completed52 ms
15 days agoHandshake completed119 ms
16 days agoHandshake completed87 ms
17 days agoHandshake completed244 ms
18 days agoHandshake completed152 ms
19 days agoHandshake completed155 ms
21 days agoHandshake completed82 ms
22 days agoHandshake completed211 ms
25 days agoHandshake completed383 ms
27 days agoHandshake completed312 ms

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

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