Connect

The server speaks Streamable HTTP at https://outagedeck.com/api/mcp. It is stateless and keyless by default, so setup is one line.

claude mcp add --transport http outagedeck https://outagedeck.com/api/mcp

{
  "mcpServers": {
    "outagedeck": {
      "url": "https://outagedeck.com/api/mcp"
    }
  }
}

curl -X POST https://outagedeck.com/api/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "get_provider_status",
      "arguments": { "provider": "aws" }
    }
  }'

The tools

5 read-only tools cover the questions agents actually ask. Provider arguments accept slugs, vendor names, or product names — "claude" resolves to Anthropic, "gcp" to Google Cloud.

• get_provider_status

  Live status for one tracked provider: overall state, non-operational services, and open incidents, read from the vendor's official status feed. Accepts a slug, provider name, or product name (e.g. "claude" resolves to Anthropic). Use this first for any "is X down?" question.

• check_my_stack

  One verdict across up to 12 providers: whether any vendor in the list is reporting a problem right now. Use before debugging an integration failure to answer "is it us or them?" in a single call. Returns a shareable status-board link.

• list_active_incidents

  Every incident currently open across all tracked providers, most severe first. Optionally filter by severity (critical, major, minor, maintenance). Use to answer "what is down right now?" across the whole cloud landscape.

• get_uptime

  Independent uptime record for one provider over a trailing window (7-90 days, default 30), computed from OutageDeck's own observations of the vendor's official feed: share of time free of major outages, strict uptime with partial outages counted as downtime, and total impaired durations.

• search_providers

  Find tracked providers by name, product name, or fragment ("postgres", "auth", "claude"). Returns slugs to use with the other tools plus each match's current status. Use when a provider argument did not resolve or to discover what OutageDeck tracks.

Limits and keys

Keyless calls share the public API's anonymous hourly limit per IP — plenty for an agent that checks status when something fails. Connecting, listing tools, and pings never count against it; only tool calls do. If your agents check status constantly, an API key raises the limit and every paid plan includes one:

claude mcp add --transport http outagedeck https://outagedeck.com/api/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

The same key works on the REST API. Keys are created on your account page — the free tier includes email outage alerts for five providers, no card required.

What the answers are made of

• Every status comes from the provider's own official status feed, ingested about every 10 minutes. OutageDeck reports what vendors publish — it does not probe or crowd-source.
• Uptime numbers are OutageDeck's independent record of those feeds, with major and partial outages reported separately so a regional event never reads as a platform-wide one.
• The server is read-only and stateless: no sessions, no conversation data received, nothing stored about the caller beyond standard rate accounting.
• Tool responses include OutageDeck links so your agent can cite a page a human can open — the same pages, API, and outage alerts cover everything the tools return.