mnemom.ai agentic web readiness

A+ Score 60 (coverage 40 + breadth 15 + conformance 5). 8 standards observed across 4 of 9 steps; 7 manifests present, 3 errors, 3 warnings. Checked 2026-10-19 01:53:42 UTC via www.mnemom.ai. This grades the agent-facing files published at mnemom.ai, not the organisation's products.

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

Coverage by step

01 DiscoverRFC 9727, agents.txt 02 Identifynothing observed 03 PermitContent Signals Policy, AI Crawler User-Agent Tokens in robots.txt, OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)04 Readllms.txt, AGENTS.md 05 Actnothing observed 06 CoordinateA2A 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) `/mcp/server-card`	absent HTTP 404
Agent2Agent Protocol `/.well-known/agent-card.json`	errors HTTP 200	supportedInterfaces[0].protocolBinding missing supportedInterfaces[0].protocolVersion missing
llms.txt `/llms.txt`	valid HTTP 200
AGENTS.md `/AGENTS.md`	valid HTTP 200	no H1 heading
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`	valid HTTP 200
auth.md `/auth.md`	errors HTTP 200	none of the auth.md mechanism names found (identity_assertion, service_auth, anonymous)

What an agent can call

A2A agent Mnemom at https://api.mnemom.ai/v1, skills: Value catalog, Agent card lookup
API description https://www.mnemom.ai/openapi.json (application/json)
API description https://docs.mnemom.ai/api-reference (text/html)
API description https://www.mnemom.ai/.well-known/oauth-protected-resource (application/json)
llms.txt: Mnemom, 76 links
robots.txt AI policy: unlisted crawlers partial
OAuth protected resource https://www.mnemom.ai, authorization servers: https://www.mnemom.ai, https://id-us2.mnemom.ai

Standards observed

Agent2Agent Protocol https://mnemom.ai/.well-known/agent-card.json
llms.txt https://mnemom.ai/llms.txt
AGENTS.md https://mnemom.ai/AGENTS.md
Content Signals Policy https://mnemom.ai/robots.txt
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://mnemom.ai/.well-known/api-catalog
AI Crawler User-Agent Tokens in robots.txt https://mnemom.ai/robots.txt
agents.txt https://mnemom.ai/agents.txt
OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization) https://mnemom.ai/.well-known/oauth-protected-resource

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
MCP Server Cards (SEP-2127): if you run an MCP server, a SEP-2127 card at <mcp-url>/server-card lets clients configure themselves

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