OutageDeck

com.outagedeck/outagedeck-statusVersion 1.1.0

Live status for 172 cloud and SaaS vendors from their official feeds. Is it you, or is it them?

Status

Responds220 msNov 14, 2026, 14:09 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:09 UTC
Latency: 220 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://outagedeck.com/api/mcpResponds220 msNov 14, 2026, 14:09 UTC

No sign-in

Claude Code

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

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: outagedeck-status
Remote MCP server URL: https://outagedeck.com/api/mcp

Cursor

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

VS Code

code --add-mcp '{"name":"outagedeck-status","type":"http","url":"https://outagedeck.com/api/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

14 tools

Tools of OutageDeck
	Description		Read-only	Idempotent	Open world
`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 providers. The feed is read live before anything is saved, and it must be reachable from the public internet. Feeds behind authentication are set up on the account page instead, so credentials never travel through a conversation.	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 providers. The feed is read live before anything is saved, and it must be reachable from the public internet. Feeds behind authentication are set up on the account page instead, so credentials never travel through a conversation.	No	No	No	Yes
`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 link and a prefilled alert setup link.	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 link and a prefilled alert setup link.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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_provider_status. Use to read what the official source has actually said about an outage.	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_provider_status. Use to read what the official source has actually said about an outage.	No	Yes	Yes	No
`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. Use to answer "which vendors had outages recently?" or to compare vendor reliability.	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. Use to answer "which vendors had outages recently?" or to compare vendor reliability.	No	Yes	Yes	No
`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. When regions are present, reportedCodes lists published codes; notOperational lists impaired rows. If those rows are truncated, notOperationalCodes lists every impaired code. For an inventory feed, a reported code absent from the complete impaired list is operational; an unreported code has no published status. Withdrawn readings omit these lists. When only some services sit behind a feed OutageDeck could not re-read, services.notOperationalCount is null, confirmedNotOperationalCount counts the impaired services it could read, and unconfirmedServices names the rest.	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. When regions are present, reportedCodes lists published codes; notOperational lists impaired rows. If those rows are truncated, notOperationalCodes lists every impaired code. For an inventory feed, a reported code absent from the complete impaired list is operational; an unreported code has no published status. Withdrawn readings omit these lists. When only some services sit behind a feed OutageDeck could not re-read, services.notOperationalCount is null, confirmedNotOperationalCount counts the impaired services it could read, and unconfirmedServices names the rest.	No	Yes	Yes	No
`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 with partial outages counted as downtime, and total impaired durations.	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 with partial outages counted as downtime, and total impaired durations.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	Deletes one of the caller's custom providers and its stored incident history, freeing a slot on their plan. Requires an API key.	Yes	No	Yes	No
`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 incident"; use get_provider_status when the question is simply whether one named vendor is down right now.	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 incident"; use get_provider_status when the question is simply whether one named vendor is down right now.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`update_custom_provider`Renames one of the caller's custom providers, points it at a different status page, or pauses and resumes OutageDeck reading it. Requires an API key. A new address is read live before it is stored.	Renames one of the caller's custom providers, points it at a different status page, or pauses and resumes OutageDeck reading it. Requires an API key. A new address is read live before it is stored.	No	No	Yes	Yes
`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 delivery is allowed; otherwise a new owner-email watch is added or the request is refused with an explanation. A successful result always means delivery is allowed and reports the alert's channel. Other channels are set up on the account page; their destination URLs are never returned.	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 delivery is allowed; otherwise a new owner-email watch is added or the request is refused with an explanation. A successful result always means delivery is allowed and reports the alert's channel. Other channels are set up on the account page; their destination URLs are never returned.	No	No	Yes	No

Details

Registry status: Active
Published: Aug 2, 2026
Updated: Aug 2, 2026
Website: https://outagedeck.com/developers/mcp⁠ (opens in a new tab)
Repository: Not given
Categories (suggested): Cloud and infrastructureSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing