{
  "markdown": "# agent-ready-mcp\n\nMCP server for [Agent Ready](https://agent-ready.dev) — scan any URL for AI agent readability against the [Vercel Agent Readability Spec](https://vercel.com/kb/guide/agent-readability-spec), the [llmstxt.org](https://llmstxt.org) standard, and agent-protocol manifests (MCP server cards, A2A, agents.json, agent-permissions.json, UCP, x402, NLWeb). 71 checks across four spec families — 39 site and page checks (15 site-wide + 24 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.\n\nHosted 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).\n\n## Features\n\n- **`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.\n- **`get_scan`** — fetch a previously-run scan by id (Pro key required — scan history is account-scoped).\n- **`ask`** — natural-language (NLWeb) search over Agent Ready's own methodology, checks, and specs. Public, no API key required; returns Schema.org-typed results.\n- **`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.\n- **Three discovery prompts** — `scan`, `interpret_scan`, `remediation_plan`. End-to-end workflows from URL → score → fix-it plan.\n- **`SKILL.md`** — Claude Skill descriptor included under `skills/agent-ready/` for activation routing.\n\n## Setup\n\nNo 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](https://agent-ready.dev) and issue a key from the [dashboard](https://agent-ready.dev/dashboard/api-keys). The `env` block in the configs below is optional; omit it to run keyless.\n\n### Claude Desktop\n\nAdd to `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\\Claude\\claude_desktop_config.json` (Windows):\n\n```json\n{\n  \"mcpServers\": {\n    \"agent-ready\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"agent-ready-mcp@latest\"],\n      \"env\": {\n        \"AGENT_READY_API_KEY\": \"ar_live_...\"\n      }\n    }\n  }\n}\n```\n\n### Claude Code\n\n```bash\nclaude mcp add agent-ready \\\n  -e AGENT_READY_API_KEY=ar_live_... \\\n  -- npx -y agent-ready-mcp@latest\n```\n\n### Cursor / VS Code / Windsurf\n\n`.cursor/mcp.json`, `.vscode/mcp.json`, or `~/.codeium/windsurf/mcp_config.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"agent-ready\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"agent-ready-mcp@latest\"],\n      \"env\": {\n        \"AGENT_READY_API_KEY\": \"ar_live_...\"\n      }\n    }\n  }\n}\n```\n\n## Environment variables\n\n| Variable | Required | Default | Purpose |\n|---|---|---|---|\n| `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. |\n| `AGENT_READY_API_URL` | No | `https://agent-ready.dev` | Override for self-hosted or staging deployments. |\n| `AGENT_READY_SCAN_TIMEOUT_MS` | No | `60000` | How long `scan_site` polls before returning a `running` placeholder. |\n| `AGENT_READY_GET_TIMEOUT_MS` | No | `5000` | Timeout for `get_scan` and per-poll fetches. |\n\n## Tools\n\n| Tool | Inputs | Returns |\n|---|---|---|\n| `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. |\n| `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. |\n| `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. |\n| `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. |\n\n## Prompts\n\n| Prompt | Args | What it does |\n|---|---|---|\n| `scan` | `url` | Fresh scan + high-level summary (score, rating, top 3–5 failures, next step). |\n| `interpret_scan` | `id` | Plain-English explanation of a previous scan's findings, grouped by category. |\n| `remediation_plan` | `id`, optional `focus` (`\"seo\"` or `\"agents\"`) | Prioritised fix-it doc with Now/Next/Later buckets and per-fix check ids. |\n\n## Example workflow\n\n```\nYou: Use agent-ready to scan https://my-saas.com\nClaude: [calls scan_site] Your site scored 78/100 (Good) on the Vercel Agent\n        Readability Spec. The top 3 fixes: …\nYou: Can you build me a remediation plan?\nClaude: [calls remediation_plan with the scan id] Here's the prioritised list…\n```\n\n## Skill (Anthropic Claude Skills)\n\nA `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/`.\n\nThe 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).\n\n## How it works\n\nThis package is a thin stdio→HTTPS wrapper:\n\n```\nMCP client (stdio) ↔ agent-ready-mcp ↔ HTTPS ↔ agent-ready.dev/api/v1/scans\n```\n\nAll 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.\n\nIf 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_...`.\n\n## Methodology\n\nThe 71 checks, their weights, and the score formula are documented at [agent-ready.dev/methodology](https://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).\n\n## Development\n\n```bash\nnpm install\nnpm run build       # → dist/mcp-server.mjs\nnpm test\nnpm run typecheck\n```\n\n## Releasing\n\nSee [RELEASE.md](RELEASE.md). It is the source of truth for version surfaces,\nlocal checks, tag pushing, the GitHub Actions release workflow, and the manual\npost-release steps.\n\n## License\n\nMIT — see [LICENSE](LICENSE).\n",
  "bytes": 7403,
  "sha": "595d1ec595d57db2012c381e96fd77b594c971be9fe6c7f707afcf55b2b3daef",
  "repo_slug": "mlava/agent-ready-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_mlava_agent_ready_mcp_6e3248ae/readme"
}