io.usefulapi由 usefulapi.io 發布官方發布者v1.23.5更新於 Nov 8, 2026
Read Status.io components, incidents, maintenance; post incidents, schedule maintenance, set status.
發布方自己的服務：Ably MCP by usefulapi
Status.io MCP by usefulapi 的託管 MCP 服務（status-io.usefulapi.io），由 usefulapi.io 發布；無需登入；Streamable HTTP；20 個工具。
暫無 AI 概覽：以下資訊來自註冊中心條目和服務本身。
Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.usefulapi%2Fstatus-io/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"status-io-by-usefulapi": {
"type": "http",
"url": "https://status-io.usefulapi.io/mcp"
}
}
}Use Status.io from Claude, Cursor, or any MCP client — status page components, incidents, maintenance windows and subscribers, plus incident and maintenance updates. Hosted, no local install: connect with your own Status.io credentials.
Live endpoint: https://status-io.usefulapi.io/mcp · Homepage: https://usefulapi.io/status-io
https://status-io.usefulapi.io/mcp.claude mcp add --transport http status-io https://status-io.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 Status.io credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/status-io/
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 statusio_upgrade (it returns a Stripe Checkout link). Cancel any time with statusio_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running statusio_upgrade before then undoes the cancel. Or write to [email protected].
MIT © usefulapi. Not affiliated with or endorsed by Status.io.
來源：servers/status-io/README.md，提交 4046075
Get status summary
The current state of the status page in one call: overall status, every component and container with its status code and last update, open incidents and active/upcoming maintenance. Start here. GET /status/summary/{statuspage_id}.
statuspage_idList components
List the components of the status page and the containers (data centers / locations) attached to each, with ids. Component and container ids are needed to update a status or to say what an incident affects ('<component_id>-<container_id>'). GET /component/list/{statuspage_id}.
statuspage_idList incident ids
The ids of all active and resolved incidents (ids only, no details): a quick way to see which incidents exist. Fetch one with statusio_get_incident. GET /incidents/{statuspage_id}.
statuspage_idList active incidents
Active (unresolved) incidents with their messages and affected components. GET /incident/list/active/{statuspage_id}.
pagestatuspage_idList resolved incidents
Resolved incidents (history) with their messages and affected components. GET /incident/list/resolved/{statuspage_id}.
pagestatuspage_idGet incident
One incident in full: components, containers, infrastructure affected and all its messages. GET /incident/{statuspage_id}/{incident_id}.
incident_id必填statuspage_idGet incident message
One message (update) of an incident: text, state, status, time and the user who posted it. GET /incident/message/{statuspage_id}/{message_id}.
message_id必填statuspage_idList maintenance ids
The ids of all active, closed and upcoming maintenance events (ids only). Fetch one with statusio_get_maintenance. GET /maintenances/{statuspage_id}.
statuspage_idList maintenance
Maintenance events in one state, with messages and affected components: pending (scheduled, not started), active (in progress) or closed (finished). GET /maintenance/list/{pending|active|closed}/{statuspage_id}.
pagestate必填statuspage_idGet maintenance
One maintenance event in full, with all messages and the infrastructure affected. GET /maintenance/{statuspage_id}/{maintenance_id}.
statuspage_idmaintenance_id必填Get maintenance message
One message of a maintenance event. GET /maintenance/message/{statuspage_id}/{message_id}.
message_id必填statuspage_idList subscribers
List the people and endpoints subscribed to the status page (email addresses, phone numbers, webhook hosts) with ids and their granular preferences. This is personal data of your subscribers. Webhook URLs are shortened to their host, because they can carry secrets. GET /subscriber/list/{statuspage_id}.
statuspage_idUpdate component status
WRITE: change the PUBLIC status of one component/container pair (for example to degraded_performance) without creating an incident. It changes what visitors of your status page see right away. Set it back to operational when done. Ids from statusio_list_components. POST /component/status/update.
status必填details必填component_id必填container_id必填statuspage_idCreate incident
WRITE: open a new incident on the PUBLIC status page. It is visible to every visitor immediately and sets the status of the affected components. No subscriber, Slack, Teams, IRC or Twitter notification is sent unless you switch it on (notify_*). Returns the new incident id. Say what is affected with all_infrastructure_affected or infrastructure_affected pairs. POST /incident/create.
name必填statestatus必填details必填notify_ircnotify_smsnotify_emailnotify_slackstatuspage_idnotify_msteamsnotify_webhookmessage_subject另有 3 個Update incident
WRITE: post a new update message on an existing incident and set its state and component status. The message is public at once. No subscriber or channel notification is sent unless you switch it on (notify_*). To close an incident use statusio_resolve_incident. POST /incident/update.
state必填status必填details必填notify_ircnotify_smsincident_id必填notify_emailnotify_slackstatuspage_idnotify_msteamsnotify_webhookmessage_subject另有 1 個Resolve incident
WRITE: resolve an incident with a closing message. The affected components return to operational and the incident moves to history. No notification is sent unless you switch it on (notify_*). POST /incident/resolve.
details必填notify_ircnotify_smsincident_id必填notify_emailnotify_slackstatuspage_idnotify_msteamsnotify_webhookmessage_subjectpost_to_twitterSchedule maintenance
WRITE: schedule a planned maintenance on the PUBLIC status page. It is visible to visitors as upcoming maintenance. Subscribers are told only if you switch on notify_now / notify_72_hr / notify_24_hr / notify_1_hr (all default off). With automation true Status.io starts and ends it by itself at the planned times. Returns the maintenance id. POST /maintenance/schedule.
end必填name必填start必填details必填automationnotify_nownotify_1_hrnotify_24_hrnotify_72_hrstatuspage_idmessage_subjectautomation_stop_text另有 3 個Start maintenance
WRITE: start a scheduled maintenance now; it moves from pending to active and the affected components show planned maintenance. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/start.
details必填notify_ircnotify_smsnotify_emailnotify_slackstatuspage_idmaintenance_id必填notify_msteamsnotify_webhookmessage_subjectpost_to_twitterUpdate maintenance
WRITE: post a new status message on an active maintenance event. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/update.
details必填notify_ircnotify_smsnotify_emailnotify_slackstatuspage_idmaintenance_id必填notify_msteamsnotify_webhookmessage_subjectpost_to_twitterFinish maintenance
WRITE: finish an active maintenance event; it moves to history and the affected components return to operational. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/finish.
details必填notify_ircnotify_smsnotify_emailnotify_slackstatuspage_idmaintenance_id必填notify_msteamsnotify_webhookmessage_subjectpost_to_twitter已滿足適用檢查項的 100%
該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。
io.usefulapi官方發布者
MCP server for Ably — channel history, presence, occupancy, stats, publish, and app management.
io.usefulapi官方發布者
託管的唯讀 MCP 伺服器，讓助理讀取 Tiltify 的募款活動、捐款紀錄以及捐款人與募款人排行榜。
io.usefulapi官方發布者
託管的 Termii 伺服器，讓助理傳送簡訊，並查詢錢包餘額、DND 狀態、寄件者 ID 和訊息紀錄。
io.usefulapi官方發布者
託管型 MCP 伺服器，讓助理讀取 Temp Stick 的溫度與濕度感測器、其讀值以及警示通知。
io.usefulapi官方發布者
將助理連接到 Stibee 電子郵件行銷工作區，可讀取地址簿、訂閱者和郵件統計，並新增訂閱者與分組。
{ "mcpServers": { "status-io": { "url": "https://status-io.usefulapi.io/mcp" } }}