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" } }}