Skip to content
OutageDeck logo

OutageDeck MCP server

Which servers in the official MCP registry are OutageDeck's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-20

← Back to OutageDeck

Whose server it is
  • Registry namecom.outagedeck/outagedeck-statusverified in the MCP registry

The registry name sits under outagedeck.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-20
  • Stateanswerschecked 2026-10-20
  • Tools14
  • Server calls itselfoutagedeck
  • Server version1.1.2
  • Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 185 ms.

Measured dailydaily checks: 1, the first on 2026-10-20
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer233 ms
  • Space in an agent's context≈ 2,096 tokensthe definitions of all its tools (14), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Every tool passes all six checks.

Worth a look

  • Tools that change data, on a server that answers without a sign-in: add_custom_provider, update_custom_provider, remove_custom_provider

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The state of vendors' MCP servers: method and numbers →

Tools it offers14 tools · read 2026-10-20
  • 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…

  • check_my_stack

    One verdict across up to 12 providers: whether any vendor in the list is reported as having 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…

  • 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_incident_details

    Full detail for one incident: updates from the official incident source in chronological order, the services OutageDeck matched to it, severity, and resolution state. Pass the incident slug returned by list_active_incidents or…

  • get_uptime

    Independent uptime record for one provider over a trailing window (7-90 days, default 30), computed from OutageDeck's readings of the official source that publishes the provider's status: share of time free of major outages, strict uptime…

  • get_outage_report

    A reliability summary across every tracked provider over a trailing window (7-90 days, default 30): incident totals, severity and category breakdowns, the providers hit hardest by major outages, and the longest-running severe incidents…

  • 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…

  • list_custom_providers

    Lists the custom providers on the caller's own OutageDeck account: vendors they registered themselves by pointing at a status feed we do not track in the public catalog. Requires an API key, and only ever returns that key owner's providers.

  • add_custom_provider

    Registers a vendor OutageDeck does not track by pointing at its Statuspage or Instatus status page, so it joins the caller's account with live status, incident history, and alerting. Requires an API key and a plan that includes custom…

  • update_custom_provider

    Renames one of the caller's custom providers, points it at a different status page, or pauses and resumes its checks. Requires an API key. A new address is read live before it is stored.

  • remove_custom_provider

    Deletes one of the caller's custom providers and its stored incident history, freeing a slot on their plan. Requires an API key.

  • watch_provider

    Starts sending the caller outage alerts for one provider, either from the tracked catalog or from their own custom providers. Requires an API key. A new watch is added to the owner's email alert. An existing alert counts only when…

  • search

    Search everything OutageDeck tracks: cloud and SaaS providers, and their incident history. Returns citable results with stable ids for the fetch tool. Use for open questions like "who had outages last week" or "find the GitHub Actions…

  • fetch

    Retrieve the full text of one search result by its id: a provider's current status with its services and open incidents, or an incident's complete timeline. Ids come from the search tool.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "outagedeck-status": {
      "type": "http",
      "url": "https://outagedeck.com/api/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.