Is catfact.ninja agent ready?

catfact.ninja is not yet agent ready: it scores 32/100 (grade D) on the w2agent rubric. Weakest areas: Agent Discovery (0), Structured Data (0), Content Quality (17), Agent Auth (20).

32/ 100
Grade: D

Last checked

Scored Oct 14, 2026 · Rubric v3.0

Changed since last check

+2 points since the previous check (2026-09-15)

Fixed: Response time

Category scores

Technical
67
Agent Auth
20
Agent Discovery
0
Agent Protocols
60
Content Quality
17
Structured Data
0
Bot Accessibility
71

Agent protocol panel

  • A2A agent cardNot found
  • OAuth discoveryNot found
  • MCP discoveryPresent
  • llms.txt validityNot measured

Check results

Bot Accessibility

  • ✓No error status codespass
  • ✓Response timepass
  • ✗XML sitemap existsfail
  • ✓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 elementsfail
  • ✗Appropriate Schema.org typefail
  • —JSON-LD validskip
  • ✗Heading hierarchyfail
  • ✗Schema.org JSON-LD presentfail
  • ✗Schema.org completenessfail

Content Quality

  • ✗FAQ contentfail
  • ✗Answer-first contentfail
  • ✗Content lengthfail
  • ✓Token efficiency (HTML-to-text ratio)pass
  • ✗Freshness signalsfail
  • ✗Author attributionfail
  • ✓Citation readinesspass
  • ✗Lists and tables for structured infofail

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 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 surfacepass
  • —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 URLsfail
  • ✗Mobile viewportfail
  • ✓Content accessible without JSpass
  • ~Security headerspartial

Score history

  • 32/100 · rubric v3.0
  • 30/100 · rubric v3.0
  • 31/100 · rubric v3.0
  • 20/100 · rubric v2.0
  • 20/100 · rubric v2.0
  • 20/100 · rubric v2.0
  • 18/100 · rubric v2.0
  • 18/100 · rubric v2.0
  • 20/100 · rubric v2.0
  • 28/100 · rubric v2.0
  • 28/100 · rubric v2.0

Related websites