Agent Ready Report is an MCP server published by ai.agenticplug, hosted at scan.agenticplug.ai. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 2 tools, including scan_website, explain_check.
Scan any public website and see how ready it is for AI agents and AI search, explained plainly.
Nothing else in the archive shares these values.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
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.
| Parameter | Type | Description |
|---|---|---|
| url * | string | The website to scan, e.g. "example.com" or "https://www.example.com". |
| 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. |
{
"name": "scan_website",
"title": "Scan a website for agent readiness",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"maxLength": 2048,
"minLength": 3,
"description": "The website to scan, e.g. \"example.com\" or \"https://www.example.com\"."
},
"detail": {
"enum": [
"standard",
"full"
],
"type": "string",
"default": "standard",
"description": "\"standard\": findings with plain-English and technical explanations. \"full\": adds pass criteria, request-by-request evidence and source links."
},
"sells_online": {
"enum": [
"auto",
"yes",
"no"
],
"type": "string",
"default": "auto",
"description": "Whether the site sells online. \"auto\" detects it from the homepage; use \"yes\" or \"no\" when the owner has said."
}
}
},
"annotations": {
"title": "Scan a website for agent readiness",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| check_id | string | The check's id, as shown in a scan report (e.g. "dnsAid", "aiCrawlerAccess"). Omit to list all checks. |
{
"name": "explain_check",
"title": "Explain an agent-readiness check",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"check_id": {
"enum": [
"robotsTxt",
"sitemap",
"linkHeaders",
"dnsAid",
"markdownNegotiation",
"robotsTxtAiRules",
"contentSignals",
"apiCatalog",
"oauthDiscovery",
"oauthProtectedResource",
"authMd",
"mcpServerCard",
"a2aAgentCard",
"agentSkills",
"webMcp",
"ard",
"webBotAuth",
"x402",
"mpp",
"ucp",
"acp",
"ap2",
"https",
"aiCrawlerAccess",
"indexable",
"contentWithoutJs",
"headingStructure",
"titleAndDescription",
"canonical",
"structuredData",
"entitySchema",
"pageTypeSchema",
"language",
"responseTime",
"llmsTxt"
],
"type": "string",
"description": "The check's id, as shown in a scan report (e.g. \"dnsAid\", \"aiCrawlerAccess\"). Omit to list all checks."
}
}
},
"annotations": {
"title": "Explain an agent-readiness check",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}This server scans a public website and reports how ready it is for AI agents and AI search. When presenting a scan: - Lead with the tallies (e.g. "3 of 16 agent-readiness checks passing"). Never describe the result as a "level" or grade. - "Couldn't check" means the scanner got no answer (the site blocked it, timed out or errored). It is not a failure; say so. - Checks marked "emerging standard" are new; missing them is common, even for large companies. - Agentic commerce is only scored for sites that sell online. If the owner says their site sells online but the report says it doesn't, scan again with sells_online "yes". - The report is a diagnostic. Explain what each finding means using the report's own explanations. - Keep the report's attribution line and its disclaimer. Use explain_check for more detail on any single check, or with no check_id to list every check.
Names, descriptions and schemas were written by the server and are shown as data.
Pattern matches on what the server declares. They show what it says it can do, not what it does.
None yet. Changes appear after a server's second daily check.