Outage.Me
REMOTE · OUTAGE.ME · 2 COMPONENTS · SCANNED SEP 28
Live cloud/SaaS outages, provider reliability and exploited CVEs from official status pages and CISA
Available components
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 Security74
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 483 tokens (~120/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the Outage.Me MCP server?
Outage.Me is a hosted endpoint at https://outage.me/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 · outage.me
claude mcp add --transport http marcioyoshida-outage-me 'https://outage.me/mcp'
{
"mcpServers": {
"marcioyoshida-outage-me": {
"url": "https://outage.me/mcp"
}
}
} {
"servers": {
"marcioyoshida-outage-me": {
"type": "http",
"url": "https://outage.me/mcp"
}
}
} [mcp_servers.marcioyoshida-outage-me] url = "https://outage.me/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"marcioyoshida-outage-me": {
"type": "remote",
"url": "https://outage.me/mcp",
"enabled": true
}
}
} openclaw mcp add marcioyoshida-outage-me --url 'https://outage.me/mcp' --transport streamable-http
mcp_servers:
marcioyoshida-outage-me:
url: "https://outage.me/mcp" {
"McpServers": {
"marcioyoshida-outage-me": {
"Transport": "http",
"Url": "https://outage.me/mcp"
}
}
} assistant mcp add marcioyoshida-outage-me -t streamable-http -u 'https://outage.me/mcp'
{
"mcpServers": {
"marcioyoshida-outage-me": {
"type": "http",
"url": "https://outage.me/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 71
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 28 Sept 2026 · Probed https://outage.me/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=outage.me | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 14 Sept 2026 | 30 Mar 2027 | RSA 2048 | SHA256-RSA | b1c650c5ce254a42f1c2c7452991e23 |
| SANs: outage.me, www.outage.me, app.outage.me | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of outage.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| me. | present | 45352 | 8 | Verified |
| outage.me. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://outage.me/mcp | Verified | 200 | |
| http (plaintext) | http://outage.me/mcp | HTTPS enforced | 301 | https://outage.me/mcp |
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 →
answer Ask the outage.me analyst (sign-in or API key) ~109
Ask a free-form question about the live monitor and get a cited answer. This is a LANGUAGE MODEL call and CAN BE WRONG — it returns `confidence` and `citations`; check them. Needs sign-in (connect to https://outage.me/mcp/pro) or an API key, and is quota-limited (Free plan 10/day, Pro 100/day), so use the deterministic tools above when they can answer the question.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | The question, in natural language. |
No output schema declared.
No examples provided.
exploited_vulnerabilities Actively exploited CVEs, patch-first ~106
LIVE: CVEs being exploited in the wild (CISA KEV), ranked patch-first by CVSS × EPSS exploitation probability × known ransomware use, with CISA due date, patch availability and the factors behind each rank. Use for 'what should we patch first', 'is CVE-X exploited', or recent vulnerabilities your training data can't know. Deterministic: no model in the loop.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Optional. Max rows, default 10. |
No output schema declared.
No examples provided.
list_active_incidents Active cloud/SaaS incidents ~92
LIVE: cloud and SaaS incidents open right now (AWS, Azure, GCP, Cloudflare, GitHub, Stripe, …), quoted from each provider's own status page with a link, refreshed several times a day. Use for 'is X down', 'why is X failing', or anything after your training cutoff. Deterministic: no model in the loop. Prefer it over `answer`.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
provider_reliability Provider reliability track record ~85
LIVE: reliability index, incident count and median recovery time per cloud/SaaS provider over the current window, from their official status pages. Use for 'how reliable is X' or 'which provider is more stable'. Deterministic: no model in the loop. Prefer it over `answer`.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | – | Optional. Filter to one provider by name. |
No output schema declared.
No examples provided.
What is the Outage.Me MCP server?
Outage.Me is an MCP server listed in the public MCP registry as io.github.marcioyoshida/outage-me. Live cloud/SaaS outages, provider reliability and exploited CVEs from official status pages and CISA. This page covers its hosted endpoint (https://outage.me/mcp).
Is the Outage.Me MCP server safe to use?
Outage.Me scores 71 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 Outage.Me MCP server expose?
Outage.Me exposes 4 tools: list_active_incidents, provider_reliability, exploited_vulnerabilities, answer. Their descriptions and schemas cost roughly 392 tokens of context every time the server is loaded.
Does the Outage.Me MCP server require authentication?
No. We connected to Outage.Me without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Outage.Me MCP server still maintained?
Outage.Me is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.