# Status.io MCP by usefulapi (remote · status-io.usefulapi.io)

Read Status.io components, incidents, maintenance; post incidents, schedule maintenance, set status.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

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

## Channel facts

- Endpoint: `https://status-io.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-10-17.

- **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 enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - 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**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3396 tokens (~169/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Status.io MCP by usefulapi server?

Status.io MCP by usefulapi is a hosted endpoint at https://status-io.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-status-io": {
      "url": "https://status-io.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-status-io": {
      "Transport": "http",
      "Url": "https://status-io.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-status-io -t streamable-http -u 'https://status-io.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-status-io": {
      "type": "http",
      "url": "https://status-io.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-10-17 (score 64, +1)

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

### 2026-10-14 (score 63, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 60, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 59)

First indexed and scored.

## MCP tools (20)

### `statusio_get_status_summary` (~80 tokens)

Get status summary

The current state of the status page in one call: overall status, every component and container with its status code and last update, open incidents and active/upcoming maintenance. Start here. GET /status/summary/{statuspage_id}.

Input parameters:

- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_list_components` (~90 tokens)

List components

List the components of the status page and the containers (data centers / locations) attached to each, with ids. Component and container ids are needed to update a status or to say what an incident affects ('<component_id>-<container_id>'). GET /component/list/{statuspage_id}.

Input parameters:

- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_list_incidents` (~75 tokens)

List incident ids

The ids of all active and resolved incidents (ids only, no details): a quick way to see which incidents exist. Fetch one with statusio_get_incident. GET /incidents/{statuspage_id}.

Input parameters:

- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_list_active_incidents` (~93 tokens)

List active incidents

Active (unresolved) incidents with their messages and affected components. GET /incident/list/active/{statuspage_id}.

Input parameters:

- `page` (integer): Page number, from 1 (default 1). Status.io reports no totals: ask for the next page until a page comes back empty.
- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_list_resolved_incidents` (~94 tokens)

List resolved incidents

Resolved incidents (history) with their messages and affected components. GET /incident/list/resolved/{statuspage_id}.

Input parameters:

- `page` (integer): Page number, from 1 (default 1). Status.io reports no totals: ask for the next page until a page comes back empty.
- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_get_incident` (~83 tokens)

Get incident

One incident in full: components, containers, infrastructure affected and all its messages. GET /incident/{statuspage_id}/{incident_id}.

Input parameters:

- `incident_id` (string, required): Incident id (from statusio_list_incidents or the active/resolved lists).
- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_get_incident_message` (~87 tokens)

Get incident message

One message (update) of an incident: text, state, status, time and the user who posted it. GET /incident/message/{statuspage_id}/{message_id}.

Input parameters:

- `message_id` (string, required): Incident message id (from statusio_get_incident).
- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_list_maintenance_ids` (~68 tokens)

List maintenance ids

The ids of all active, closed and upcoming maintenance events (ids only). Fetch one with statusio_get_maintenance. GET /maintenances/{statuspage_id}.

Input parameters:

- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_list_maintenance` (~134 tokens)

List maintenance

Maintenance events in one state, with messages and affected components: pending (scheduled, not started), active (in progress) or closed (finished). GET /maintenance/list/{pending|active|closed}/{statuspage_id}.

Input parameters:

- `page` (integer): Page number, from 1 (default 1). Status.io reports no totals: ask for the next page until a page comes back empty.
- `state` (string, required): pending = scheduled and not started, active = in progress, closed = finished.
- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_get_maintenance` (~82 tokens)

Get maintenance

One maintenance event in full, with all messages and the infrastructure affected. GET /maintenance/{statuspage_id}/{maintenance_id}.

Input parameters:

- `maintenance_id` (string, required): Maintenance id (from statusio_list_maintenance_ids or statusio_list_maintenance).
- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_get_maintenance_message` (~71 tokens)

Get maintenance message

One message of a maintenance event. GET /maintenance/message/{statuspage_id}/{message_id}.

Input parameters:

- `message_id` (string, required): Maintenance message id (from statusio_get_maintenance).
- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_list_subscribers` (~92 tokens)

List subscribers

List the people and endpoints subscribed to the status page (email addresses, phone numbers, webhook hosts) with ids and their granular preferences. This is personal data of your subscribers. Webhook URLs are shortened to their host, because they can carry secrets. GET /subscriber/list/{statuspage_id}.

Input parameters:

- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_update_component_status` (~143 tokens)

Update component status

WRITE: change the PUBLIC status of one component/container pair (for example to degraded_performance) without creating an incident. It changes what visitors of your status page see right away. Set it back to operational when done. Ids from statusio_list_components. POST /component/status/update.

Input parameters:

- `component_id` (string, required): Component id.
- `container_id` (string, required): Container id; it must be attached to that component.
- `details` (string, required): Short message shown with the status change.
- `status` (string, required): New status level.
- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_create_incident` (~352 tokens)

Create incident

WRITE: open a new incident on the PUBLIC status page. It is visible to every visitor immediately and sets the status of the affected components. No subscriber, Slack, Teams, IRC or Twitter notification is sent unless you switch it on (notify_*). Returns the new incident id. Say what is affected with all_infrastructure_affected or infrastructure_affected pairs. POST /incident/create.

Input parameters:

- `all_infrastructure_affected` (boolean): true = every component and container is affected. Otherwise give infrastructure_affected.
- `details` (string, required): Message describing the incident.
- `infrastructure_affected` (array): Affected pairs, each '<component_id>-<container_id>' (ids from statusio_list_components).
- `message_subject` (string): Subject line for the email notification.
- `name` (string, required): Short incident title.
- `notify_email` (boolean): Also email your email subscribers (default false).
- `notify_irc` (boolean): Also post to your connected IRC channel (default false).
- `notify_msteams` (boolean): Also post to your connected Microsoft Teams channels (default false).
- `notify_slack` (boolean): Also post to your connected Slack channels (default false).
- `notify_sms` (boolean): Also text your SMS subscribers (default false).
- `notify_webhook` (boolean): Also call your webhook subscribers (default false).
- `post_to_twitter` (boolean): Also post to your connected Twitter/X account (default false).
- `state` (string): Incident state (default investigating).
- `status` (string, required): Status the affected components get.
- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_update_incident` (~279 tokens)

Update incident

WRITE: post a new update message on an existing incident and set its state and component status. The message is public at once. No subscriber or channel notification is sent unless you switch it on (notify_*). To close an incident use statusio_resolve_incident. POST /incident/update.

Input parameters:

- `details` (string, required): Message describing this update.
- `incident_id` (string, required): Incident id.
- `message_subject` (string): Subject line for the email notification.
- `notify_email` (boolean): Also email your email subscribers (default false).
- `notify_irc` (boolean): Also post to your connected IRC channel (default false).
- `notify_msteams` (boolean): Also post to your connected Microsoft Teams channels (default false).
- `notify_slack` (boolean): Also post to your connected Slack channels (default false).
- `notify_sms` (boolean): Also text your SMS subscribers (default false).
- `notify_webhook` (boolean): Also call your webhook subscribers (default false).
- `post_to_twitter` (boolean): Also post to your connected Twitter/X account (default false).
- `state` (string, required): Incident state now.
- `status` (string, required): Status the affected components get now.
- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_resolve_incident` (~240 tokens)

Resolve incident

WRITE: resolve an incident with a closing message. The affected components return to operational and the incident moves to history. No notification is sent unless you switch it on (notify_*). POST /incident/resolve.

Input parameters:

- `details` (string, required): Message describing the resolution.
- `incident_id` (string, required): Incident id.
- `message_subject` (string): Subject line for the email notification.
- `notify_email` (boolean): Also email your email subscribers (default false).
- `notify_irc` (boolean): Also post to your connected IRC channel (default false).
- `notify_msteams` (boolean): Also post to your connected Microsoft Teams channels (default false).
- `notify_slack` (boolean): Also post to your connected Slack channels (default false).
- `notify_sms` (boolean): Also text your SMS subscribers (default false).
- `notify_webhook` (boolean): Also call your webhook subscribers (default false).
- `post_to_twitter` (boolean): Also post to your connected Twitter/X account (default false).
- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_schedule_maintenance` (~403 tokens)

Schedule maintenance

WRITE: schedule a planned maintenance on the PUBLIC status page. It is visible to visitors as upcoming maintenance. Subscribers are told only if you switch on notify_now / notify_72_hr / notify_24_hr / notify_1_hr (all default off). With automation true Status.io starts and ends it by itself at the planned times. Returns the maintenance id. POST /maintenance/schedule.

Input parameters:

- `all_infrastructure_affected` (boolean): true = every component and container is affected. Otherwise give infrastructure_affected.
- `automation` (boolean): Start and end the maintenance automatically at the planned times (default false).
- `automation_start_text` (string): Message posted when the maintenance starts (with automation).
- `automation_stop_text` (string): Message posted when the maintenance ends (with automation).
- `details` (string, required): Message describing the maintenance.
- `end` (string, required): Planned end, 'YYYY-MM-DD HH:mm' (24-hour); after the start.
- `infrastructure_affected` (array): Affected pairs, each '<component_id>-<container_id>' (ids from statusio_list_components).
- `message_subject` (string): Subject line for the email notifications.
- `name` (string, required): Short maintenance title.
- `notify_1_hr` (boolean): Remind subscribers 1 hour before the start (default false).
- `notify_24_hr` (boolean): Remind subscribers 24 hours before the start (default false).
- `notify_72_hr` (boolean): Remind subscribers 72 hours before the start (default false).
- `notify_now` (boolean): Tell subscribers right away (default false).
- `start` (string, required): Planned start, 'YYYY-MM-DD HH:mm' (24-hour). Status.io's reference does not state the time zone of this input: check the scheduled time in your dashboard.
- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_start_maintenance` (~245 tokens)

Start maintenance

WRITE: start a scheduled maintenance now; it moves from pending to active and the affected components show planned maintenance. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/start.

Input parameters:

- `details` (string, required): Message describing this maintenance update.
- `maintenance_id` (string, required): Maintenance id.
- `message_subject` (string): Subject line for the email notification.
- `notify_email` (boolean): Also email your email subscribers (default false).
- `notify_irc` (boolean): Also post to your connected IRC channel (default false).
- `notify_msteams` (boolean): Also post to your connected Microsoft Teams channels (default false).
- `notify_slack` (boolean): Also post to your connected Slack channels (default false).
- `notify_sms` (boolean): Also text your SMS subscribers (default false).
- `notify_webhook` (boolean): Also call your webhook subscribers (default false).
- `post_to_twitter` (boolean): Also post to your connected Twitter/X account (default false).
- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_update_maintenance` (~236 tokens)

Update maintenance

WRITE: post a new status message on an active maintenance event. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/update.

Input parameters:

- `details` (string, required): Message describing this maintenance update.
- `maintenance_id` (string, required): Maintenance id.
- `message_subject` (string): Subject line for the email notification.
- `notify_email` (boolean): Also email your email subscribers (default false).
- `notify_irc` (boolean): Also post to your connected IRC channel (default false).
- `notify_msteams` (boolean): Also post to your connected Microsoft Teams channels (default false).
- `notify_slack` (boolean): Also post to your connected Slack channels (default false).
- `notify_sms` (boolean): Also text your SMS subscribers (default false).
- `notify_webhook` (boolean): Also call your webhook subscribers (default false).
- `post_to_twitter` (boolean): Also post to your connected Twitter/X account (default false).
- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

### `statusio_finish_maintenance` (~244 tokens)

Finish maintenance

WRITE: finish an active maintenance event; it moves to history and the affected components return to operational. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/finish.

Input parameters:

- `details` (string, required): Message describing this maintenance update.
- `maintenance_id` (string, required): Maintenance id.
- `message_subject` (string): Subject line for the email notification.
- `notify_email` (boolean): Also email your email subscribers (default false).
- `notify_irc` (boolean): Also post to your connected IRC channel (default false).
- `notify_msteams` (boolean): Also post to your connected Microsoft Teams channels (default false).
- `notify_slack` (boolean): Also post to your connected Slack channels (default false).
- `notify_sms` (boolean): Also text your SMS subscribers (default false).
- `notify_webhook` (boolean): Also call your webhook subscribers (default false).
- `post_to_twitter` (boolean): Also post to your connected Twitter/X account (default false).
- `statuspage_id` (string): Status page id. Defaults to the status page chosen when you connected.

## Diagnostics

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

## Score history

- 2026-10-17: 64
- 2026-10-16: 63
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 60
- 2026-10-12: 59

## Common questions

### What is the Status.io MCP by usefulapi server?

Status.io MCP by usefulapi is listed in the public MCP registry as io.usefulapi/status-io. Read Status.io components, incidents, maintenance; post incidents, schedule maintenance, set status. This page covers its hosted endpoint (https://status-io.usefulapi.io/mcp).

### Is the Status.io MCP by usefulapi server safe to use?

Status.io MCP by usefulapi scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Status.io MCP by usefulapi server expose?

Status.io MCP by usefulapi exposes 20 tools: statusio_get_status_summary, statusio_list_components, statusio_list_incidents, statusio_list_active_incidents, statusio_list_resolved_incidents, and 15 more. Their descriptions and schemas cost roughly 3,191 tokens of context every time the server is loaded.

### Does the Status.io MCP by usefulapi server require authentication?

Yes. Status.io MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Status.io MCP by usefulapi server still maintained?

Status.io MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

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