Agent Ready
About
AI agent readability scanner — score any public URL against the Vercel Agent Readability Spec, llmstxt.org, and 6 agent-protocol manifests (MCP, A2A, agents.json, agent-permissions, UCP, x402). 59 checks with per-check fix guidance. Same engine as agent-ready.dev.
Details
- Author
- mlava
- Downloads
- 372
- Categories
- Productivity, Developer Tools, AI, Knowledge Base
Jump to
- 59 checks across 4 spec families (Vercel, llmstxt, agent‑protocol manifests).
- Every failing check includes a concrete howToFix string.
- Two tools: scan_site (fresh scan) and get_scan (retrieve by id).
- Three prompts: scan, interpret_scan, and remediation_plan.
- Ships a Claude Skill descriptor for activation routing.
- Runs via npm, hosted HTTP, or on Smithery.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Agent ReadyCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Configure the MCP server in your client’s mcpServers setting using npx -y agent-ready-mcp@latest and set the AGENT_READY_API_KEY environment variable (Pro or Team tier required). Once connected, use the scan_site tool to run a fresh scan or get_scan to fetch a previous scan by id. Prompts like scan, interpret_scan, and remediation_plan provide plain‑English summaries and prioritized fix documentation.
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. Works without an API key on the anonymous free tier (3 scans/30 days per IP, 25-page depth, synchronous). With a Pro AGENT_READY_API_KEY it scans deeper (up to 250 pages) and may take up to ~60s; if the local poll deadline elapses, the tool returns the scan id and asks you to poll with get_scan.
get_scan
Fetches a completed or in-progress scan by its id. Requires a Pro API key — scan history is account-scoped. (Anonymous scan_site calls return their result inline, so keyless use never needs this tool.)
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). Public, no API key required. Returns Schema.org-typed result objects; optional itemType narrows to a corpus type and mode 'summarize' adds an extractive summary.
validate_structured_data
Validates a page's (or a pasted) JSON-LD against Agent Ready's structured-data checks (schema lint + agent-coherence: freshness honesty, canonical/.md coherence, entity-name consistency, extraction signal) and returns a verdict with per-check fix guidance. Provide exactly one of `url` (fetch + validate) or `jsonld` (validate a string the agent just authored — no network needed). Public, no API key required. The one structured-data check the first-party validators (validator.schema.org, Rich Results Test) don't do.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"agent ready": {
"agent-ready": {
"command": "npx",
"args": [
"-y",
"agent-ready-mcp@latest"
],
"env": {
"AGENT_READY_API_KEY": "<YOUR_AGENT_READY_API_KEY>"
}
}
}
}
}McpServers
{
"agent-ready": {
"command": "npx",
"args": [
"-y",
"agent-ready-mcp@latest"
],
"env": {
"AGENT_READY_API_KEY": "<YOUR_AGENT_READY_API_KEY>"
}
}
}MCP server forAgent Ready— scan any URL for AI agent readability against theVercel Agent Readability Spec, thellmstxt.orgstandard, and agent-protocol manifests (MCP server cards, A2A, agents.json, agent-permissions.json, UCP, x402, NLWeb). 70 checks across four spec families — 38 against the Vercel spec (15 site-wide + 23 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 athttps://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.
- Three discovery prompts—scan,interpret_scan,remediation_plan. End-to-end workflows from URL → score → fix-it plan.
- SKILL.md— Claude Skill descriptor included underskills/agent-ready/for activation routing.
No key is required to start:scan_site,ask, andvalidate_structured_dataall work anonymously out of the box (scan_siteon the free anonymous quota — 3 scans per 30 days per IP at 25-page depth). An Agent ReadyPro API keyunlocks 50 scans/month, 250-page depth, scan history (get_scan), and weekly monitoring — sign up atagent-ready.devand issue a key from thedashboard. Theenvblock 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):
{ "mcpServers": { "agent-ready": { "command": "npx", "args": ["-y", "agent-ready-mcp@latest"], "env": { "AGENT_READY_API_KEY": "ar_live_..." } } } }
claude mcp add agent-ready \ -e AGENT_READY_API_KEY=ar_live_... \ -- npx -y agent-ready-mcp@latest
.cursor/mcp.json,.vscode/mcp.json, or~/.codeium/windsurf/mcp_config.json:
{ "mcpServers": { "agent-ready": { "command": "npx", "args": ["-y", "agent-ready-mcp@latest"], "env": { "AGENT_READY_API_KEY": "ar_live_..." } } } }
You: Use agent-ready to scan https://my-saas.com Claude: [calls scan_site] Your site scored 78/100 (Good) on the Vercel Agent Readability Spec. The top 3 fixes: … You: Can you build me a remediation plan? Claude: [calls remediation_plan with the scan id] Here's the prioritised list…
ASKILL.mdlives atskills/agent-ready/SKILL.mdinside the package. To use it in Claude Desktop / Claude Code, copy theskills/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:
MCP client (stdio) ↔ agent-ready-mcp ↔ HTTPS ↔ agent-ready.dev/api/v1/scans
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 athttps://agent-ready.dev/api/v1/mcpwithAuthorization: Bearer ar_live_....
The 70 checks, their weights, and the score formula are documented atagent-ready.dev/methodology. Bothmanifest.jsonandserver.jsonin this repo conform to the relevant registry schemas (Glama Marketplace v0.3 and MCP registry 2025-12-11 respectively).
npm install npm run build # → dist/mcp-server.mjs npm test npm run typecheck
Assists AI developers with requirement clarification, module design, and technical architecture.
Provides AI assistants with a comprehensive, one-time analysis for complete codebase context and understanding.
The official Duck Framework MCP server provides AI assistants with rich, project-aware context for building applications using Duck Framework. It offers documentation retrieval, code guidance, API references, best practices, component discovery, and framework-specific recommendations to help developers generate high-quality Duck Framework projects faster and more accurately.
Integrates MATLAB with AI to execute code, generate scripts from natural language, and access documentation.
An AI-powered documentation server for code improvement and management, with Claude and Brave Search integration.
A collection of reference implementations for the Model Context Protocol (MCP), demonstrating how to give LLMs secure access to tools and data using Typescript and Python SDKs.
Automatic documentation updates from agents, and codebase conventions to reduce token usage.
ast-mcp-server gives coding agents compact, type-aware access to TypeScript and JavaScript projects. It uses the real compiler project model through ts-morph, so declarations, references, rename locations, and diagnostics come from the AST instead of text-search guesses.
An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .
MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
