OutageDeck is listed as active in the registry but did not answer our last check. It exposes 14 tools.
Live status for 172 cloud and SaaS vendors from their official feeds. Is it you, or is it them?
Uptime history
91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 92 checks
14
Tools
read from the server
99 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 9
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 12 August 2026. No other catalogue keeps this.
25 Oct
a tool description was rewritten
update_custom_provider
25 Oct
a tool changed the parameters it asks for
update_custom_provider
18 Oct
3 tool descriptions were rewritten
get_provider_status, get_uptime, watch_provider
12 Sep
2 tool descriptions were rewritten
check_my_stack, get_incident_details
12 Sep
a tool changed the parameters it asks for
update_custom_provider
12 Aug
a tool description was rewritten
check_my_stack
OutageDeck does not always answer
Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.
run in your terminal
claude mcp add outagedeck-status --transport http https://outagedeck.com/api/mcpSettings → Connectors → Add custom connector, then paste this address
https://outagedeck.com/api/mcp~/.codex/config.toml
[mcp_servers.outagedeck-status]
url = "https://outagedeck.com/api/mcp".cursor/mcp.json
{
"mcpServers": {
"outagedeck-status": {
"url": "https://outagedeck.com/api/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"outagedeck-status": {
"type": "http",
"url": "https://outagedeck.com/api/mcp"
}
}
}Available tools 14
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
custom
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.
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.
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.
active
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.
fetch
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.
incident
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.
outage
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.
provider
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.
providers
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.
search
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.
stack
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.
uptime
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.
watch
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://outagedeck.com/api/mcp | streamable-http | answering | 99 ms | 3 min ago |
Alternatives to OutageDeck
same job, measured the same wayOutage.Me
by marcioyoshida
Live cloud/SaaS outages, provider reliability and exploited CVEs from official status pages and CISA
Outages Live
by boristane
Is it down? Live status and outages of 259 cloud, AI and developer providers, from status pages.
PulseWatch Vendor Status
by pulsewatch-api
Is this vendor down? Pay-per-call status for 1,700+ SaaS/cloud vendors from PulseWatch (x402 USDC).
Outage MCP
by reshadat
Live service outage data from 100+ status pages. Ask your AI if Cloudflare is down.
Is It Down API (60SecMonitor)
by isitdownapi-api
Is this vendor down? Pay-per-call status for 1,400+ SaaS/cloud vendors, up to 25 per call (x402).
Vendor Status MCP
by approj
Status-page map for 1,100+ SaaS/cloud vendors plus 15,700+ incidents. No API key.
UK Data: Is it down? Service status
by co-reliness
Is a service down right now? Live status, incidents and component health from official pages
Finland Company Check
by justiceua
Finland company checks: status, insolvency, LEI and sanctions from official registers.
OutageDeck — questions
Answers built from our own checks of this server.
What can OutageDeck do?
It exposes 14 tools, read directly from the server on our last check. Among them: add_custom_provider, check_my_stack, fetch, get_incident_details, get_outage_report, get_provider_status and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is OutageDeck working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 99 ms. The bar chart above shows every period we have measured.
The registry lists OutageDeck as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect OutageDeck?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does OutageDeck need an API key?
No. OutageDeck completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.