mpp.dev agentic web readiness

A Score 49 (coverage 30 + breadth 9 + conformance 10). 5 standards observed across 3 of 9 steps; 5 manifests present, 1 error, 8 warnings. Checked 2026-10-18 23:42:51 UTC. This grades the agent-facing files published at mpp.dev, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/mpp.dev.svg) · JSON · Markdown · Re-check now

Coverage by step

01 DiscoverRFC 9727 02 Identifynothing observed 03 PermitContent Signals Policy, AI Crawler User-Agent Tokens in robots.txt 04 Readllms.txt, AGENTS.md 05 Actnothing observed 06 Coordinatenothing observed 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

Manifests

Manifest	Result	Findings
Agentic Resource Discovery `/.well-known/ard.json`	absent HTTP 404
AI Catalog well-known file `/.well-known/ai-catalog.json`	absent HTTP 404
MCP Server Cards (SEP-2127) `/.well-known/mcp.json`	errors HTTP 200	name missing Content-Type is application/json; charset=utf-8; SEP-2127 says serve application/mcp-server-card+json pre-final card shape (url/transport/tools); the final SEP-2127 card uses name, version, description and remotes[] $schema is not https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json description is over 100 characters remotes missing: a card with no remotes gives clients nothing to connect to tools/resources/prompts listed in the card; SEP-2127 excludes primitives (list them live, or under a namespaced _meta key)
Agent2Agent Protocol `/.well-known/agent-card.json`	absent HTTP 404
llms.txt `/llms.txt`	valid HTTP 200	no blockquote summary under the title
AGENTS.md `/AGENTS.md`	valid HTTP 200
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs `/.well-known/api-catalog`	valid HTTP 200
AI Crawler User-Agent Tokens in robots.txt `/robots.txt`	valid HTTP 200	no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
security.txt (RFC 9116) `/.well-known/security.txt`	absent HTTP 404
auth.md `/auth.md`	absent HTTP 404

What an agent can call

API description https://mpp.dev/.well-known/mcp.json (application/json)
API description https://mpp.dev/guides/building-with-an-llm (text/html)
API description https://mpp.dev/AGENTS.md (text/markdown)
API description https://mpp.dev/.well-known/agent-skills/index.json (application/json)
API description https://mpp.dev/agent-permissions.json (application/json)
llms.txt: MPP — Machine Payments Protocol, 199 links
robots.txt AI policy: allows GPTBot, ClaudeBot, Google-Extended, PerplexityBot; unlisted crawlers allowed

Standards observed

llms.txt https://mpp.dev/llms.txt
AGENTS.md https://mpp.dev/AGENTS.md
Content Signals Policy https://mpp.dev/robots.txt
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://mpp.dev/.well-known/api-catalog
AI Crawler User-Agent Tokens in robots.txt https://mpp.dev/robots.txt

Cheapest next steps

Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch
security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people

How the grade is made

+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.

JSON · Markdown · probe rules