OutageDeck is an MCP server with 14 tools an agent can call, among them add_custom_provider, check_my_stack, fetch. It answers at https://outagedeck.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Live status for 172 cloud and SaaS vendors from their official feeds. Is it you, or is it them?
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 provi Inputs: url, name |
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 and a Inputs: providers |
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. Inputs: id |
get_incident_details | 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 get_provider_status. Use to read what th Inputs: incident |
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 Inputs: days |
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 Inputs: provider |
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 co Inputs: provider, days |
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. Inputs: severity |
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. |
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. Inputs: provider |
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 incid Inputs: query |
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 OutageDec Inputs: query |
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. Inputs: provider, name, url, state |
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. Alerts are emailed to the account address; the other channels (Slack, Teams, Discord, webhook Inputs: provider |
Every block below points at https://outagedeck.com/api/mcp. Pick your client and copy.
claude mcp add --transport http outagedeck https://outagedeck.com/api/mcp
{
"mcpServers": {
"outagedeck": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://outagedeck.com/api/mcp"]
}
}
}{
"mcpServers": {
"outagedeck": {
"url": "https://outagedeck.com/api/mcp"
}
}
}{
"servers": {
"outagedeck": {
"type": "http",
"url": "https://outagedeck.com/api/mcp"
}
}
}{
"context_servers": {
"outagedeck": {
"url": "https://outagedeck.com/api/mcp"
}
}
}{
"mcpServers": {
"outagedeck": {
"serverUrl": "https://outagedeck.com/api/mcp"
}
}
}{
"mcpServers": {
"outagedeck": {
"url": "https://outagedeck.com/api/mcp"
}
}
}name: OutageDeck
version: 0.0.1
schema: v1
mcpServers:
- name: OutageDeck
type: streamable-http
url: https://outagedeck.com/api/mcp{
"mcpServers": {
"outagedeck": {
"httpUrl": "https://outagedeck.com/api/mcp"
}
}
}{
"mcpServers": {
"outagedeck": {
"type": "http",
"url": "https://outagedeck.com/api/mcp"
}
}
}{
"mcpServers": {
"outagedeck": {
"url": "https://outagedeck.com/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Foutagedeck.com%2Fapi%2Fmcp&type=streamable_http&id=outagedeck&name=OutageDeck
It answered our last check on 18 October 2026 in 202 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by outagedeck.com and served from outagedeck.com, the vendor's own domain: https://outagedeck.com/api/mcp.
14, as returned by the server's own tools/list on 31 August 2026: add_custom_provider, check_my_stack, fetch, get_incident_details, get_outage_report, get_provider_status, get_uptime, list_active_incidents, and 6 more.
It answered our last check on 18 October 2026 in 202 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://outagedeck.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.outagedeck. Endpoint host: outagedeck.com. ARD identifier: urn:air:com.outagedeck:mcp:outagedeck-status.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.