Is granbluefantasy.jp agent ready?
granbluefantasy.jp is not yet agent ready: it scores 40/100 (grade D) on the w2agent rubric. Weakest areas: Agent Discovery (0), Agent Auth (10), Agent Protocols (30), Content Quality (49).
Changed since last check
+1 points since the previous check (2026-09-16)
Fixed: Response time
Category scores
Technical
60
Agent Auth
10
Agent Discovery
0
Agent Protocols
30
Content Quality
49
Structured Data
87
Bot Accessibility
53
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 timepass
- ✗XML sitemap existsfail
- ✓AI agent accesspass
- ✓Edge treatment of agent user-agentstracked, not scoredpass
- ✗robots.txt existsfail
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ✓OpenGraph meta tagspass
- ✓Semantic HTML elementspass
- ✓Appropriate Schema.org typepass
- ✓JSON-LD validpass
- ✓Heading hierarchypass
- ✓Schema.org JSON-LD presentpass
- ~Schema.org completenesspartial
Content Quality
- ✓FAQ contentpass
- ✓Answer-first contentpass
- ~Content lengthpartial
- ~Token efficiency (HTML-to-text ratio)partial
- ✗Freshness signalsfail
- ✗Author attributionfail
- ~Citation readinesspartial
- ✓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 endpointsfail
- ✗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 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 URLsfail
- ✓Mobile viewportpass
- ~Content accessible without JSpartial
- ~Security headerspartial
Score history
- 40/100 · rubric v3.0
- 39/100 · rubric v3.0
- 40/100 · rubric v3.0
- 43/100 · rubric v2.0
- 43/100 · rubric v2.0
- 43/100 · rubric v2.0
- 43/100 · rubric v2.0