OutageDeck is answering right now. Last checked 14 min ago. 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
48 days of history · worst day 53%
48 days agonow
100.0%
Uptime 24h
91 of 91 checks
14
Tools
read from the server
227 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 4
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 12 August 2026. No other catalogue keeps this.
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 90.3% 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 14 min ago.
run in your terminal
claude mcp add outagedeck-status --transport http https://outagedeck.com/api/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"outagedeck-status": {
"url": "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
{
"mcpServers": {
"outagedeck-status": {
"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 its checks. 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.
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 own observations of the vendor's official feed: 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. Alerts are emailed to the account address; the other channels (Slack, Teams, Discord, webhook) are set up on the account page, so no webhook URL ever has to be shared in a conversation.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://outagedeck.com/api/mcp | streamable-http | answering | 241 ms | 14 min ago |
Alternatives to OutageDeck
same job, measured the same wayVendor Status MCP
by approj
Live status-page map for 1,127 SaaS/cloud vendors plus 15,418 historical incidents.
Outage MCP
by reshadat
Live service outage data from 100+ status pages. Ask your AI if Cloudflare is down.
Capawesome
by capawesome
The official MCP server for Capawesome documentation and Capawesome Cloud.
Yocoolab
by jonahbkerr
Pin visual feedback on any live web page and send it to Claude Code, Cursor or your AI agent.
I
Dxb Data
by dxbdata
Official Dubai real estate data: live prices and rental yields by area, from the DLD.
FilingDesk Data
by filingdesk
US LLC filing fees, deadlines, and name checks for all 50 states — from official sources.
LEGAION Verifier
by legaion
Checks legal citations against the official register they should come from, and records it.
Zetadeck
by zetadeck
One workspace for tasks, CRM, docs, and live runway from your bank feed.
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 91 of 91 checks got a reply (100.0%), average response time 227 ms. The bar chart above shows every period we have measured.
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 with the file path 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.
How fast is OutageDeck?
It answers our handshake in 227 ms on average, which is faster than 62% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.