openstatus.dev agentic web readiness

A+ Manifest validity: 75% (3/4 valid, 3 errors, 10 warnings) · Surface score 65 (coverage 40 + breadth 15 + conformance 10). 7 standards observed across 4 of 9 steps; 4 manifests present (+ robots.txt, security.txt), 3 errors, 10 warnings. Checked 2026-10-25 19:17:05 UTC via www.openstatus.dev. This grades the agent-facing files published at openstatus.dev, not the organisation's products.

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

Coverage by step

Manifests

{
  "$schema": "https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json",
  "name": "dev.openstatus/openstatus",
  "title": "Openstatus",
  "version": "1.0.0",
  "description": "Openstatus and what it offers to agents",
  "websiteUrl": "https://openstatus.dev/",
  "icons": [
    {
      "src": "https://openstatus.dev/icon.png",
      "mimeType": "image/png",
      "sizes": [
        "180x180"
      ]
    }
  ],
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://openstatus.dev/mcp",
      "supportedProtocolVersions": [
        "2025-11-25",
        "2025-06-18",
        "2025-03-26"
      ]
    }
  ]
}

What an agent can call

• MCP endpoint https://api.openstatus.dev/mcp (streamable-http), tools: list_status_pages, list_status_reports, create_status_report, append_status_report_update, resolve_status_report, update_status_report, create_maintenance, update_maintenance — from /.well-known/mcp.json
• MCP endpoint https://api.openstatus.dev/mcp (streamable-http), tools: list_status_pages, list_status_reports, create_status_report, append_status_report_update, resolve_status_report, update_status_report, create_maintenance, update_maintenance — from /.well-known/mcp/server-card.json
• API description https://api.openstatus.dev/openapi.json (application/json)
• API description https://www.openstatus.dev/docs (text/html)
• API description https://www.openstatus.dev/.well-known/mcp/server-card.json (application/json)
• API description https://www.openstatus.dev/docs/reference/mcp-server/ (text/html)
• API description https://www.openstatus.dev/openapi.json (service-desc)
• llms.txt: openstatus, 323 links, llms-full.txt present
• robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed

Standards observed

• llms.txt https://openstatus.dev/llms.txt
• Content Signals Policy https://openstatus.dev/robots.txt
• api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://openstatus.dev/.well-known/api-catalog
• Agent Skills https://openstatus.dev/.well-known/agent-skills/index.json
• Markdown for Agents https://openstatus.dev/
• MCP Server Cards (SEP-2127)
• Model Context Protocol

Cheapest next steps

1. Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch (emerging spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "ard", "domain": "openstatus.dev"}))
2. AGENTS.md: instructions for coding agents working on or with the site
   Generate starter /AGENTS.md for openstatus.dev

   # Openstatus for agents
   
   Openstatus and what it offers to agents
   
   ## Read the data, not the HTML
   - Index: https://openstatus.dev/llms.txt
   - API description: https://openstatus.dev/openapi.json
   - Discovery catalog: https://openstatus.dev/.well-known/ard.json
   
   ## Calling
   - MCP server (Streamable HTTP): https://openstatus.dev/mcp
   - Rate limits and authentication: describe them here
   
   ## Conventions
   - How to cite or attribute content
   - What not to do (no scraping of /account/, no automated sign-ups, etc.)
   
   Contact: security@openstatus.dev
   

Agent pre-flight & practical readiness

Preferred mode: mcp (fallback openapi). Call the MCP endpoint at https://api.openstatus.dev/mcp first. Do not scrape the HTML when a tool can answer.

Fetch: POST https://api.openstatus.dev/mcp POST a JSON-RPC tools/list, or server/discover on the 2026-07-28 revision, before reading HTML.

Practical readability: exa_parsable yes, markdown negotiation yes, render markdown_native, HTML quality high, first content at byte 0.

AI crawler posture: search_allowed_training_blocked · Assistant access: OpenAI allowed, Anthropic allowed, Google allowed, Perplexity allowed, Exa allowed.

Readiness subscores: reach 20/20, readability 30/30, capabilities 31/35, conformance 10/15, total 91/100, grade A+.

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). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. 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