Outages Live
REMOTE · OUTAGES.LIVE
Is it down? Live status and outages of 259 cloud, AI and developer providers, from status pages.
Available components
Last scanned (4 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 918 tokens (~183/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://outages.live/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=outages.live | CN=WE1,O=Google Trust Services,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 509aaa1afa50cbe50e7c5a797ba0720c |
| SANs: outages.live, *.outages.live | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of outages.live. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| live. | present | 4724, 36322 | 8, 8 | Verified |
| outages.live. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://outages.live/mcp | Verified | 200 | |
| http (plaintext) | http://outages.live/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_provider Get a provider's status ~202
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.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | – | Optional component or product to match, for example Actions, S3, Chat Completions |
| provider | string | yes | Provider id or name, for example github, aws, Google Cloud, openai |
| region | string | – | Optional region to match, for example us-east-1 |
No output schema declared.
No examples provided.
list_feed List provider incidents ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| days | integer | – | Window for state recent |
| impact | string | – | Minimum impact: partial_outage keeps partial and major outages |
| include_maintenance | boolean | – | – |
| limit | integer | – | – |
| providers | array | – | Provider ids or names, for example github, vercel |
| state | string | – | active: open now. recent: everything updated in the last days. |
No output schema declared.
No examples provided.
report_affected Say an outage affects your user ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| outage_id | string | yes | The outage id from get_provider or list_feed, for example github-abc123 |
No output schema declared.
No examples provided.
report_outage Report a provider outage ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | What does not work: api (an API or service), website (the website or dashboard), sign_in, or other |
| note | string | – | Optional short note from your user about what they see, for example Pushes time out |
| provider | string | yes | Provider id or name, for example github, aws, openai |
No output schema declared.
No examples provided.
send_feedback Send feedback to outages.live ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | missing_provider, wrong_data, idea, or other |
| message | string | yes | What to add, what looks wrong and where, or the idea |
| provider | string | – | Optional provider the feedback is about, tracked or not, for example stripe |
No output schema declared.
No examples provided.
How do I install the Outages Live MCP server?
Outages Live is a hosted endpoint at https://outages.live/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · outages.live
claude mcp add --transport http boristane-outages-live 'https://outages.live/mcp'
What is the Outages Live MCP server?
Outages Live is an MCP server listed in the public MCP registry as io.github.boristane/outages-live. Is it down? Live status and outages of 259 cloud, AI and developer providers, from status pages. This page covers its hosted endpoint (https://outages.live/mcp).
Is the Outages Live MCP server safe to use?
Outages Live scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Outages Live MCP server expose?
Outages Live exposes 5 tools: get_provider, list_feed, send_feedback, report_affected, report_outage. Their descriptions and schemas cost roughly 750 tokens of context every time the server is loaded.
Does the Outages Live MCP server require authentication?
No. We connected to Outages Live without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Outages Live MCP server still maintained?
Outages Live is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.