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 连接器，让助手读取状态页的组件、事件和维护，并发布公开的事件与维护更新。
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官方发布者
用于 Ably 的 MCP 服务器——频道历史、在线状态、占用情况、统计、发布和应用管理。AI 翻译
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" } }}