Statuspage MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Statuspage MCP by usefulapi is answering right now. Last checked 12 min ago. It exposes 15 tools. Last commit 2 Nov 2026.

Read pages, components, incidents and maintenances; create and update incidents in Statuspage.

Uptime history 5 hours of history

5 hours agonow

100.0%

Uptime 24h

16 of 16 checks

Tools

read from the server

230 ms

Response time

average over 24h

Stars

last commit 2 Nov 2026

Nothing serious here today

Today is the operative word: we check Statuspage MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add statuspage --transport http https://statuspage.usefulapi.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://statuspage.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.statuspage]
url = "https://statuspage.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "statuspage": {
      "url": "https://statuspage.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "statuspage": {
      "type": "http",
      "url": "https://statuspage.usefulapi.io/mcp"
    }
  }
}

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

statuspage

statuspage_count_subscribers

Count the subscribers of a page by type (email, sms, webhook and others). API: GET /pages/{page_id}/subscribers/count.

statuspage_create_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.

statuspage_get_component

Get one component with its status, group and description. API: GET /pages/{page_id}/components/{component_id}.

statuspage_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.

statuspage_get_incident

Get one incident with its full update timeline and affected components. API: GET /pages/{page_id}/incidents/{incident_id}.

statuspage_get_page

Get the profile of one status page (name, subdomain, domain, time zone, notification settings). API: GET /pages/{page_id}.

statuspage_list_component_groups

List the component groups of a page. API: GET /pages/{page_id}/component-groups.

statuspage_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.

statuspage_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.

statuspage_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}.

statuspage_list_metrics

List the metrics shown on a page (for example response time). API: GET /pages/{page_id}/metrics.

statuspage_list_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_list_unresolved_incidents

List incidents that are not resolved yet (investigating, identified, monitoring). API: GET /pages/{page_id}/incidents/unresolved.

statuspage_update_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}.

statuspage_update_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}.

Endpoints

URL	Transport	State	Latency	Checked
https://statuspage.usefulapi.io/mcp	streamable-http	answering	272 ms	12 min ago

Alternatives to Statuspage MCP by usefulapi

same job, measured the same way

Instatus MCP by usefulapi

by usefulapi

Manage status pages: components, incidents and maintenances; set live component status.

14 tools answering

StatusPage.me MCP by usefulapi

by usefulapi

Read status pages, incidents and monitors, and post incidents and maintenance in StatusPage.me.

14 tools answering

StatusCast MCP by usefulapi

by usefulapi

Read page status, components, uptime, incidents and content templates in StatusCast.

10 tools answering

StatusPal MCP by usefulapi

by usefulapi

Read status-page status, services, incidents and metrics; create, update and publish incidents.

11 tools answering

Status.io MCP by usefulapi

by usefulapi

Read Status.io components, incidents, maintenance; post incidents, schedule maintenance, set status.

20 tools answering

Instatus

by instatus

Status pages, incidents, maintenance, components and subscribers on Instatus.

answering

StatusCake MCP by usefulapi

by usefulapi

Review uptime, SSL, pagespeed and heartbeat checks, alerts and maintenance windows; create checks.

21 tools answering

All Quiet MCP by usefulapi

by usefulapi

Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides.

11 tools answering

Statuspage MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Statuspage MCP by usefulapi do?

It exposes 15 tools, read directly from the server on our last check. Among them: statuspage_count_subscribers, statuspage_create_incident, statuspage_get_component, statuspage_get_component_uptime, statuspage_get_incident, statuspage_get_page and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Statuspage MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 16 of 16 checks got a reply (100.0%), average response time 230 ms. The bar chart above shows every period we have measured.

How do I connect Statuspage MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Statuspage MCP by usefulapi need an API key?

No. Statuspage MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Statuspage MCP by usefulapi?

It answers our handshake in 230 ms on average, which is faster than 62% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Statuspage MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at statuspage.usefulapi.io, which runs on its operator's own terms.