Statuspage MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://statuspage.usefulapi.io/mcp

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

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

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

https://statuspage.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• 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_get_page

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

• 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_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_list_component_groups

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

• 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_unresolved_incidents

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

• 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_get_incident

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

• statuspage_count_subscribers

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

• statuspage_list_metrics

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

• 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_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_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/{pag

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 33 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 15 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32417 servers in this category
• Published to the registry more recently than 98% of the other 32417 servers in this category
• Basic checks equal to or better than 100% of the other 32417 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{