Is npci.org.in agent ready?
npci.org.in is not yet agent ready: it scores 22/100 (grade F) on the w2agent rubric.
Changed since last check
+4 points since the previous check (2026-09-15)
Fixed: Mobile viewport, Token efficiency (HTML-to-text ratio), Citation readiness
Category scores
Category breakdown not recorded for this audit.
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 existspass
- ✗AI agent accessfail
- ✗Edge treatment of agent user-agentstracked, not scoredfail
- ✓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 endpointfail
- ✗Action schemasfail
- —/.well-known/ucpskip
- —Structured formsskip
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✗Reachable as Google-Agentfail
- ✗Reachable as ChatGPT-Userfail
- ✗Reachable as Perplexity-Userfail
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 viewportpass
- ✗Content accessible without JSfail
- ~Security headerspartial
Score history
- 22/100 · rubric v3.0
- 18/100 · rubric v3.0
- 39/100 · rubric v2.0
- 39/100 · rubric v2.0
- 38/100 · rubric v2.0
- 39/100 · rubric v2.0
- 38/100 · rubric v2.0
- 38/100 · rubric v2.0