Agent Ready
REMOTE · AGENT-READY.DEV · 2 COMPONENTS · SCANNED SEP 20
Scan any URL for AI agent readability — Vercel Spec, llmstxt.org, and agent-protocol manifests.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 870 tokens (~108/item across 8 items; 3 tools + 5 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
How do I install the Agent Ready MCP server?
Agent Ready is a hosted endpoint at https://agent-ready.dev/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agent-ready.dev
claude mcp add --transport http mlava-agent-ready-mcp 'https://agent-ready.dev/api/v1/mcp'
{
"mcpServers": {
"mlava-agent-ready-mcp": {
"url": "https://agent-ready.dev/api/v1/mcp"
}
}
} {
"servers": {
"mlava-agent-ready-mcp": {
"type": "http",
"url": "https://agent-ready.dev/api/v1/mcp"
}
}
} [mcp_servers.mlava-agent-ready-mcp] url = "https://agent-ready.dev/api/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mlava-agent-ready-mcp": {
"type": "remote",
"url": "https://agent-ready.dev/api/v1/mcp",
"enabled": true
}
}
} openclaw mcp add mlava-agent-ready-mcp --url 'https://agent-ready.dev/api/v1/mcp' --transport streamable-http
mcp_servers:
mlava-agent-ready-mcp:
url: "https://agent-ready.dev/api/v1/mcp" {
"McpServers": {
"mlava-agent-ready-mcp": {
"Transport": "http",
"Url": "https://agent-ready.dev/api/v1/mcp"
}
}
} assistant mcp add mlava-agent-ready-mcp -t streamable-http -u 'https://agent-ready.dev/api/v1/mcp'
{
"mcpServers": {
"mlava-agent-ready-mcp": {
"type": "http",
"url": "https://agent-ready.dev/api/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://agent-ready.dev/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agent-ready.dev | CN=YR1,O=Let's Encrypt,C=US | 19 Aug 2026 | 17 Nov 2026 | RSA 2048 | SHA256-RSA | 6e17824c1890c290d6dccba7397db9b3371 |
| SANs: agent-ready.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agent-ready.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| agent-ready.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="agent-ready", error="invalid_token", error_description="Missing Authorization header.", resource_metadata="https://agent-ready.dev/.well-known/oauth-protected-resource"
Bearer realm="agent-ready", error="invalid_token", error_description="Missing Authorization header.", resource_metadata="https://agent-ready.dev/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://clerk.agent-ready.dev https://*.clerk.accounts.dev https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://img.clerk.com; font-src 'self' data:; connect-src 'self' https://clerk.agent-ready.dev https://*.clerk.accounts.dev https://clerk-telemetry.com; frame-src 'self' https://clerk.agent-ready.dev https://*.clerk.accounts.dev https://challenges.cloudflare.com; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Protected resource metadata
| Document | https://agent-ready.dev/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://agent-ready.dev/api/v1/mcp |
| Authorisation server | https://agent-ready.dev |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-ready.dev/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://agent-ready.dev/api/v1/mcp | HTTPS enforced | 308 | https://agent-ready.dev/api/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask Ask Agent Ready in natural language ~194
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). Returns Schema.org-typed result objects. Optional itemType narrows to a corpus type; mode 'summarize' adds an extractive summary.
| Name | Type | Req | Description |
|---|---|---|---|
| itemType | string | – | Restrict results to a content type: methodology, checks, specs, llms-txt, check, page (explainers/guides/glossary), or any (default: all types). |
| mode | string | – | "list" (default) returns matching items; "summarize" returns a synthesized answer. |
| q | string | yes | Natural-language question to search Agent Ready's docs, scoring methodology, check registry, and content library (explainers, comparisons, how-to guides, glossary). |
| Name | Type | Req | Description |
|---|---|---|---|
| message | – | – | Extractive summary when mode is 'summarize'. |
| results | array | yes | Matching result items (Schema.org-typed). |
No examples provided.
get_scan Get a previous scan by id ~60
Fetches a completed or in-progress scan by its id. Only scans owned by the authenticated API key's user are returned.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The scan id returned by scan_site (also the share token in a /scan/<id> URL). |
| Name | Type | Req | Description |
|---|---|---|---|
| accessibilityChecks | – | – | Accessibility / layout-stability checks (A-series) run over the homepage. |
| accessibilityScore | – | – | Accessibility / layout-stability sub-score (0–100) over the homepage WCAG checks; null when none ran. Separate from the Vercel score. |
| id | string | yes | The scan id. |
| llmstxtScore | – | – | llms.txt score (0–100). |
| pagesDiscovered | – | – | Number of pages discovered. |
| pagesScanned | – | – | Number of pages scanned. |
| pollUrl | – | – | Poll URL while the scan is still running. |
| protocolResults | – | – | Agent-protocol checks (C-series) that ran — only for endpoints the site actually exposes. |
| rootUrl | – | – | The scanned site URL. |
| shareUrl | – | – | Path to the shareable report (/scan/<id>). |
| status | string | yes | Scan status: running, completed, or failed. |
| vercelRating | – | – | Rating band for the Vercel score. |
| vercelScore | – | – | Score against the Vercel Agent Readability Spec (0–100); null while running. |
No examples provided.
scan_site Scan a site for AI agent readability ~127
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; for larger scans the tool returns a scan id and asks you to poll with get_scan.
| Name | Type | Req | Description |
|---|---|---|---|
| pageLimit | integer | – | Maximum number of pages to crawl. Defaults to your tier's per-scan page limit when omitted. |
| url | string | yes | Full URL of the site to scan, e.g. https://example.com. Must be a public http(s) address. |
| Name | Type | Req | Description |
|---|---|---|---|
| accessibilityChecks | – | – | Accessibility / layout-stability checks (A-series) run over the homepage. |
| accessibilityScore | – | – | Accessibility / layout-stability sub-score (0–100) over the homepage WCAG checks; null when none ran. Separate from the Vercel score. |
| id | string | yes | The scan id. |
| llmstxtScore | – | – | llms.txt score (0–100). |
| pagesDiscovered | – | – | Number of pages discovered. |
| pagesScanned | – | – | Number of pages scanned. |
| pollUrl | – | – | Poll URL while the scan is still running. |
| protocolResults | – | – | Agent-protocol checks (C-series) that ran — only for endpoints the site actually exposes. |
| rootUrl | – | – | The scanned site URL. |
| shareUrl | – | – | Path to the shareable report (/scan/<id>). |
| status | string | yes | Scan status: running, completed, or failed. |
| vercelRating | – | – | Rating band for the Vercel score. |
| vercelScore | – | – | Score against the Vercel Agent Readability Spec (0–100); null while running. |
No examples provided.
What is the Agent Ready MCP server?
Agent Ready is an MCP server listed in the public MCP registry as io.github.mlava/agent-ready-mcp. Scan any URL for AI agent readability, Vercel Spec, llmstxt.org, and agent-protocol manifests. This page covers its hosted endpoint (https://agent-ready.dev/api/v1/mcp).
Is the Agent Ready MCP server safe to use?
Agent Ready scores 95 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agent Ready MCP server expose?
Agent Ready exposes 3 tools: scan_site, get_scan, ask. Their descriptions and schemas cost roughly 381 tokens of context every time the server is loaded.
Does the Agent Ready MCP server require authentication?
Yes. Agent Ready asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Agent Ready MCP server still maintained?
Agent Ready is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.