Agent Ready
REMOTE · AGENTREADY.SNEEZE.IT
Score any website out of 100 for how well AI agents can find, understand and use it.
Available components
Last scanned (4 hours ago)
Scores higher than 69% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Testing and QA
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.37 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 72
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 5 Nov 2026 · Probed https://agentready.sneeze.it/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentready.sneeze.it. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| it. | present | 51765 | 13 | Verified |
| sneeze.it. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentready.sneeze.it/mcp | Unreachable | ||
| http (plaintext) | http://agentready.sneeze.it/mcp | HTTPS enforced |
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 →
explain_check Explain one Agent Ready check ~67
Explain what one check measures, what it is worth and where to read how to fix it. Pass the check name as it appears in a report, for example "WebMCP tools an agent can call".
| Name | Type | Req | Description |
|---|---|---|---|
| check | string | yes | The check name, or a few words from it. |
No output schema declared.
No examples provided.
get_report Get an existing Agent Ready report ~52
Fetch a report that was already run, by its report link or id, without scanning again.
| Name | Type | Req | Description |
|---|---|---|---|
| report | string | yes | A report URL (https://agentready.sneeze.it/report/...) or report id. |
No output schema declared.
No examples provided.
get_scoring_method How the Agent Ready score works ~27
The scored areas, their weights and every check, so a score can be explained.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_website Scan a website for agent readiness ~156
Score any public website out of 100 for how well AI agents can use it: reach it, understand it, act on it (book, quote, buy), complete the task, act for a signed-in customer, trust its facts, and find the right location. Returns the score, a score per area, the most important finding in each area, and a link to the full report with every finding and the ordered fix plan. Takes 5 to 20 seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | Rescan even if the site was scanned in the last 30 minutes. Use after the owner changed something. |
| url | string | yes | The website to scan, for example acme.com or https://www.acme.com/ |
No output schema declared.
No examples provided.
How do I install the Agent Ready MCP server?
Agent Ready is a hosted endpoint at https://agentready.sneeze.it/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 · agentready.sneeze.it
claude mcp add --transport http it-sneeze-agentready-agent-ready 'https://agentready.sneeze.it/mcp'
What is the Agent Ready MCP server?
Agent Ready is an MCP server listed in the public MCP registry as it.sneeze.agentready/agent-ready. Score any website out of 100 for how well AI agents can find, understand and use it. This page covers its hosted endpoint (https://agentready.sneeze.it/mcp).
Is the Agent Ready MCP server safe to use?
Agent Ready scores 77 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 4 tools: scan_website, get_report, explain_check, get_scoring_method. Their descriptions and schemas cost roughly 302 tokens of context every time the server is loaded.
Does the Agent Ready MCP server require authentication?
Its publisher declares no required credentials for Agent Ready. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Agent Ready MCP server still maintained?
Agent Ready is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.