StatusPal MCP by usefulapi
Server Details
Read status-page status, services, incidents and metrics; create, update and publish incidents.
- Status
- Healthy
- Uptime
- 70.9% over 53 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
TDQS
Scored across 11 tools
Each tool targets a distinct resource and action: incidents have separate create, update, delete, get, and list tools; status, summary, service status, metrics, and services are each covered by dedicated read/list tools. Even get_incident and get_summary, which both expose incident data, serve clearly different purposes (single entity vs full page snapshot).
All tools follow the consistent pattern `statuspal_<verb>_<noun>`, using standard verbs (create, delete, get, list, update) and clear nouns (incident, incident_update, service_status, status, summary, metrics, services). No mixed conventions or vague verbs.
With 11 tools, the server is well-scoped for a status page management API. Each tool corresponds to a logical API endpoint and there is no redundancy or bloat. The count falls comfortably within the expected range for a focused domain.
Incidents have full CRUD plus update posting, covering the main lifecycle. However, services and metrics are only readable (list and get status), with no create, update, or delete operations. This leaves a notable gap for workflows that require adding or modifying services, though the core incident handling is complete.
Available Tools
11 toolsstatuspal_create_incidentCreate incidentDestructiveInspect
PUBLISHES a new incident to the LIVE public status page (and, with notify=true, emails/notifies subscribers). type="major" or "minor" is an outage incident; type="scheduled" creates a scheduled maintenance window. StatusPal: POST /status_pages/{subdomain}/incidents.
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | Incident type. "major"/"minor" = outage severity; "scheduled" = a maintenance window. | |
| title | Yes | Incident title (required). | |
| notify | No | Whether to notify/email subscribers. | |
| ends_at | No | ISO8601 end time (optional). | |
| updates | No | Optional initial updates to post with the incident. | |
| starts_at | No | ISO8601 start time (optional; required for scheduled maintenance). | |
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). | |
| service_ids | Yes | Ids of the affected services (required). |
statuspal_create_incident_updatePost incident updateDestructiveInspect
POSTS an update (e.g. investigating → identified → monitoring → resolved) to an existing incident on the LIVE public status page (and, with notify=true, notifies subscribers). StatusPal: POST /status_pages/{subdomain}/incidents/{incident_id}/updates.
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | Update type — common values: "investigating", "identified", "monitoring", "resolved", "issue". | |
| notify | No | Whether to notify/email subscribers about this update. | |
| posted_at | No | ISO8601 timestamp for the update (optional; defaults to now). | |
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). | |
| description | Yes | The update message shown on the status page (required). | |
| incident_id | Yes | The incident id to post an update to. |
statuspal_delete_incidentDelete incidentDestructiveInspect
DELETES an incident from the LIVE public status page — this permanently removes it. StatusPal: DELETE /status_pages/{subdomain}/incidents/{incident_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). | |
| incident_id | Yes | The incident id to delete. |
statuspal_get_incidentGet incidentRead-onlyInspect
Get a single incident by its id. StatusPal: GET /status_pages/{subdomain}/incidents/{incident_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). | |
| incident_id | Yes | The incident id. |
statuspal_get_service_statusGet service statusRead-onlyInspect
Get the current status of a single service by its id. StatusPal: GET /status_pages/{subdomain}/services/{service_id}/status.
| Name | Required | Description | Default |
|---|---|---|---|
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). | |
| service_id | Yes | The service id. |
statuspal_get_statusGet overall statusRead-onlyInspect
Get the current overall status of the status page (the aggregate status type). StatusPal: GET /status_pages/{subdomain}/status.
| Name | Required | Description | Default |
|---|---|---|---|
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
statuspal_get_summaryGet status page summaryRead-onlyInspect
Get the FULL status-page summary — status_page, services[], incidents[], maintenances[], upcoming_maintenances[], info_notices[], and current_status_type. StatusPal: GET /status_pages/{subdomain}/summary.
| Name | Required | Description | Default |
|---|---|---|---|
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
statuspal_list_incidentsList incidentsRead-onlyInspect
List incidents for a status page. Returns {incidents[], links:{next,prev}, meta:{total_count}}. Use before/after cursors to paginate and type to filter. StatusPal: GET /status_pages/{subdomain}/incidents.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Filter incidents by type. | |
| after | No | Pagination cursor — return incidents after this cursor. | |
| limit | No | Max incidents to return (default 20, max 100). | |
| before | No | Pagination cursor — return incidents before this cursor. | |
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
statuspal_list_metricsList metricsRead-onlyInspect
List the metrics configured on a status page. Use before/after cursors to paginate. StatusPal: GET /status_pages/{subdomain}/metrics.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Pagination cursor — return metrics after this cursor. | |
| limit | No | Max metrics to return. | |
| before | No | Pagination cursor — return metrics before this cursor. | |
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
statuspal_list_servicesList servicesRead-onlyInspect
List the services on a status page — each with {id, name, current_incident_type, children[]}. StatusPal: GET /status_pages/{subdomain}/services.
| Name | Required | Description | Default |
|---|---|---|---|
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
statuspal_update_incidentUpdate incidentDestructiveInspect
UPDATES an existing incident on the LIVE public status page (title/type/services/timing). StatusPal: PUT /status_pages/{subdomain}/incidents/{incident_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | New incident type ("major"/"minor"/"scheduled"). | |
| title | No | New incident title. | |
| notify | No | Whether to notify/email subscribers about the change. | |
| ends_at | No | New ISO8601 end time. | |
| starts_at | No | New ISO8601 start time. | |
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). | |
| incident_id | Yes | The incident id to update. | |
| service_ids | No | New set of affected service ids. |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
11 tool updates
- Changed
statuspal_create_incident1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
statuspal_create_incident_update1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
statuspal_delete_incident1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
statuspal_get_incident1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
statuspal_get_service_status1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
statuspal_get_status1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
statuspal_get_summary1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
statuspal_list_incidents1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
statuspal_list_metrics1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
statuspal_list_services1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
statuspal_update_incident1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
11 tool updates
- First observed
statuspal_create_incident - First observed
statuspal_create_incident_update - First observed
statuspal_delete_incident - First observed
statuspal_get_incident - First observed
statuspal_get_service_status - First observed
statuspal_get_status - First observed
statuspal_get_summary - First observed
statuspal_list_incidents - First observed
statuspal_list_metrics - First observed
statuspal_list_services - First observed
statuspal_update_incident
Related MCP Connectors
Status pages and uptime monitoring: read status, monitors and incidents; open incidents.
Manage status pages: components, incidents and maintenances; set live component status.
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.
Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables management of Atlassian Statuspage incidents, components, and subscribers through natural language.-
- AlicenseAqualityCmaintenanceEnables AI agents to check whether anything on a status page is down, open, update and resolve incidents, change component statuses, and schedule maintenance windows through Instatus's public API. Writes keep subscriber notifications off by default and expose MCP annotations so clients can confirm before publishing anything.1411 npmMIT

StackWitnessofficial
FlicenseNot gradedqualityCmaintenanceLet agents read and manage your org’s independent monitors, incidents, status pages, and alerts (honest measured state, no false greens).-- AlicenseAqualityBmaintenanceEnables querying the current state, incident history, resolution times, and feed URLs for over 1,100 SaaS/cloud vendor status pages.7MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.