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。

  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。