# io.usefulapi/statuspal (remote · statuspal.usefulapi.io)

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

- Trust score: 73/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `statuspal.usefulapi.io`: 73/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-statuspal/statuspal.md), [page](https://verifymcp.io/servers/io-usefulapi-statuspal/statuspal)

## Channel facts

- Endpoint: `https://statuspal.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1218 tokens (~110/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.io-usefulapi-statuspal]
url = "https://statuspal.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-statuspal": {
      "type": "remote",
      "url": "https://statuspal.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-statuspal --url https://statuspal.usefulapi.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-statuspal:
    url: "https://statuspal.usefulapi.io/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 69, +57)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 12)

First indexed and scored.

## MCP tools (11)

### `statuspal_get_summary` (~75 tokens)

Get status page summary

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.

Input parameters:

- `subdomain` (string): Status page subdomain (overrides STATUSPAL_SUBDOMAIN).

### `statuspal_get_status` (~57 tokens)

Get overall status

Get the current overall status of the status page (the aggregate status type). StatusPal: GET /status_pages/{subdomain}/status.

Input parameters:

- `subdomain` (string): Status page subdomain (overrides STATUSPAL_SUBDOMAIN).

### `statuspal_list_services` (~65 tokens)

List services

List the services on a status page — each with {id, name, current_incident_type, children[]}. StatusPal: GET /status_pages/{subdomain}/services.

Input parameters:

- `subdomain` (string): Status page subdomain (overrides STATUSPAL_SUBDOMAIN).

### `statuspal_get_service_status` (~71 tokens)

Get service status

Get the current status of a single service by its id. StatusPal: GET /status_pages/{subdomain}/services/{service_id}/status.

Input parameters:

- `service_id` (number, required): The service id.
- `subdomain` (string): Status page subdomain (overrides STATUSPAL_SUBDOMAIN).

### `statuspal_list_incidents` (~147 tokens)

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. StatusPal: GET /status_pages/{subdomain}/incidents.

Input parameters:

- `after` (string): Pagination cursor — return incidents after this cursor.
- `before` (string): Pagination cursor — return incidents before this cursor.
- `limit` (number): Max incidents to return (default 20, max 100).
- `subdomain` (string): Status page subdomain (overrides STATUSPAL_SUBDOMAIN).
- `type` (string): Filter incidents by type.

### `statuspal_get_incident` (~66 tokens)

Get incident

Get a single incident by its id. StatusPal: GET /status_pages/{subdomain}/incidents/{incident_id}.

Input parameters:

- `incident_id` (number, required): The incident id.
- `subdomain` (string): Status page subdomain (overrides STATUSPAL_SUBDOMAIN).

### `statuspal_list_metrics` (~105 tokens)

List metrics

List the metrics configured on a status page. Use `before`/`after` cursors to paginate. StatusPal: GET /status_pages/{subdomain}/metrics.

Input parameters:

- `after` (string): Pagination cursor — return metrics after this cursor.
- `before` (string): Pagination cursor — return metrics before this cursor.
- `limit` (number): Max metrics to return.
- `subdomain` (string): Status page subdomain (overrides STATUSPAL_SUBDOMAIN).

### `statuspal_create_incident` (~207 tokens)

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; type="scheduled" creates a scheduled maintenance window. StatusPal: POST /status_pages/{subdomain}/incidents.

Input parameters:

- `ends_at` (string): ISO8601 end time (optional).
- `notify` (boolean): Whether to notify/email subscribers.
- `service_ids` (array, required): Ids of the affected services (required).
- `starts_at` (string): ISO8601 start time (optional; required for scheduled maintenance).
- `subdomain` (string): Status page subdomain (overrides STATUSPAL_SUBDOMAIN).
- `title` (string, required): Incident title (required).
- `type` (string, required): Incident type. "major"/"minor" = outage severity; "scheduled" = a maintenance window.
- `updates` (array): Optional initial updates to post with the incident.

### `statuspal_update_incident` (~163 tokens)

Update incident

UPDATES an existing incident on the LIVE public status page (title/type/services/timing). StatusPal: PUT /status_pages/{subdomain}/incidents/{incident_id}.

Input parameters:

- `ends_at` (string): New ISO8601 end time.
- `incident_id` (number, required): The incident id to update.
- `notify` (boolean): Whether to notify/email subscribers about the change.
- `service_ids` (array): New set of affected service ids.
- `starts_at` (string): New ISO8601 start time.
- `subdomain` (string): Status page subdomain (overrides STATUSPAL_SUBDOMAIN).
- `title` (string): New incident title.
- `type` (string): New incident type ("major"/"minor"/"scheduled").

### `statuspal_create_incident_update` (~185 tokens)

Post 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, notifies subscribers). StatusPal: POST /status_pages/{subdomain}/incidents/{incident_id}/updates.

Input parameters:

- `description` (string, required): The update message shown on the status page (required).
- `incident_id` (number, required): The incident id to post an update to.
- `notify` (boolean): Whether to notify/email subscribers about this update.
- `posted_at` (string): ISO8601 timestamp for the update (optional; defaults to now).
- `subdomain` (string): Status page subdomain (overrides STATUSPAL_SUBDOMAIN).
- `type` (string, required): Update type — common values: "investigating", "identified", "monitoring", "resolved", "issue".

### `statuspal_delete_incident` (~77 tokens)

Delete incident

DELETES an incident from the LIVE public status page — this permanently removes it. StatusPal: DELETE /status_pages/{subdomain}/incidents/{incident_id}.

Input parameters:

- `incident_id` (number, required): The incident id to delete.
- `subdomain` (string): Status page subdomain (overrides STATUSPAL_SUBDOMAIN).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-statuspal/statuspal#diagnostics

## Score history

- 2026-08-03: 73
- 2026-08-02: 73
- 2026-08-01: 72
- 2026-07-31: 72
- 2026-07-30: 71
- 2026-07-29: 71
- 2026-07-28: 70
- 2026-07-27: 69
- 2026-07-26: 12

## Links

- Remote endpoint: https://statuspal.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-statuspal/statuspal/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-statuspal/statuspal/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-statuspal/statuspal