io.usefulapi/statuspage · v1.0.0 · cloud-and-infra
Statuspage MCP by usefulapi is healthy: it completed an MCP handshake in 615 ms and exposes 15 tools.
Read pages, components, incidents and maintenances; create and update incidents in Statuspage.
Endpoint: https://statuspage.usefulapi.io/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 15 |
| Latency | 615 ms |
| Last checked (UTC) | 2026-11-02T01:55:23.885Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-11-02T01:55:23.885Z | Healthy | 615 |
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/{page_id}/incidents/{inc |