Outage.Me

io.github.marcioyoshidaPublished by GitHub account marcioyoshidav1.3.0Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that gives an assistant live cloud and SaaS outage data, provider reliability, exploited CVEs and CISA advisories.

What you can do
Check live cloud and SaaS incidents, filtered by provider, region or component, and get a deploy go/no-go verdict per provider or region with the incidents behind it and data age. Compare providers by reliability index, incident count and median recovery time. Look up CVEs exploited in the wild from CISA KEV, ranked patch-first, and read CISA's newest advisories with affected vendors, CVEs and CVSS. Browse headlines from security trade outlets. Ask a free-form question about the live monitor for a cited answer, and optionally report a recent failed request to a listed host.
When to use it
Useful when an assistant needs current outage or reliability information beyond its training cutoff, such as answering whether a provider is down, choosing between providers, or deciding whether to deploy. Also suited to patch prioritization and tracking CISA advisories and security news.
Requirements
A remote streamable HTTP endpoint at outage.me; no package or runtime install. No authentication is declared for the core tools. The answer tool needs sign-in or an API key and is quota-limited (Free plan 10/day, Pro 100/day). Network access to the endpoint is required.
Before you install
The answer tool is a language-model call and can be wrong; check its confidence and citations. It also requires sign-in or an API key and has daily quotas. report_observation sends hostnames and error classes to a third party and is restricted to listed hosts; do not report 401/403/429 errors. deploy_check returns unknown rather than true when data is stale or a provider is untracked.

Installation

In SourceWeft

  1. Open Outage.Me in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.marcioyoshida%2Foutage-me/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "outage-me": {
      "type": "http",
      "url": "https://outage.me/mcp"
    }
  }
}

Tools

8

list_active_incidents

Active cloud/SaaS 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 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`.

Parametersregionprovidercomponent

provider_reliability

Provider reliability track record

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`.

Parametersprovider

exploited_vulnerabilities

Actively exploited CVEs, patch-first

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. `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.

Parameterscvelimitvendorproduct

threat_advisories

CISA security advisories (ICS, medical, vulnerability)

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 CISA advise this week' or 'any CISA advisory for <vendor>'. A vendor with no advisory says so, which is not a statement that it is unaffected. Deterministic: no model in the loop.

Parameterslimitvendor

security_headlines

Security news headlines (breaches, attacks, exploits)

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 attacks are in the news this week'; read the article at its link before relying on it. Deterministic: no model in the loop.

Parametersdaysquery

deploy_check

Deploy gate: is it safe to deploy to this provider now?

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 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.

Parametersregionproviderrequired

answer

Ask the outage.me analyst (sign-in or API key)

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.

Parametersqrequired

report_observation

Report an API failure you observed (optional)

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/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).

Parametershostrequiredregionerror_classrequiredreport_token

Version history

3
  1. v1.3.0LatestSep 27, 2026
  2. v1.2.1Sep 27, 2026
  3. v1.2.0Sep 27, 2026

Score

83% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.