Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGENT_READY_API_KEYYesBearer token issued from the Agent Ready dashboard.
AGENT_READY_API_URLNoOverride for self-hosted or staging deployments.https://agent-ready.dev
AGENT_READY_GET_TIMEOUT_MSNoTimeout for get_scan and per-poll fetches.5000
AGENT_READY_SCAN_TIMEOUT_MSNoHow long scan_site polls before returning a running placeholder.60000

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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. 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_scanA

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.)

askA

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_dataA

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.

Prompts

Interactive templates invoked by user choice

NameDescription
scanRun a fresh agent-readability scan against a URL and summarise the most important findings.
interpret_scanFetch a previous scan by id and translate the per-check findings into plain-English explanations.
remediation_planFetch 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

NameDescription
methodologyHow Agent Ready computes the 0–100 readability score and the llms.txt sub-score. Covers the 69 checks across four categories, rating bands, weighting, and JS-rendering handling.
checksReference table of all 69 checks Agent Ready runs, grouped by category (site, page, llms.txt, protocol), plus the 9-check accessibility suite scored as a separate accessibility sub-score. Each row pairs the stable check ID (e.g. P11, S15, L9, C3, A7) with its human-readable name. Use this to identify a check by id when interpreting scan results.
llms-txtThe /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.
specsCanonical URLs and check-ID mappings for the 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), x402 and MPP payments, NLWeb, API Catalog (RFC 9727), Web Bot Auth, Agent Skills Discovery, content parity, and Agent-driven UI (A2UI).

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