# Usefulapi Statuspal MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.usefulapi%2Fstatuspal
Registry id: `mcp-registry/io.usefulapi/statuspal`
Status: auth-required (checked 2026-10-27T06:18:11.952Z)

## Verdict

Usefulapi Statuspal MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 62 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (96/100) across 11 tools, costing an agent about 2,244 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 62 ms | 88% of MCP servers |
| p95 handshake latency | 386 ms | — |
| Checks in 30 days | 219 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 11 | — |
| Tool-list size for an agent | ~2,244 tokens | 50% of MCP servers |
| Days observed | 28 | — |

## Install

```json
{
  "mcpServers": {
    "usefulapi-statuspal-mcp-server": {
      "type": "http",
      "url": "https://statuspal.usefulapi.io/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http usefulapi-statuspal-mcp-server https://statuspal.usefulapi.io/mcp
```

## Tools (11)

- `statuspal_create_incident`: 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; typ
- `statuspal_create_incident_update`: POSTS an update (e.g. investigating → identified → monitoring → resolved) to an existing incident on the LIVE public status page (and, with notify=true, notifie
- `statuspal_delete_incident`: DELETES an incident from the LIVE public status page — this permanently removes it. StatusPal: DELETE /status_pages/{subdomain}/incidents/{incident_id}.
- `statuspal_get_incident`: Get a single incident by its id. StatusPal: GET /status_pages/{subdomain}/incidents/{incident_id}.
- `statuspal_get_service_status`: Get the current status of a single service by its id. StatusPal: GET /status_pages/{subdomain}/services/{service_id}/status.
- `statuspal_get_status`: Get the current overall status of the status page (the aggregate status type). StatusPal: GET /status_pages/{subdomain}/status.
- `statuspal_get_summary`: Get the FULL status-page summary — status_page, services[], incidents[], maintenances[], upcoming_maintenances[], info_notices[], and current_status_type. Statu
- `statuspal_list_incidents`: List incidents for a status page. Returns {incidents[], links:{next,prev}, meta:{total_count}}. Use `before`/`after` cursors to paginate and `type` to filter. S
- `statuspal_list_metrics`: List the metrics configured on a status page. Use `before`/`after` cursors to paginate. StatusPal: GET /status_pages/{subdomain}/metrics.
- `statuspal_list_services`: List the services on a status page — each with {id, name, current_incident_type, children[]}. StatusPal: GET /status_pages/{subdomain}/services.
- `statuspal_update_incident`: UPDATES an existing incident on the LIVE public status page (title/type/services/timing). StatusPal: PUT /status_pages/{subdomain}/incidents/{incident_id}.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.