Agent Ready
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_READY_API_KEY | Yes | Bearer token issued from the Agent Ready dashboard. | |
| AGENT_READY_API_URL | No | Override for self-hosted or staging deployments. | https://agent-ready.dev |
| AGENT_READY_GET_TIMEOUT_MS | No | Timeout for get_scan and per-poll fetches. | 5000 |
| AGENT_READY_SCAN_TIMEOUT_MS | No | How long scan_site polls before returning a running placeholder. | 60000 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_siteA | 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. Scans 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_scanA | Fetches a completed or in-progress scan by its id. Only scans owned by the authenticated API key's user are returned. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| scan | Run a fresh agent-readability scan against a URL and summarise the most important findings. |
| interpret_scan | Fetch a previous scan by id and translate the per-check findings into plain-English explanations. |
| remediation_plan | Fetch a scan by id and produce a prioritised, actionable remediation plan, optionally focused on SEO or agent-protocol fixes. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| methodology | How Agent Ready computes the 0–100 readability score and the llms.txt sub-score. Covers the 59 checks across four categories, rating bands, weighting, and JS-rendering handling. |
| checks | Reference table of all 59 checks Agent Ready runs, grouped by category (site, page, llms.txt, protocol). Each row pairs the stable check ID (e.g. P11, S15, L9, C3) with its human-readable name. Use this to identify a check by id when interpreting scan results. |
| llms-txt | The /llms.txt file agent-ready.dev publishes for AI agents discovering it as a tool. Mirrors the live document at https://agent-ready.dev/llms.txt. Useful as a worked example for the llms.txt validator and for clients introspecting Agent Ready's surface. |
| specs | Canonical URLs and check-ID mappings for the seven specifications Agent Ready implements: Vercel Agent Readability Spec, llmstxt.org, MCP Server Cards (SEP-1649 / RFC 9728), A2A Agent Cards (a2a.proto v1.0.0), Wildcard agents.json, agent-permissions.json, UCP (RFC 8414), and x402 Payment Required. |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mlava/agent-ready-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server