mcpbeat Sign in

Agent Readiness MCP Server

by webmcp-tool Your server? Claim it
not responding

Agent Readiness is listed as active in the registry but did not answer our last check. It exposes 5 tools.

Scores any public website on how usable it is by AI agents, with per-check evidence.

Uptime history 67 days of history · worst day 0%
67 days agonow
0.0%
Uptime 24h
0 of 91 checks
5
Tools
read from the server
10178 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 10

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 September 2026. No other catalogue keeps this.

1 Oct 5 tool descriptions were rewritten explain_check, get_badge_embed, list_checks and 2 more
25 Sep 2 tool descriptions were rewritten score_site, watch_site
25 Sep a tool changed the parameters it asks for watch_site
8 Sep a tool appeared get_agent_stats
8 Sep a tool disappeared get_agent_stats

Agent Readiness does not always answer

Over the last week it answered 49.2% 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 12 min ago.

run in your terminal
claude mcp add agent-readiness --transport http https://webmcp-tool.com/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://webmcp-tool.com/api/mcp
~/.codex/config.toml
[mcp_servers.agent-readiness]
url = "https://webmcp-tool.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agent-readiness": {
      "url": "https://webmcp-tool.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "agent-readiness": {
      "type": "http",
      "url": "https://webmcp-tool.com/api/mcp"
    }
  }
}

Available tools 5

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

badge
get_badge_embed
Use this when the user wants to show a site's Agent Readiness badge on that site. Scores the site if needed, then returns the HTML snippet for sites at grade C or better (bronze, silver or gold), or the reason and the first fixes when the site is not eligible. Returns HTML to paste; it installs nothing and runs no script.
checks
list_checks
Use this when the user asks what the Agent Readiness Score measures or how it is calculated, rather than how one site performs. Lists every check in the rule set with its pillar, weight and question. Fetches nothing.
explain
explain_check
Use this when the user asks what a specific Agent Readiness finding means, why it matters to AI agents or how to fix it, usually after score_site. Explains one check: what it asks, why an agent cares, how it is weighted and how to fix it, with a code snippet where one exists. Answers from the rule set only and fetches nothing.
score
score_site
Use this when the user asks whether a website is ready for AI agents, agent-ready, AI-agent friendly or WebMCP-ready, or what to fix so agents can use it. Scores one public website out of 100 for agent readiness and returns a grade, the fitness and adoption sub-scores, the five highest-value fixes, the scan time and whether the result came from cache. Reads one public page plus standard discovery files (robots.txt, /.well-known endpoints, sitemaps, llms.txt) and up to ten same-origin script bundles; it never logs in, submits forms or changes the site. Results are cached for about an hour.
watch
watch_site
Use this only when the user explicitly asks to be emailed when a site's Agent Readiness Score changes. Sends a confirmation email for monitoring that site. Use only when the user explicitly asks to receive a confirmation email for monitoring at the supplied address. Set sendConfirmationEmail to true only then. Monitoring starts only after the recipient opens the link and confirms on the page; this call itself sends one email.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

get_agent_stats
removed 8 Sep 2026

Endpoints

URLTransportStateLatencyChecked
https://webmcp-tool.com/api/mcp streamable-http answering 10178 ms 12 min ago

Alternatives to Agent Readiness

same job, measured the same way
AgenticWebScore
by agenticwebscore

Scan a public website for AI agent readiness: 60 checks, a score, and the evidence for each.

4 tools answering
UXMachine
by qtorb

Website checker for AI coding agents. Measures your site in a real browser, with evidence.

answering
Agent Ready Report
by agenticplug

Scan any public website and see how ready it is for AI agents and AI search, explained plainly.

2 tools answering
Open for Agents Website Visibility
by mdotk

Check how well AI agents can discover and understand a public website.

answering
Tuper Site Check
by tuper

Check a website in a real browser, or check if AI agents can use it: score, problems, report link.

3 tools answering
Semanto by Trooth
by trooth

Set up, sign, publish and check Semanto, a company's signed website file for AI agents.

16 tools answering
Bench Agent Discovery
by virajmishra1

Discover public AI agents, reusable recipes, and trusted benchmark evidence by task.

3 tools answering
O
Omega Router
by gbacot-wq

Route agent services by observed price and public usage evidence.

3 tools answering

Agent Readiness — questions

Answers built from our own checks of this server.

What can Agent Readiness do?
It exposes 5 tools, read directly from the server on our last check. Among them: explain_check, get_badge_embed, list_checks, score_site, watch_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 Readiness working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 10178 ms. The bar chart above shows every period we have measured.
Did Agent Readiness ever remove tools?
Yes. get_agent_stats is no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
The registry lists Agent Readiness 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 Readiness?
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 Readiness need an API key?
No. Agent Readiness completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.