mcpbeat Sign in

Outages Live MCP Server

answering

Outages Live is answering right now. Last checked moments ago. It exposes 5 tools.

Is it down? Live status and outages of 259 cloud, AI and developer providers, from status pages.

Uptime history 5 days of history
5 days agonow
100.0%
Uptime 24h
92 of 92 checks
5
Tools
read from the server
480 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 6 November 2026. No other catalogue keeps this.

6 Nov a tool description was rewritten list_feed

Nothing serious here today

Today is the operative word: we check Outages Live every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add outages-live --transport http https://outages.live/mcp
Settings → Connectors → Add custom connector, then paste this address
https://outages.live/mcp
~/.codex/config.toml
[mcp_servers.outages-live]
url = "https://outages.live/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "outages-live": {
      "url": "https://outages.live/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "outages-live": {
      "type": "http",
      "url": "https://outages.live/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

report
report_affected
Tell outages.live that an outage affects your user, as the "I'm affected" button on the outage page does. Call it only when your user says that the outage affects them, never on your own. Give the outage id that get_provider or list_feed returns. The count shows on the outage page at once, and each user counts once for each outage, so a second call changes nothing. Returns the new affected count.
report_outage
Report that a provider does not work for your user, as "Report an outage" on outages.live does, also when its status page shows no problem. Call it only when your user asks you to report it, never on your own. The outages.live team reviews each report, and only approved reports show on outages.live, in the API, and in get_provider. One report for each provider each hour.
feed
list_feed
List incidents across providers, the most recently updated first. By default only incidents that are open now. Narrow it with providers, category, and a minimum impact; set state to recent to add incidents resolved in the last days. When the server URL sets filters, they apply to each argument you do not give.
provider
get_provider
Get one provider (for example GitHub, AWS, Vercel, OpenAI): a one-line verdict on whether it reports a problem now, its active incidents, what people reported about it on outages.live in the last 24 hours (reviewed reports only, with a spike flag when many arrive in an hour), maintenance in progress, its last 10 incidents, and 90 days of daily history. Give region or component to keep only active incidents that name it, for example us-east-1 or Actions. Call it when a request to the provider fails, before you change code. An unknown name returns every tracked id.
send
send_feedback
Send feedback to the outages.live team: a provider to add, data that looks wrong (a status that does not match the provider's own page, a missing or stale incident), or an idea. The team reads every message. Send only what the user agreed to share.

Endpoints

URLTransportStateLatencyChecked
https://outages.live/mcp streamable-http answering 378 ms 0 min ago

Alternatives to Outages Live

same job, measured the same way
Outage MCP
by reshadat

Live service outage data from 100+ status pages. Ask your AI if Cloudflare is down.

54 installs/wk local only
Outage.Me
by marcioyoshida

Live cloud/SaaS outages, provider reliability and exploited CVEs from official status pages and CISA

8 tools answering
Is It Down
by kaiv

Is GitHub, npm, Cloudflare or your AI provider down right now? 20 status pages, one call.

3 tools answering
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

10 tools answering
Downtester Status
by downtester

Live service status, active incidents, search, and outage history from Downtester.

answering
AI Down: live AI service status
by aidown

Is Claude, ChatGPT, Gemini, Cursor or Copilot down? Live status from API probes and user reports.

1 tools answering
Statuser
by statuser-cloud

Monitor services, manage incidents and status pages in Statuser.cloud from your AI assistant.

768 installs/wk answering
AI Provider Status
by lazymac2x

Cloudflare Workers MCP server: ai-provider-status

3 tools answering

Outages Live — questions

Answers built from our own checks of this server.

What can Outages Live do?
It exposes 5 tools, read directly from the server on our last check. Among them: get_provider, list_feed, report_affected, report_outage, send_feedback. 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 Outages Live working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 480 ms. The bar chart above shows every period we have measured.
How do I connect Outages Live?
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 Outages Live need an API key?
No. Outages Live completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Outages Live?
It answers our handshake in 480 ms on average, which is faster than 25% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.