Skip to content
Official MCP RegistryListed

Outage.Me

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

First seen 2 Oct 2026. Evidence as of 4 Oct 2026.

6
Tools
From an anonymous probe
1
Source listings
Each with its own history
6
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
answerAsk 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.Read-only
deploy_checkLIVE, 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 provider is "unknown", never true. Planned maintenance alone doesn't block. Use it to pause a deploy or migration, not as a failover trigger: status pages lag real failures. Deterministic: no model in the loop.Read-only
exploited_vulnerabilitiesLIVE: 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. `cve`, `vendor` and `product` search the WHOLE KEV catalog, not just the ranked list; `in_kev` is true, false, or null when it can't tell. Deterministic: no model in the loop.Read-only
list_active_incidentsLIVE: 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. Filter by provider, region or component instead of reading the whole list; an untracked provider says so rather than returning an empty all-clear. Deterministic: no model in the loop. Prefer it over `answer`.Read-only
provider_reliabilityLIVE: 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`.Read-only
report_observationOptional. 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/agent/hosts.json. Do not report 401/403/429 (your own key or rate limit), and never include URLs, paths or request data. A report earns Ask quota only if it is confirmed (our own probe or other organizations agree).Changes data

Change history

  1. list_active_incidents: input schema changed (+component, +provider, +region)
  2. list_active_incidents: description changed (+"Filter by provider, region or component instead of reading the whole list; an untracked provider says so rather than returning an empty all-clear.")
  3. exploited_vulnerabilities: input schema changed (+cve, +product, +vendor)
  4. exploited_vulnerabilities: description changed (+"`cve`, `vendor` and `product` search the WHOLE KEV catalog, not just the ranked list; `in_kev` is true, false, or null when it can't tell.")
  5. deploy_check: tool added
  6. server instructions changed (+"How to connect: https://outage.me/connect")
Source listings
SourceListingFirst seenLast seenVersions
Official MCP Registryio.github.marcioyoshida/outage-me2 Oct 20263 Oct 20261