Remote MCP · Endpoint

io.github.puluceno/agentready MCP server

No. io.github.puluceno/agentready answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agentready.agentready.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.puluceno/agentready
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
210 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Can ChatGPT, Claude and Perplexity reach and read a website? Score, problems found and fixes.
Listing
From the official MCP registry (active).
Recent checks of io.github.puluceno/agentready
CheckedResultHandshake
1 hour agoHandshake completed210 ms
2 days agoHandshake completed436 ms
4 days agoHandshake completed132 ms
7 days agoHandshake completed99 ms
9 days agoHandshake completed128 ms
11 days agoHandshake completed103 ms
13 days agoHandshake completed136 ms
15 days agoHandshake completed77 ms
16 days agoHandshake completed130 ms
18 days agoHandshake completed154 ms
19 days agoHandshake completed450 ms
20 days agoHandshake completed175 ms
23 days agoHandshake completed119 ms
24 days agoHandshake completed118 ms

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

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 io.github.puluceno/agentready and makes no claim about it beyond what these checks measured.