Is coframe.com agent ready?
coframe.com is partly agent ready: it scores 52/100 (grade C) on the w2agent rubric. Weakest areas: Agent Auth (22), Agent Protocols (27), Structured Data (35).
Changed since last check
+7 points since the previous check (2026-09-15)
Fixed: Markdown alternate links, Content negotiation (Markdown), Lists and tables for structured info
Regressed: No error status codes, Response time, Security headers
Changed: Schema.org JSON-LD present (fail → partial), Schema.org completeness (fail → partial)
Category scores
Technical
80
Agent Auth
22
Agent Discovery
61
Agent Protocols
27
Content Quality
71
Structured Data
35
Bot Accessibility
84
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityPresent
Check results
Bot Accessibility
- ~No error status codespartial
- ✗Response timefail
- ✓XML sitemap existspass
- ✓AI agent accesspass
- ?Edge treatment of agent user-agentstracked, not scorederror
- ✓robots.txt existspass
- ✓Content negotiation (Markdown)pass
- ✓Declared AI usage preferencestracked, not scoredpass
Structured Data
- ✓OpenGraph meta tagspass
- ✓Semantic HTML elementspass
- ✗Appropriate Schema.org typefail
- ~JSON-LD validpartial
- ~Heading hierarchypartial
- ~Schema.org JSON-LD presentpartial
- ~Schema.org completenesspartial
Content Quality
- ✓FAQ contentpass
- ✓Answer-first contentpass
- ✓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 specpass
- ✓llms.txt existspass
- —MCP server cardtracked, not scoredskip
- ✓Markdown alternate linkspass
- ✗/.well-known/agent-card.jsonfail
- ~llms.txt links resolvepartial
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✗Action schemasfail
- —/.well-known/ucpskip
- ~Structured formspartial
- ✓WebMCP imperative APItracked, not scoredpass
- ✓WebMCP declarative APItracked, not scoredpass
- ✓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 surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- ✗Agent/bot auth documentationfail
- —OAuth discovery chain (RFC 9728 → RFC 8414)skip
- ✓Developer portalpass
- ✗Scoped API permissionsfail
- —API catalog (RFC 9727)skip
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ✗Security headersfail
Other
- —local-business-hours-jsonldskip
- —local-business-nap-structuredskip
- —local-business-booking-accessibleskip
Score history
- 52/100 · rubric v3.0
- 45/100 · rubric v3.0
- 48/100 · rubric v3.0
- 39/100 · rubric v2.0
- 39/100 · rubric v2.0
- 38/100 · rubric v2.0
- 38/100 · rubric v2.0
- 38/100 · rubric v2.0
- 38/100 · rubric v2.0