Is developer.mozilla.org agent ready?
developer.mozilla.org is partly agent ready: it scores 46/100 (grade C) on the w2agent rubric. Weakest areas: Agent Discovery (0), Structured Data (14), Agent Auth (27).
Changed since last check
−1 points since the previous check (2026-10-14)
Changed: Response time (partial → fail)
Category scores
Technical
100
Agent Auth
27
Agent Discovery
0
Agent Protocols
50
Content Quality
67
Structured Data
14
Bot Accessibility
79
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot found
- MCP discoveryNot found
- llms.txt validityNot measured
Check results
Bot Accessibility
- ✓No error status codespass
- ✗Response timefail
- ✓XML sitemap existspass
- ✓AI agent accesspass
- ✓Edge treatment of agent user-agentstracked, not scoredpass
- ✓robots.txt existspass
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ✗OpenGraph meta tagsfail
- ✓Semantic HTML elementspass
- ✗Appropriate Schema.org typefail
- —JSON-LD validskip
- ✓Heading hierarchypass
- ✗Schema.org JSON-LD presentfail
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ✗Answer-first contentfail
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✓Freshness signalspass
- ✗Author attributionfail
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- —llms.txt follows specskip
- ✗llms.txt existsfail
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- —llms.txt links resolveskip
Agent Protocols
- ✓Discoverable API endpointspass
- ✗MCP endpointfail
- ✗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 supportfail
- ✓Public API surfacepass
- —Client ID Metadata Documents (bonus)skip
- ✗OpenAPI specificationfail
- ✗Agent/bot auth documentationfail
- ✗OAuth discovery chain (RFC 9728 → RFC 8414)fail
- ✓Developer portalpass
- ✗Scoped API permissionsfail
- ✗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
Score history
- 46/100 · rubric v3.0
- 47/100 · rubric v3.0
- 47/100 · rubric v3.0
- 47/100 · rubric v3.0
- 45/100 · rubric v2.0
- 47/100 · rubric v2.0
- 47/100 · rubric v2.0
- 45/100 · rubric v2.0
- 44/100 · rubric v2.0
- 40/100 · rubric v2.0
- 40/100 · rubric v2.0
- 38/100 · rubric v2.0
- 38/100 · rubric v2.0
- 40/100 · rubric v2.0
- 39/100 · rubric v2.0
- 40/100 · rubric v2.0
- 40/100 · rubric v2.0
- 44/100 · rubric v2.0
- 34/100 · rubric v2.0