Remote MCP · Endpoint

CanAIReadMe MCP server

No. CanAIReadMe answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://canaireadme.netlify.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.juanquiservin/canaireadme
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
270 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Can an AI agent understand and act on a business website? Evidence-based facts, gaps and fixes.
Listing
From the official MCP registry (active).
Recent checks of CanAIReadMe
CheckedResultHandshake
1 hour agoHandshake completed270 ms
2 days agoHandshake completed5.09 s
5 days agoHandshake completed574 ms
7 days agoHandshake completed367 ms
9 days agoHandshake completed1.02 s
11 days agoHandshake completed401 ms
13 days agoHandshake completed485 ms
15 days agoHandshake completed508 ms
17 days agoHandshake completed196 ms
19 days agoHandshake completed139 ms
20 days agoHandshake completed284 ms
21 days agoHandshake completed374 ms
23 days agoHandshake completed134 ms
25 days agoHandshake completed209 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 CanAIReadMe and makes no claim about it beyond what these checks measured.