mcpbeat Sign in

Agent Ready MCP Server

not responding

Agent Ready is listed as active in the registry but did not answer our last check. 113 installs a week from npm. It exposes 3 tools. Last commit 7 Sep 2026.

Scan any URL for AI agent readability — Vercel Spec, llmstxt.org, and agent-protocol manifests.

Installs per day peak 40 · avg 16 · +17% w/w
a month agotoday
Uptime history 91 days of history · worst day 0%
91 days agonow
1.1%
Uptime 24h
1 of 91 checks
3
Tools
read from the server
319 ms
Response time
average over 24h
113
Installs / week
npm and PyPI

Agent Ready does not always answer

Over the last week it answered 0.6% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

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 agent-ready-mcp --transport http https://agent-ready.dev/api/v1/mcp
Settings → Connectors → Add custom connector, then paste this address
https://agent-ready.dev/api/v1/mcp
~/.codex/config.toml
[mcp_servers.agent-ready-mcp]
url = "https://agent-ready.dev/api/v1/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agent-ready-mcp": {
      "url": "https://agent-ready.dev/api/v1/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "agent-ready-mcp": {
      "type": "http",
      "url": "https://agent-ready.dev/api/v1/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.

scan
get_scan
Fetches a completed or in-progress scan by its id. Only scans owned by the authenticated API key's user are returned.
scan_site
Runs the agent-ready.dev scanner against a URL and returns structured results: Vercel score, llmstxt.org score, and per-check findings with remediation hints. Scans may take up to ~60s; for larger scans the tool returns a scan id and asks you to poll with get_scan.
ask
ask
Natural-language search (NLWeb /ask) over Agent Ready's own content — scoring methodology, the check registry, the specs it validates, and the content library (explainers, comparisons, how-to guides, glossary). Returns Schema.org-typed result objects. Optional itemType narrows to a corpus type; mode 'summarize' adds an extractive summary.

Endpoints

URLTransportStateLatencyChecked
https://agent-ready.dev/api/v1/mcp streamable-http answering 77 ms 13 min ago

Alternatives to Agent Ready

same job, measured the same way
Onto
by ravixalgorithm

Clean Markdown and AI-readability scoring for any URL. Built for AI agents.

86 installs/wk answering
AgentGrade
by agentgrade

Scan any website for AI agent readiness, payment protocols, and discovery endpoints

4 tools answering
Junto MCP
by vrllrv

The payment protocol for people and agents. One MCP server, any payment rail.

51 installs/wk local only
Manifestlens
by cloudcorprecords

Agent Manifest Protocol: fetch, validate and permission-check API manifests; registry submissions.

349 installs/wk local only
CodaURL
by codaurl

URL monitoring for AI agents: manage monitors and read status and incidents. Free or Pro account.

answering
Fastcrawl
by fastcrawl

Cloud scraping & crawling API for AI agents. Turn any URL into clean, LLM-ready markdown.

answering
Accessibility Scanner MCP
by bishop81

Scan any URL for WCAG accessibility issues (axe-core) and get per-element fixes for an AI agent.

92 installs/wk local only
Agent Readiness Auditor
by asish-singh

Audits any website for AI agent readiness and safety, scoring prompt injection risk and llms.txt.

74 installs/wk local only

Agent Ready — questions

Answers built from our own checks of this server.

What can Agent Ready do?
It exposes 3 tools, read directly from the server on our last check. Among them: ask, get_scan, scan_site. 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 Agent Ready working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 1 of 91 checks got a reply (1.1%), average response time 319 ms. The bar chart above shows every period we have measured.
The registry lists Agent Ready as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Agent Ready?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Agent Ready need an API key?
No. Agent Ready 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 Agent Ready?
It answers our handshake in 319 ms on average, which is faster than 44% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Agent Ready?
The npm package agent-ready-mcp was installed 113 times in the last week. Week over week that is +17%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Agent Ready open source?
The code is open source: it is published under the MIT licence, written in TypeScript and 2 stars on GitHub. The licence covers the code in the repository, not the hosted service at agent-ready.dev, which runs on its operator's own terms.