Agent Ready CLI

The Agent Ready CLI (agent-ready, published to npm as agent-ready-scanner) scores any public URL against ~70 checks across the Vercel Agent Readability Spec, the llmstxt.org standard, and the agent-protocol manifests (MCP server cards, A2A, agents.json, agent-permissions.json, UCP, x402, NLWeb). It's a thin zero-dependency wrapper over the hosted agent-ready.dev REST API — no scanning happens locally.

Use this skill when you can run shell commands and want the fewest moving parts: one command starts a scan, polls to completion, and prints a summary — no HTTP wiring, no MCP client config. It's also the right fit for scripting, because it emits machine-readable JSON to stdout and uses distinct exit codes.

When to use

Use when you can run shell commands and want a one-command scan with no HTTP wiring. Choose a sibling instead for raw HTTP or no shell (agent-ready-api) or for MCP-native tool calls (agent-ready-mcp) — all three share one REST API and rate-limit budget. Trigger phrases are in the description above.

Step 1: Confirm Node and reach the CLI

The CLI needs Node.js ≥ 20.10. No install is required — run it on demand with npx:

npx agent-ready-scanner --version

If the user will use it repeatedly, install it globally (this provides the agent-ready command):