Is modelcontextprotocol.io agent ready?
modelcontextprotocol.io is partly agent ready: it scores 59/100 (grade C) on the w2agent rubric.
Changed since last check
No change in score since the previous check (2026-09-15)
Category scores
Category breakdown not recorded for this audit.
Agent protocol panel
- A2A agent cardPresent
- OAuth discoveryNot found
- MCP discoveryPresent
- llms.txt validityPresent
Check results
Bot Accessibility
- ✓No error status codespass
- ✓Response timepass
- ✓XML sitemap existspass
- ✓AI agent accesspass
- ✓Edge treatment of agent user-agentstracked, not scoredpass
- ✓robots.txt existspass
- ✓Content negotiation (Markdown)pass
- ✓Declared AI usage preferencestracked, not scoredpass
Structured Data
- ~OpenGraph meta tagspartial
- ~Semantic HTML elementspartial
- ✗Appropriate Schema.org typefail
- ✗JSON-LD validfail
- ✓Heading hierarchypass
- ✓Schema.org JSON-LD presentpass
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ✗Answer-first contentfail
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- ~llms.txt follows specpartial
- ✓llms.txt existspass
- ✓MCP server cardtracked, not scoredpass
- ✓Markdown alternate linkspass
- ~/.well-known/agent-card.jsonpartial
- ✓llms.txt links resolvepass
Agent Protocols
- ✗Discoverable API endpointsfail
- ✓MCP endpointpass
- ✗Action schemasfail
- —/.well-known/ucpskip
- —Structured formsskip
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✓Reachable as Google-Agentpass
- ✓Reachable as ChatGPT-Userpass
- ✓Reachable as Perplexity-Userpass
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- —PKCE S256 supportskip
- ~Public API surfacepartial
- —Client ID Metadata Documents (bonus)skip
- ✗OpenAPI specificationfail
- —Agent/bot auth documentationskip
- ✗OAuth discovery chain (RFC 9728 → RFC 8414)fail
- ✗Developer portalfail
- —Scoped API permissionsskip
- ✗API catalog (RFC 9727)fail
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ✓Security headerspass
Other
- ✗nextjs-metadata-apifail
- ~nextjs-static-generationpartial
- ✓nextjs-well-known-servedpass
Score history
- 59/100 · rubric v3.0
- 59/100 · rubric v3.0
- 55/100 · rubric v2.0
- 55/100 · rubric v2.0
- 53/100 · rubric v2.0
- 52/100 · rubric v2.0
- 49/100 · rubric v2.0
- 49/100 · rubric v2.0
- 49/100 · rubric v2.0
- 48/100 · rubric v2.0
- 49/100 · rubric v2.0