The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Agent Ready MCP listing page.
MCP server for Agent Ready — scan any URL for AI agent readability against the Vercel Agent Readability Spec, the llmstxt.org standard, and agent-protocol manifests (MCP server cards, A2A, agents.json, agent-permissions.json, UCP, x402, NLWeb). 72 checks across four spec families — 40 site and page checks (15 site-wide + 25 per-page), 10 against llmstxt.org, and 22 against agent-protocol manifests — each with per-check fix guidance, plus a separate accessibility sub-score from 23 WCAG 2.2 / layout-stability checks.
Hosted at https://agent-ready.dev/api/v1/mcp (Streamable HTTP); this package is a thin stdio wrapper around the same REST endpoints, distributed via npm for local MCP clients (Claude Desktop, Claude Code, Cursor, VS Code, Windsurf).
scan_site — fresh agent-readability scan on any URL. Works without a key on the anonymous free tier (3 scans/30 days per IP, 25-page depth, synchronous); with a Pro key it scans up to 250 pages, polling the hosted API up to 60s.get_scan — fetch a previously-run scan by id (Pro key required — scan history is account-scoped).ask — natural-language (NLWeb) search over Agent Ready's own methodology, checks, and specs. Public, no API key required; returns Schema.org-typed results.validate_structured_data — validate a page's (or a pasted) JSON-LD against Agent Ready's structured-data checks. Public, no API key required; paste mode needs no network, so an agent can check JSON-LD it just authored.scan, interpret_scan, remediation_plan. End-to-end workflows from URL → score → fix-it plan.SKILL.md — Claude Skill descriptor included under skills/agent-ready/ for activation routing.No key is required to start: scan_site, ask, and validate_structured_data all work anonymously out of the box (scan_site on the free anonymous quota — 3 scans per 30 days per IP at 25-page depth). An Agent Ready Pro API key unlocks 50 scans/month, 250-page depth, scan history (get_scan), and weekly monitoring — sign up at agent-ready.dev and issue a key from the dashboard. The env block in the configs below is optional; omit it to run keyless.
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
.cursor/mcp.json, .vscode/mcp.json, or ~/.codeium/windsurf/mcp_config.json:
| Variable | Required | Default | Purpose |
|---|---|---|---|
AGENT_READY_API_KEY | No | — | Pro Bearer token from the Agent Ready dashboard. Without it, scan_site uses the anonymous free tier and get_scan is unavailable. |
AGENT_READY_API_URL | No | https://agent-ready.dev | Override for self-hosted or staging deployments. |
AGENT_READY_SCAN_TIMEOUT_MS | No | 60000 | How long scan_site polls before returning a running placeholder. |
AGENT_READY_GET_TIMEOUT_MS | No | 5000 | Timeout for get_scan and per-poll fetches. |
| Tool | Inputs | Returns |
|---|---|---|
scan_site | url (string, required), pageLimit (number, optional, max 2000 — capped by your plan; fixed at 25 keyless) | Scan object: Vercel score 0–100, llms.txt sub-score 0–100, per-check findings with howToFix strings. Keyless runs use the anonymous free tier (3 scans/30 days per IP) and return synchronously; with a Pro key, returns { id, status: "running" } placeholder if the scan exceeds the poll deadline. |
get_scan | id (string, scan id from a prior scan_site call) | Same scan object as scan_site, or not_found if the id is unknown or doesn't belong to the authenticated user. Pro key required. |
ask | q (string, required), itemType (optional corpus filter), mode (optional, list or summarize) | NLWeb /ask over Agent Ready's methodology, checks, and specs. Public — no API key required. Schema.org-typed result objects. |
validate_structured_data | exactly one of url (string) or jsonld (string) | D-series structured-data result: mode, url, per-check findings, and a summary verdict. Public — no API key required. Validates schema lint + agent-coherence the first-party validators don't. |
| Prompt | Args | What it does |
|---|---|---|
scan | url | Fresh scan + high-level summary (score, rating, top 3–5 failures, next step). |
interpret_scan | id | Plain-English explanation of a previous scan's findings, grouped by category. |
remediation_plan | id, optional focus ("seo" or "agents") | Prioritised fix-it doc with Now/Next/Later buckets and per-fix check ids. |
A SKILL.md lives at skills/agent-ready/SKILL.md inside the package. To use it in Claude Desktop / Claude Code, copy the skills/agent-ready/ directory into ~/.claude/skills/.
The skill describes when to activate (URL + readability-audit intent), which tool to pick, how to surface scan results without dumping raw JSON, and when to defer to other tools (general SEO, performance profiling, code editing).
This package is a thin stdio→HTTPS wrapper:
All scan execution, persistence, and Pro-tier quota enforcement happen on the hosted server. The npm package only translates between MCP JSON-RPC over stdio and the REST API.
If you'd rather use the hosted MCP server directly (Streamable HTTP transport, no local install), point your MCP client at https://agent-ready.dev/api/v1/mcp with Authorization: Bearer ar_live_....
The 72 checks, their weights, and the score formula are documented at agent-ready.dev/methodology. Both manifest.json and server.json in this repo conform to the relevant registry schemas (Glama Marketplace v0.3 and MCP registry 2025-12-11 respectively).
See RELEASE.md. It is the source of truth for version surfaces, local checks, tag pushing, the GitHub Actions release workflow, and the manual post-release steps.
MIT — see LICENSE.