Statuspage MCP by usefulapi

io.usefulapi由 usefulapi.io 發布官方發布者v1.3.4更新於 Nov 7, 2026

Read pages, components, incidents and maintenances; create and update incidents in Statuspage.

發布方自己的服務:Ably MCP by usefulapi

已驗證Streamable HTTP可網頁執行效率與工作流安全與監控

概覽

AI 產生的概覽

託管式 Statuspage 連接器,讓助理讀取狀態頁、元件、可用率、事件與維護計畫,並建立或更新事件和元件狀態。

可以做什麼
  • 列出並檢視狀態頁、頁面資料、元件群組及元件目前狀態
  • 依日期範圍讀取元件可用率,以及頁面上顯示的指標
  • 列出、搜尋並檢視事件詳情,包括未解決事件及其完整更新紀錄
  • 列出已排定、即將開始與進行中的維護,並依類型統計訂閱者數量
  • 寫入線上頁面:設定元件狀態、建立事件或發布事件更新
適用情境
適合讓助理回答關於公開狀態頁的問題,例如哪些元件異常、有哪些未解決事件、上個月可用率如何;也適合在不開啟 Statuspage 後台的情況下發布事件更新與修改元件狀態。
執行需求
遠端 MCP 端點,使用 streamable HTTP,無需本機安裝。透過 OAuth 登入,首次連線時需提供 Statuspage API 金鑰(在 Statuspage 使用者選單的 API info 取得),伺服器會驗證並依使用者儲存。用戶端設定中不要填入 API 金鑰或 Authorization 標頭。需要方案:免費版每月 50 次工具呼叫。
安裝前請注意
有三個工具會寫入公開的線上狀態頁:設定元件狀態、建立事件、發布事件更新。變更會立即對訪客可見,建立或更新事件預設還會通知訂閱者,重複呼叫會產生重複事件或重複時間軸項目。Statuspage API 金鑰會交給第三方託管服務。付費方案透過 Stripe 結帳連結付款,取消後目前週期不退款。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Statuspage MCP by usefulapi,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.usefulapi%2Fstatuspage/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "statuspage-by-usefulapi": {
      "type": "http",
      "url": "https://statuspage.usefulapi.io/mcp"
    }
  }
}

README

Statuspage MCP by usefulapi

Use your Statuspage account from Claude, Cursor, or any MCP client. Read status pages, components, uptime, incidents, maintenances and metrics, and create or update incidents and component status. Hosted, no local install: connect with your own credentials.

Live endpoint: https://statuspage.usefulapi.io/mcp · Homepage: https://usefulapi.io

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://statuspage.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http statuspage https://statuspage.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "mcpServers": {    "statuspage": {      "url": "https://statuspage.usefulapi.io/mcp"    }  }}

Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Statuspage credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/statuspage/

On first connect you provide a Statuspage API key (Statuspage → user menu → API info). The server validates it and stores it per user. No keys go in config files.

Tools

ToolTypeWhat it does
statuspage_list_pagesreadList status pages
statuspage_get_pagereadGet a status page
statuspage_list_componentsreadList components
statuspage_get_componentreadGet a component
statuspage_get_component_uptimereadGet component uptime
statuspage_list_component_groupsreadList component groups
statuspage_list_incidentsreadList incidents
statuspage_list_unresolved_incidentsreadList unresolved incidents
statuspage_list_maintenancesreadList maintenances
statuspage_get_incidentreadGet an incident
statuspage_count_subscribersreadCount subscribers
statuspage_list_metricsreadList metrics
statuspage_update_component_statuswriteUpdate a component status
statuspage_create_incidentwriteCreate an incident
statuspage_update_incidentwriteUpdate an incident
statuspage_usage_statusmetaUsage status (free-tier meter)
statuspage_request_featuremetaRequest a missing feature
statuspage_upgrademetaUpgrade to Pro or Pro+
statuspage_cancel_subscriptionmetaCancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro (per user)$9/mo or $90/yr (2 months free)Unlimited*

*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].

Pro covers this server only. Subscribe with statuspage_upgrade (it returns a Stripe Checkout link). Cancel any time with statuspage_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running statuspage_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT — see LICENSE. Documentation only; the server is hosted.

來源:servers/statuspage/README.md,提交 4046075

工具

15

statuspage_list_pages

List status pages

List the status pages the API key can see, with ids, names and subdomains. Start here to get a page_id. API: GET /pages.

無需輸入參數。

statuspage_get_page

Get a status page

Get the profile of one status page (name, subdomain, domain, time zone, notification settings). API: GET /pages/{page_id}.

輸入參數page_id必填

statuspage_list_components

List components

List the components of a page with their current status (operational, degraded_performance, partial_outage, major_outage, under_maintenance). API: GET /pages/{page_id}/components.

輸入參數pagepage_id必填per_page

statuspage_get_component

Get a component

Get one component with its status, group and description. API: GET /pages/{page_id}/components/{component_id}.

輸入參數page_id必填component_id必填

statuspage_get_component_uptime

Get component uptime

Get uptime data for one component over a date range (default: the last 90 days). Dates are ISO 8601. API: GET /pages/{page_id}/components/{component_id}/uptime.

輸入參數endstartpage_id必填component_id必填

statuspage_list_component_groups

List component groups

List the component groups of a page. API: GET /pages/{page_id}/component-groups.

輸入參數pagepage_id必填per_page

statuspage_list_incidents

List incidents

List incidents of a page, newest first. Use q to search by name, status or impact text. API: GET /pages/{page_id}/incidents.

輸入參數qpagelimitpage_id必填

statuspage_list_unresolved_incidents

List unresolved incidents

List incidents that are not resolved yet (investigating, identified, monitoring). API: GET /pages/{page_id}/incidents/unresolved.

輸入參數qpagelimitpage_id必填

statuspage_list_maintenances

List maintenances

List scheduled maintenances of a page. kind: scheduled (all planned), upcoming (not started) or active (in progress). API: GET /pages/{page_id}/incidents/{scheduled|upcoming|active_maintenance}.

輸入參數kindpagepage_id必填per_page

statuspage_get_incident

Get an incident

Get one incident with its full update timeline and affected components. API: GET /pages/{page_id}/incidents/{incident_id}.

輸入參數page_id必填incident_id必填

statuspage_count_subscribers

Count subscribers

Count the subscribers of a page by type (email, sms, webhook and others). API: GET /pages/{page_id}/subscribers/count.

輸入參數page_id必填

statuspage_list_metrics

List metrics

List the metrics shown on a page (for example response time). API: GET /pages/{page_id}/metrics.

輸入參數pagepage_id必填per_page

statuspage_update_component_status

Update a component status

WRITE, public. Set the status of one component on the live status page. Visitors see the change at once. API: PATCH /pages/{page_id}/components/{component_id}.

輸入參數status必填page_id必填component_id必填

statuspage_create_incident

Create an incident

WRITE, public. Create a real-time incident on the live status page. It is visible to visitors. With deliver_notifications true (the default of Statuspage) it also sends messages to subscribers. A second call creates a second incident. API: POST /pages/{page_id}/incidents.

輸入參數bodyname必填statuspage_id必填componentscomponent_idsimpact_overridedeliver_notifications

statuspage_update_incident

Update an incident

WRITE, public. Post a new update on an incident: change its status, add update text, or set the status of components. Each call with body adds a new timeline entry and can notify subscribers, so do not repeat it. Setting status resolved closes the incident. API: PATCH /pages/{page_id}/incidents/{incident_id}.

輸入參數bodynamestatuspage_id必填componentsincident_id必填impact_overridedeliver_notifications

版本歷史

6
  1. v1.3.4最新Nov 7, 2026
  2. v1.2.3Nov 5, 2026
  3. v1.2.2Nov 5, 2026
  4. v1.2.1Nov 4, 2026
  5. v1.2.0Nov 3, 2026
  6. v1.1.1Nov 3, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Usefulapi 整合