io.usefulapi由 usefulapi.io 發布官方發布者v1.36.5更新於 Nov 8, 2026
Manage status pages: components, incidents and maintenances; set live component status.
發布方自己的服務：Ably MCP by usefulapi
託管的 Instatus 伺服器，讓助理讀取並修改狀態頁：元件、事件與排定維護。
Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.usefulapi%2Finstatus/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"instatus-by-usefulapi": {
"type": "http",
"url": "https://instatus.usefulapi.io/mcp"
}
}
}Manage Instatus from Claude, Cursor, or any MCP client — manage status pages — components, incidents and scheduled maintenances, and set live status. Hosted, no local install: connect with your Instatus API token.
Live endpoint: https://instatus.usefulapi.io/mcp · Homepage: https://usefulapi.io
https://instatus.usefulapi.io/mcp.claude mcp add --transport http instatus https://instatus.usefulapi.io/mcp, then run /mcp to log in.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 Instatus credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/instatus/
On first connect you'll paste your Instatus API token (Instatus → Developers → API). It's validated, stored per-user, and scoped to you — no keys in config files.
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.
*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 instatus_upgrade (it returns a Stripe Checkout link). Cancel any time with instatus_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running instatus_upgrade before then undoes the cancel. Or write to [email protected].
MIT — see LICENSE. Documentation only; the server is hosted.
來源：servers/instatus/README.md，提交 4046075
List pages
List all status pages on the account — each page's id, subdomain, name, status, url, custom domain, and timestamps. The page id is what every other tool takes as `page_id`. Instatus: GET /v2/pages.
pageper_pageList components
List a status page's components — id, name, description, status, order, showUptime, grouped, archived. The component ids are what you set impact on. Instatus: GET /v2/{page_id}/components.
pagepage_id必填per_pageGet component
Get a single component by id — its full state (name, description, status, order, showUptime, grouped, archived). Instatus: GET /v2/{page_id}/components/{component_id}.
page_id必填component_id必填List incidents
List a status page's incidents, most recent first — optionally filtered by status. Each incident: id, name, status, impact, affected components, updates, timestamps. Instatus: GET /v1/{page_id}/incidents.
pagestatuspage_id必填per_pageGet incident
Get a single incident by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/incidents/{incident_id}.
page_id必填incident_id必填List maintenances
List a status page's scheduled maintenances, most recent first — id, name, status, affected components, start/end, updates. Instatus: GET /v2/{page_id}/maintenances.
pagepage_id必填per_pageGet maintenance
Get a single scheduled maintenance by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/maintenances/{maintenance_id}.
page_id必填maintenance_id必填Update component
UPDATES a component by id — this MODIFIES live status-page data. The key way to set a component's operational status (OPERATIONAL, UNDERMAINTENANCE, DEGRADEDPERFORMANCE, PARTIALOUTAGE, MAJOROUTAGE). Send only the fields you want to change. Instatus: PUT /v2/{page_id}/components/{component_id}. Returns the updated component.
nameorderstatusgroupedpage_id必填archivedshowUptimedescriptioncomponent_id必填Create incident
CREATES a new incident — this MODIFIES live status-page data and can notify subscribers. Provide `name` (required); optionally set the initial `message`, affected `components`, per-component impact via `statuses`, `status`, `started`, `notify`, and `shouldPublish`. Instatus: POST /v1/{page_id}/incidents. Returns the created incident.
name必填notifystatusmessagepage_id必填startedstatusescomponentsshouldPublishUpdate incident
UPDATES an existing incident by id — this MODIFIES live status-page data and can notify subscribers (e.g. move it to MONITORING or RESOLVED). Send only the fields you want to change. Instatus: PUT /v1/{page_id}/incidents/{incident_id}. Returns the updated incident.
namenotifystatusmessagepage_id必填startedstatusescomponentsincident_id必填shouldPublishDelete incident
PERMANENTLY DELETES an incident by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/incidents/{incident_id}.
page_id必填incident_id必填Create maintenance
CREATES a new scheduled maintenance — this MODIFIES live status-page data and can notify subscribers. Provide `name` (required); optionally set `message`, affected `components`, per-component impact via `statuses`, `status`, `start`/`end`, `duration`, and `notify`. Instatus: POST /v1/{page_id}/maintenances. Returns the created maintenance.
endname必填startnotifystatusmessagepage_id必填durationstatusescomponentsUpdate maintenance
UPDATES an existing scheduled maintenance by id — this MODIFIES live status-page data and can notify subscribers. Send only the fields you want to change. Instatus: PUT /v1/{page_id}/maintenances/{maintenance_id}. Returns the updated maintenance.
endnamestartnotifystatusmessagepage_id必填durationstatusescomponentsmaintenance_id必填Delete maintenance
PERMANENTLY DELETES a scheduled maintenance by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/maintenances/{maintenance_id}.
page_id必填maintenance_id必填已滿足適用檢查項的 100%
該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。
io.usefulapi官方發布者
面向 Ably 即時訊息的託管 MCP 伺服器：檢視頻道歷史、線上狀態與佔用情形，發布訊息，並查看應用程式用量與設定。
io.usefulapi官方發布者
託管式唯讀 MCP 伺服器，讓助理查詢 Woffu 公司的使用者、勞動契約、部門與辦公地點。
io.usefulapi官方發布者
託管的 White Label Loyalty MCP 伺服器：瀏覽獎勵、查看客戶點數錢包與等級進度，並以點數購買獎勵。
io.usefulapi官方發布者
託管的 Weekdone 連接器，讓助理讀取週報、團隊、目標與 KPI，並新增報告項目、留言和 KPI 數值。
io.usefulapi官方發布者
託管式唯讀 MCP 伺服器，讓助理列出 WebinarKit 的網路研討會、場次時間、系列、會議以及白標子帳戶。
{ "mcpServers": { "instatus": { "url": "https://instatus.usefulapi.io/mcp" } }}