Outage.Me

io.github.marcioyoshida由 GitHub 账号 marcioyoshida 发布v1.3.0更新于 Oct 25, 2026

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

已验证Streamable HTTP可网页运行云端与基础设施安全与监控

概览

AI 生成的概览

远程 MCP 服务器,为助手提供云与 SaaS 实时故障、服务商可靠性、在野利用漏洞和 CISA 公告。

可以做什么
查询云与 SaaS 实时故障,可按服务商、区域或组件筛选,并获取针对某服务商或区域的部署放行判断及背后故障和数据时效。按可靠性指数、故障次数和中位恢复时间比较服务商。查询 CISA KEV 中在野利用的 CVE,按优先修补排序,并阅读 CISA 最新公告及其受影响厂商、CVE 和 CVSS。浏览安全行业媒体头条。就实时监控提出自由问题并获得带引用的回答,可选上报近期对指定主机的失败请求。
适用场景
适合需要超出训练截止时间的实时故障或可靠性信息的场景,例如判断某服务商是否宕机、在服务商之间做选择,或决定是否部署。也适合漏洞修补优先级排序以及跟踪 CISA 公告和安全新闻。
运行要求
位于 outage.me 的远程 streamable HTTP 端点,无需安装包或运行时。核心工具未声明身份验证。answer 工具需要登录或 API 密钥,并有配额限制(免费版每天 10 次,Pro 每天 100 次)。需要能访问该端点的网络。
安装前请注意
answer 工具是语言模型调用,可能出错,应核对其 confidence 和 citations。它还需要登录或 API 密钥,并有每日配额。report_observation 会把主机名和错误类别发送给第三方,且仅限清单内主机;不要上报 401/403/429 错误。数据过期或服务商未被跟踪时,deploy_check 返回 unknown 而非 true。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Outage.Me,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.marcioyoshida%2Foutage-me/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

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

工具

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

输入参数regionprovidercomponent

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

输入参数provider

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.

输入参数cvelimitvendorproduct

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.

输入参数limitvendor

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.

输入参数daysquery

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.

输入参数regionprovider必填

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.

输入参数q必填

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

输入参数host必填regionerror_class必填report_token

版本历史

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

评分

已满足适用检查项的 83%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分

    请声明包含 README 的 GitHub 仓库,或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证不适用

    托管服务按其提供方的条款使用,因此这里不要求许可证。此检查项不计入百分比。