Other

46 / 100

Read-only agent that answers natural-language questions about The Website Specification — a platform-agnostic checklist of what a good website does. Send a message and the agent searches every spec pa

Scanned 16d ago · 38 views · Open site

Callable

• MCP — · none
• OpenAPI —
• Pricing —
• Auth none
• No agent payment rail · /pay/specification.website

Checks

• HTTPS5/5

  Served over HTTPS.

  https://specification.website/
• llms.txt12/12

  Found /llms.txt (53414 chars).

  https://specification.website/llms.txt
• Agent manifest0/15

  No /.well-known/ai-agent.json.

  Fix: Publish https://specification.website/.well-known/ai-agent.json with name, description, capabilities, contact, auth, and pricing.

• A2A agent card12/12

  A2A agent card with skills or capabilities.

  https://specification.website/.well-known/agent-card.json
• MCP endpoint4/12

  MCP document found, but it has no remote server URL.

  https://specification.website/mcp

  Fix: Publish /.well-known/mcp.json with an HTTPS server URL. A homepage mention does not count.

• OpenAPI spec0/12

  No OpenAPI or Swagger spec found.

  Fix: Serve /openapi.json (or /swagger.json) with a valid OpenAPI spec, or link it from the homepage.

• Named capabilities8/8

  3 named capabilities (3 with descriptions).

• I/O schemas0/8

  No I/O schemas.

  Fix: Add components.schemas / requestBody schemas in OpenAPI, or input/output schemas on each skill.

• Machine-readable pricing0/8

  No machine-readable pricing.

  Fix: Add a pricing object to ai-agent.json, or publish /pricing.json with currency and product amounts.

• Auth, contact, rate limits5/8

  Declared: contact, auth.

  Fix: Declare contact, auth, and rateLimit in ai-agent.json (and OpenAPI info.contact / securitySchemes).

6 checks short of a perfect 100. The fix lines above are the report — what to publish, at which path.

How scoring works · Recently graded · Back to the board