Agent Ready Report
REMOTE · SCAN.AGENTICPLUG.AI
Scan any public website and see how ready it is for AI agents and AI search, explained plainly.
Available components
Last scanned (7 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 608 tokens (~304/item across 2 items; 2 tools + 0 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 Management87
- Stability observed for 26 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 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 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 5 Nov 2026 · Probed https://scan.agenticplug.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agenticplug.ai | CN=WE1,O=Google Trust Services,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | dfa485818c447afa132d65380cabed24 |
| SANs: agenticplug.ai, scan.agenticplug.ai, *.scan.agenticplug.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of scan.agenticplug.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| agenticplug.ai. | present | 2371 | 13 | Verified |
| scan.agenticplug.ai. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://scan.agenticplug.ai/mcp | Verified | 200 | |
| http (plaintext) | http://scan.agenticplug.ai/mcp | Inconclusive | 405 |
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 an agent-readiness check ~97
Explain one agent-readiness check in depth: what it is, why it matters for AI agents and AI search, exactly how the scanner tests it, what counts as a pass, and the official sources. Call with no check_id to list every check.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | – | The check's id, as shown in a scan report (e.g. "dnsAid", "aiCrawlerAccess"). Omit to list all checks. |
No output schema declared.
No examples provided.
scan_website Scan a website for agent readiness ~311
Scan a public website and report how ready it is for AI agents and AI search: which checks pass, which are missing, and what each check is, in plain English and technically. Covers 35 checks in three groups: agent readiness (robots.txt and AI crawler rules, sitemap, Link headers, DNS-AID, markdown for agents, Content Signals, API catalog, OAuth discovery, auth.md, MCP server card, A2A agent card, agent skills, WebMCP, ARD), agentic commerce (x402, MPP, UCP, ACP, AP2; scored only for sites that sell online), and AI search foundations (HTTPS, AI crawler access, indexability, content without JavaScript, heading structure, title and description, canonical URL, structured data, business identity markup, language, response time). Use when someone asks whether their website is ready for AI agents, AI search, ChatGPT, Claude, Perplexity, Muse or agentic commerce. A scan takes 5 to 30 seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | "standard": findings with plain-English and technical explanations. "full": adds pass criteria, request-by-request evidence and source links. |
| sells_online | string | – | Whether the site sells online. "auto" detects it from the homepage; use "yes" or "no" when the owner has said. |
| url | string | yes | The website to scan, e.g. "example.com" or "https://www.example.com". |
No output schema declared.
No examples provided.
How do I install the Agent Ready Report MCP server?
Agent Ready Report is a hosted endpoint at https://scan.agenticplug.ai/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 · scan.agenticplug.ai
claude mcp add --transport http ai-agenticplug-agent-ready-report 'https://scan.agenticplug.ai/mcp'
What is the Agent Ready Report MCP server?
Agent Ready Report is an MCP server listed in the public MCP registry as ai.agenticplug/agent-ready-report. Scan any public website and see how ready it is for AI agents and AI search, explained plainly. This page covers its hosted endpoint (https://scan.agenticplug.ai/mcp).
Is the Agent Ready Report MCP server safe to use?
Agent Ready Report scores 78 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 Report MCP server expose?
Agent Ready Report exposes 2 tools: scan_website, explain_check. Their descriptions and schemas cost roughly 408 tokens of context every time the server is loaded.
Does the Agent Ready Report MCP server require authentication?
No. We connected to Agent Ready Report without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Ready Report MCP server still maintained?
Agent Ready Report is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.