Agent Ready
NPM · AGENT-READY-MCP · 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 from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mlava/agent-ready-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability89
- 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
- Context-footprint check failed: tool/resource definitions use about 931 tokens (~116/item across 8 items; 4 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 4 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
How do I install the Agent Ready MCP server?
Agent Ready runs locally as an npm package, launched with npx -y agent-ready-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · agent-ready-mcp
claude mcp add mlava-agent-ready-mcp -- npx -y agent-ready-mcp
{
"mcpServers": {
"mlava-agent-ready-mcp": {
"command": "npx",
"args": [
"-y",
"agent-ready-mcp"
]
}
}
} {
"servers": {
"mlava-agent-ready-mcp": {
"command": "npx",
"args": [
"-y",
"agent-ready-mcp"
]
}
}
} codex mcp add mlava-agent-ready-mcp -- npx -y agent-ready-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mlava-agent-ready-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"agent-ready-mcp"
],
"enabled": true
}
}
} openclaw mcp add mlava-agent-ready-mcp --command npx --arg -y --arg agent-ready-mcp
mcp_servers:
mlava-agent-ready-mcp:
command: "npx"
args: ["-y", "agent-ready-mcp"] {
"McpServers": {
"mlava-agent-ready-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"agent-ready-mcp"
]
}
}
} assistant mcp add mlava-agent-ready-mcp -t stdio -c npx -a -y agent-ready-mcp
{
"mcpServers": {
"mlava-agent-ready-mcp": {
"command": "npx",
"args": [
"-y",
"agent-ready-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.87 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 14 Sept 26 −1
- Stability: pass → 0.93 functional
- 13 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 · Analysed npm/agent-ready-mcp@0.7.7
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | mlava/agent-ready-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mlava/agent-ready-mcp/.github/workflows/release.yml@refs/tags/v0.7.7 |
| Rekor log index | 2747947218 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3f0061e492b3224547193439f00055ef18e583e3b2b0fd475c4545c346ceb4147f516841b3319fd60cc5b5475f008b8e9bc4aebc79e24d43089169224 |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| itemType | string | – | Optional filter narrowing the search to one corpus type ('page' = explainers/guides/glossary). |
| mode | string | – | 'summarize' adds an extractive summary over the top results. |
| q | string | yes | Natural-language question about Agent Ready's scoring methodology, its check registry, the specs it validates, or its content library (explainers, comparisons, how-to guides, glossary). |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| error | object | – | – |
| mode | string | – | – |
| query | string | – | – |
| query_id | string | – | – |
| results | array | – | – |
| site | string | – | – |
| summary | string | – | – |
No examples provided.
get_scan Get a previous scan by id ~73
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.)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Scan id returned by a previous scan_site call (10-character nanoid). |
| Name | Type | Req | Description |
|---|---|---|---|
| completedAt | – | – | – |
| createdAt | string | – | – |
| id | string | yes | – |
| llmstxtChecks | array | – | – |
| llmstxtScore | number | – | – |
| message | string | – | – |
| pageResults | array | – | – |
| pagesDiscovered | number | – | – |
| pagesScanned | number | – | – |
| pollUrl | string | – | – |
| rootUrl | string | – | – |
| saveUrl | string | – | – |
| shareToken | string | – | – |
| siteChecks | array | – | – |
| status | string | yes | – |
| url | string | – | – |
| vercelRating | string | – | – |
| vercelScore | number | – | – |
No examples provided.
scan_site Scan a site for AI agent readability ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pageLimit | integer | – | Optional maximum number of pages to crawl from the root URL. Capped by your plan (Free 25, Pro 250, Team 2000). |
| url | string | yes | Fully-qualified URL to scan, including scheme (https://...). |
| Name | Type | Req | Description |
|---|---|---|---|
| completedAt | – | – | – |
| createdAt | string | – | – |
| id | string | yes | – |
| llmstxtChecks | array | – | – |
| llmstxtScore | number | – | – |
| message | string | – | – |
| pageResults | array | – | – |
| pagesDiscovered | number | – | – |
| pagesScanned | number | – | – |
| pollUrl | string | – | – |
| rootUrl | string | – | – |
| saveUrl | string | – | – |
| shareToken | string | – | – |
| siteChecks | array | – | – |
| status | string | yes | – |
| url | string | – | – |
| vercelRating | string | – | – |
| vercelScore | number | – | – |
No examples provided.
validate_structured_data Validate JSON-LD structured data ~191
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.
| Name | Type | Req | Description |
|---|---|---|---|
| jsonld | string | – | A raw JSON-LD string to validate directly (paste mode) — e.g. structured data an agent just authored. Provide either jsonld OR url, not both. |
| url | string | – | URL of a page to fetch and validate its JSON-LD. Provide either url OR jsonld, not both. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| mode | string | yes | – |
| summary | object | yes | – |
| url | – | yes | – |
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 npm package (agent-ready-mcp).
Is the Agent Ready MCP server safe to use?
Agent Ready scores 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 4 tools: scan_site, get_scan, ask, validate_structured_data. Their descriptions and schemas cost roughly 619 tokens of context every time the server is loaded.
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.
What licence is the Agent Ready MCP server under?
Agent Ready declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.