Outage.Me is a remote MCP server that gives an AI agent 8 tools, among them answer, deploy_check, exploited_vulnerabilities. It answers at https://outage.me/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 27 September 2026; the last check, on 12 November 2026, succeeded.
Live cloud/SaaS outages, provider reliability and exploited CVEs from official status pages and CISA
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
answer | 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 Inputs: q |
deploy_check | LIVE, from the 5-minute status poll: proceed true, false, or "unknown" for deploying to one provider (optionally one region), with the open incidents behind it and data_age_minutes. Fails safe: a stale poll, a failed fetch or an untracked p Inputs: provider, region |
exploited_vulnerabilities | 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 fir Inputs: limit, cve, vendor, product |
list_active_incidents | 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 aft Inputs: provider, region, component |
provider_reliability | 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 t Inputs: provider |
report_observation | Optional. If a request you made to an external service failed with a 5xx, a timeout, a refused connection, a DNS failure or a TLS error in the last 15 minutes, report the hostname and error class here. Only hosts listed in https://outage.me Inputs: host, error_class, region, report_token |
security_headlines | LIVE: headlines from eight security trade outlets (BleepingComputer, The Hacker News, SecurityWeek, The Record, Krebs on Security, …): headline, outlet, date and link only, never the article text. Use for 'any breach news about X', 'what at Inputs: days, query |
threat_advisories | LIVE: CISA's newest security advisories (CSAF: industrial control systems, medical devices, general vulnerabilities), each with its ID, affected vendors, CVEs, CVSS, the opening of CISA's mitigation text and the CISA link. Use for 'what did Inputs: limit, vendor |
Every block below points at https://outage.me/mcp. Pick your client and copy.
claude mcp add --transport http outage-me https://outage.me/mcp
{
"mcpServers": {
"outage-me": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://outage.me/mcp"]
}
}
}{
"mcpServers": {
"outage-me": {
"url": "https://outage.me/mcp"
}
}
}{
"servers": {
"outage-me": {
"type": "http",
"url": "https://outage.me/mcp"
}
}
}{
"context_servers": {
"outage-me": {
"url": "https://outage.me/mcp"
}
}
}{
"mcpServers": {
"outage-me": {
"serverUrl": "https://outage.me/mcp"
}
}
}{
"mcpServers": {
"outage-me": {
"url": "https://outage.me/mcp"
}
}
}name: Outage.Me
version: 0.0.1
schema: v1
mcpServers:
- name: Outage.Me
type: streamable-http
url: https://outage.me/mcp{
"mcpServers": {
"outage-me": {
"httpUrl": "https://outage.me/mcp"
}
}
}{
"mcpServers": {
"outage-me": {
"type": "http",
"url": "https://outage.me/mcp"
}
}
}{
"mcpServers": {
"outage-me": {
"url": "https://outage.me/mcp"
}
}
}goose://extension?url=https%3A%2F%2Foutage.me%2Fmcp&type=streamable_http&id=outage-me&name=Outage.Me
It answered our last check on 12 November 2026 in 445 ms. Over 4 checks since 27 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
8, as returned by the server's own tools/list on 16 November 2026: answer, deploy_check, exploited_vulnerabilities, list_active_incidents, provider_reliability, report_observation, security_headlines, threat_advisories.
It answered our last check on 12 November 2026 in 445 ms. Over 4 checks since 27 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://outage.me/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.marcioyoshida. Endpoint host: outage.me. ARD identifier: urn:air:io.github.marcioyoshida:mcp:outage-me.
First indexed 27 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.