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 集成