io.github.msanchezgrice/agentready
REMOTE · WWW.AGENTREADY.ME · SCANNED SEP 22
Scan any public site for AI-agent visibility; get scored findings, a machine-readable fix pack, and
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 595 tokens (~85/item across 7 items; 7 tools + 0 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.msanchezgrice/agentready MCP server?
io.github.msanchezgrice/agentready is a hosted endpoint at https://www.agentready.me/api/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 · www.agentready.me
claude mcp add --transport http msanchezgrice-agentready 'https://www.agentready.me/api/mcp'
{
"mcpServers": {
"msanchezgrice-agentready": {
"url": "https://www.agentready.me/api/mcp"
}
}
} {
"servers": {
"msanchezgrice-agentready": {
"type": "http",
"url": "https://www.agentready.me/api/mcp"
}
}
} [mcp_servers.msanchezgrice-agentready] url = "https://www.agentready.me/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"msanchezgrice-agentready": {
"type": "remote",
"url": "https://www.agentready.me/api/mcp",
"enabled": true
}
}
} openclaw mcp add msanchezgrice-agentready --url 'https://www.agentready.me/api/mcp' --transport streamable-http
mcp_servers:
msanchezgrice-agentready:
url: "https://www.agentready.me/api/mcp" {
"McpServers": {
"msanchezgrice-agentready": {
"Transport": "http",
"Url": "https://www.agentready.me/api/mcp"
}
}
} assistant mcp add msanchezgrice-agentready -t streamable-http -u 'https://www.agentready.me/api/mcp'
{
"mcpServers": {
"msanchezgrice-agentready": {
"type": "http",
"url": "https://www.agentready.me/api/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.
- 31 Aug 26 −2
- MCP protocol: pass → fail ▼ functional
- Schema quality: 95 → 85 ▲ functional
- MCP protocol version: 2025-11-25 → 2025-06-18 functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “audit_openapi_readiness” functional
- New tool “check_crawler_access” functional
- New tool “validate_a2a_agent_card” functional
- 26 Aug 26 +1
- 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 81
- Schema quality: 280 → 381 ▼ functional
- New tool “get_public_report” functional
- “scan_url” added an optional parameter “publish_report” cosmetic
- 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
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 22 Sept 2026 · Probed https://www.agentready.me/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.agentready.me | CN=YR1,O=Let's Encrypt,C=US | 26 Jul 2026 | 24 Oct 2026 | RSA 2048 | SHA256-RSA | 5c9d73a55eac617e4400d10c3078ab75f67 |
| SANs: www.agentready.me | ||||||
| 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 www.agentready.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| me. | present | 45352 | 8 | Verified |
| agentready.me. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; script-src 'self' 'unsafe-inline' https:; worker-src 'self' blob:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: https:; font-src 'self' data: https:; connect-src 'self' https:; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.agentready.me/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.agentready.me/api/mcp | HTTPS enforced | 308 | https://www.agentready.me/api/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 →
audit_openapi_readiness Audit OpenAPI agent readiness ~83
Statically inspect an OpenAPI 3.0 or 3.1 JSON object or JSON string for operation identity, auth and scopes, errors, examples, retries, limits, lifecycle, pagination, and workflows. No API operation is executed.
| Name | Type | Req | Description |
|---|---|---|---|
| document | – | yes | OpenAPI JSON object or a string containing JSON. YAML is reported as unsupported and unobservable. |
No output schema declared.
No examples provided.
check_crawler_access Check AI crawler policy and page delivery ~75
Fetch robots.txt and a bounded public page through validated redirects, then inspect named-token path rules, final delivery, X-Robots-Tag, and HTML meta robots. Named-bot edge/WAF treatment remains unobservable.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public site URL and path to evaluate (https://example.com/docs) |
No output schema declared.
No examples provided.
get_fix_pack Get machine-readable fixes ~64
Scan a public URL and return Fix Pack v2: prioritized fixes with stable ids, observed evidence, candidate target URLs and repository paths, review gates, and fix-specific acceptance assertions for a coding agent.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public site URL (https://example.com) |
No output schema declared.
No examples provided.
get_public_report Retrieve a public scan report ~79
Read the latest saved public scan report or bounded history using its opaque report id. Reports are only created after explicit opt-in and expire after 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| history | boolean | – | Return saved snapshots newest first instead of only the latest snapshot. |
| report_id | string | yes | Opaque report id returned by scan_url when publish_report is true. |
No output schema declared.
No examples provided.
scan_url Scan a site for agent readiness ~93
Run an AgentReady scan of a public URL. Returns the 0-100 score, per-phase findings, top priorities, and the Fix Pack v2 implementation contract. Repository paths remain candidate targets until a connected-repository resolver proves them.
| Name | Type | Req | Description |
|---|---|---|---|
| publish_report | boolean | – | Create an unlisted, expiring public report link. Defaults to false. |
| url | string | yes | Public site URL (https://example.com) |
No output schema declared.
No examples provided.
validate_a2a_agent_card Validate an A2A Agent Card ~56
Statically validate an A2A Agent Card JSON object. Strict-current evidence and legacy interoperability are reported separately; no agent endpoint or skill is invoked.
| Name | Type | Req | Description |
|---|---|---|---|
| card | object | yes | A2A Agent Card JSON object. |
No output schema declared.
No examples provided.
verify_fixes Verify fixes landed ~96
Re-scan a public URL and evaluate fix-specific stable ids from a previous v1 or v2 Fix Pack. A fix closes when its finding id is absent; score delta is secondary evidence only.
| Name | Type | Req | Description |
|---|---|---|---|
| previous_fix_pack | object | yes | The Fix Pack returned earlier by get_fix_pack (or an object with {score, fixes:[{id}]}). |
| url | string | yes | Public site URL (https://example.com) |
No output schema declared.
No examples provided.
What is the io.github.msanchezgrice/agentready MCP server?
io.github.msanchezgrice/agentready is an MCP server listed in the public MCP registry as io.github.msanchezgrice/agentready. Scan any public site for AI-agent visibility; get scored findings, a machine-readable fix pack, and. This page covers its hosted endpoint (https://www.agentready.me/api/mcp).
Is the io.github.msanchezgrice/agentready MCP server safe to use?
io.github.msanchezgrice/agentready scores 80 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 io.github.msanchezgrice/agentready MCP server expose?
io.github.msanchezgrice/agentready exposes 7 tools: scan_url, get_fix_pack, verify_fixes, get_public_report, check_crawler_access, and 2 more. Their descriptions and schemas cost roughly 546 tokens of context every time the server is loaded.
Does the io.github.msanchezgrice/agentready MCP server require authentication?
No. We connected to io.github.msanchezgrice/agentready without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.msanchezgrice/agentready MCP server still maintained?
io.github.msanchezgrice/agentready is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.