Markdown Content Negotiation
Validates Accept: text/markdown, Vary: Accept, 406 rejection, and q-value preference exactly like acceptmarkdown.com.
Agent Protocol Readiness Checker
TL;DR: Agent Protocol Readiness Checker checks audit site readiness for ai agents and mcp protocols. so you can confirm the current issue, understand when it matters, and move directly into the next fix without leaving the browser.
Check whether your site speaks the protocols AI agents expect — from Markdown negotiation to MCP discovery and agentic commerce.
Updated
Loading tool interface...
Markdown content negotiation checks MCP Server Card discovery WebMCP, Agent Skills, and API Catalog probes OAuth discovery (RFC 8414 + RFC 9728) x402, ACP, UCP, MPP commerce detection Cloudflare Content Signals and Web Bot Auth detection
What does Agent Protocol Readiness Checker do?
The Agent Protocol Readiness Checker runs twenty-plus probes against a URL to see whether it is ready for modern AI agents. It covers discoverability, Markdown content negotiation, bot access control, emerging protocol discovery endpoints, and agentic commerce standards.
Why it matters: AI agents increasingly prefer sites that advertise capabilities through well-known endpoints and serve machine-friendly formats. Exposing these signals lets agents discover tools and make payments without scraping.
Markdown Negotiation: Checks that `Accept: text/markdown` returns `Content-Type: text/markdown; charset=utf-8`, that `Vary: Accept` is set, that unsupported Accept types return 406, and that q-values are honored.
Bot Access Control: Verifies explicit rules for GPTBot, ClaudeBot, Google-Extended, and PerplexityBot in robots.txt, Cloudflare Content Signals directives, and a Web Bot Auth key directory.
Protocol Discovery: Probes `/.well-known/` endpoints for the MCP Server Card (SEP-1649 / SEP-1960), the Agent Skills manifest, the API Catalog (RFC 9727), OAuth Authorization Server metadata (RFC 8414), and OAuth Protected Resource metadata (RFC 9728). Scans the homepage HTML for WebMCP tool declarations.
Agentic Commerce: Detects x402 (402 Payment Required), ACP (Agentic Commerce Protocol), UCP (Universal Commerce Protocol), and MPP (Machine Payments Protocol) signals so you can verify whether agents can transact with your service.
When should you use Agent Protocol Readiness Checker?
Agent Protocol Readiness Checker is most useful when you need a direct answer on a live URL or draft before you change templates, ship content, or rerun a wider audit.
How to Use This Tool
- 1 Enter a URL to probe.
- 2 Wait as the tool fans out checks across discoverability, accessibility, bot access, protocol discovery, and commerce.
- 3 Review each category's score and per-check findings with evidence from the actual responses.
- 4 Apply the top recommendations to publish the signals agents expect.
What should you do next?
After checking agent protocol readiness, validate robots.txt AI bot rules and run the AI Readiness Checker for content-structure coverage. Then move to the related checks below to confirm the fix on the live canonical page.
What You Get
Protocol Discovery Sweep
Checks MCP Server Cards, Agent Skills, WebMCP, API Catalog (RFC 9727), and OAuth discovery in one pass.
Agentic Commerce Signals
Detects x402, ACP, UCP, and MPP so you know whether agents can transact with your service today.
Frequently Asked Questions
Answers about Agent Protocol Readiness Checker
The Agent Protocol Readiness Checker works by analyzing your URL or input and returning an immediate, actionable report. Use the findings for fast SEO implementation and QA.
Yes, the Agent Protocol Readiness Checker is free to use with no signup required. You can run checks instantly without paywalls.
Incomplete results usually happen when a website blocks automated requests or relies heavily on client-side rendering. Remote access restrictions can also limit what the tool can fetch.
Yes, these results are designed for practical client SEO audits and implementation handoff. They help teams prioritize fixes and validate outcomes quickly.