OutageDeck
com.outagedeck/outagedeck-statusLive status for 172 cloud and SaaS vendors from their official feeds. Is it you, or is it them?
Tools · 14
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., "c…
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. Retu…
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 w…
Full detail for one incident: the provider's own update timeline in chronological order, affected services, severity, and resolution state. Pass the incident slug returned by list_active_incidents or …
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 outage…
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 t…
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 n…
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 …
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 k…
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.
Deletes one of the caller's custom providers and its stored incident history, freeing a slot on their plan. Requires an API key.
Starts sending the caller outage alerts for one provider, either from the tracked catalog or from their own custom providers. Requires an API key. Alerts are emailed to the account address; the other …
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…
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.
Prompts · 2
Work out whether a failure is your own change or a vendor outage: check every vendor the stack depends on, dig into anything not operational, and report a verdict with citations.
Work out which vendors this project actually depends on, then set up outage alerts for them, registering any vendor OutageDeck does not track yet from its own status page. Needs an API key on the conn…
Similar MCP servers embedding-nearest
How to use
Add to your Claude Desktop / Cursor / Cline MCP config:
{
"mcpServers": {
"outagedeck": {
"url": "https://outagedeck.com/api/mcp",
"transport": "streamable-http"
}
}
}