mcpbeat

Agentready MCP Server

io.github.msanchezgrice/agentready
answering

Agentready is answering right now. Last checked 13 min ago. It exposes 3 tools.

Scan any public site for AI-agent visibility; get scored findings, a machine-readable fix pack, and

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
28.6%
Uptime 24h
26 of 91 checks
3
Tools
read from the server
334 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add agentready --transport http https://www.agentready.me/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agentready": {
      "url": "https://www.agentready.me/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.agentready]
url = "https://www.agentready.me/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agentready": {
      "url": "https://www.agentready.me/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "agentready": {
      "url": "https://www.agentready.me/api/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

fix
get_fix_pack
Scan a public URL and return Fix Pack v2: prioritized fixes with stable ids, observed evidence, candidate target URLs and repository paths, review gates, and fix-specific acceptance assertions for a coding agent.
scan
scan_url
Run an AgentReady scan of a public URL. Returns the 0-100 score, per-phase findings, top priorities, and the Fix Pack v2 implementation contract. Repository paths remain candidate targets until a connected-repository resolver proves them.
verify
verify_fixes
Re-scan a public URL and evaluate fix-specific stable ids from a previous v1 or v2 Fix Pack. A fix closes when its finding id is absent; score delta is secondary evidence only.

Endpoints

URLTransportStateLatencyChecked
https://www.agentready.me/api/mcp streamable-http answering 379 ms 13 min ago

Agentready — questions

Answers built from our own checks of this server.

What can Agentready do?
It exposes 3 tools, read directly from the server on our last check. Among them: get_fix_pack, scan_url, verify_fixes. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Agentready working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 26 of 91 checks got a reply (28.6%), average response time 334 ms. The bar chart above shows every period we have measured.
Is Agentready still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Agentready?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Agentready need an API key?
No. Agentready completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agentready?
It answers our handshake in 334 ms on average, which is faster than 42% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.