Agent Ready MCP Server

Agent Ready MCP MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. MCP server for Agent Ready — scan any URL for AI-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).

What you get

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
• Three discovery prompts — — 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

What the assistant can call

Once Agent Ready MCP is connected, these are the calls the assistant has available:

• scan_site — url (string, required), pageLimit (number, optional, max 2000 — capped by your plan; fixed at 25 keyless)
• get_scan — id (string, scan id from a prior scan_site call)
• ask — q (string, required), itemType (optional corpus filter), mode (optional, list or summarize)
• validate_structured_data — exactly one of url (string) or jsonld (string)

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need 2 environment variables: AGENT_READY_API_KEY, AGENT_READY_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Agent Ready MCP's toolset — scan_site, get_scan, ask and 1 more — is a fair guide to whether it matches your workflow. It is maintained by mlava; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the agent ready mcp mcp server does with a few real requests.