
Outage Mcp
io.github.reshadatPublished by GitHub account reshadatv0.1.1Updated Nov 3, 2026
Live service outage data from 100+ status pages. Ask your AI if Cloudflare is down.
Overview
Local MCP server that gives an assistant live outage data from 100+ service status pages via whatbroke.today, so it can answer "is X down?".
- What you can do
- Check current outages across all monitored services, active incidents first
- Look up the status and recent history of one named service
- Read full detail for a single incident, including AI root-cause analysis when available
- Get outage leaderboards and totals for a period
- List the 100+ services being monitored
- When to use it
- Useful when you want an assistant to answer questions about whether a cloud provider, developer platform or payment service is currently down, or to summarize recent incidents and which services break most often.
- Requirements
- Runs locally over stdio, typically launched with npx from the npm package outage-mcp, so Node.js and network access are needed. No API keys or signup are required.
Installation
In SourceWeft
- Open Outage Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
outage-mcp
Ask your AI if Cloudflare is down.
An MCP server that gives Claude, Cursor, and any MCP client live outage data from whatbroke.today, which monitors 100+ service status pages continuously. No API keys, no signup.
Install
Claude Desktop / Claude Code — add to your MCP config:
Claude Code one-liner:
Works the same in Cursor, Windsurf, and any MCP-capable client.
Tools
Notes
- Data comes from whatbroke.today, which aggregates official status pages and adds AI summaries and RCAs.
- The upstream API is rate-limited to 5 requests/min per IP; this server caches responses for 60 seconds, which in practice keeps you under it.
- Severity
resolvedmeans the provider closed the incident. Everything else is treated as active.
Development
MIT. Built by Reshadat Ali between 10pm and 1am.
Source: README.md at commit 4fc0b48
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts