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

Manage status pages: components, incidents and maintenances; set live component status.

- Trust score: 28/100 (low)
- Change this week: −41
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

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

## Channel facts

- Endpoint: `https://instatus.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**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
  - 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.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 4 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-instatus": {
      "type": "http",
      "url": "https://instatus.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-03 (score 28, −44)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.20 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: fail → unverified

### 2026-08-02 (score 72, +54)

- [security improvement] Authorization: unverified → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.20

### 2026-08-01 (score 18, −53)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.13 → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-31 (score 71, +3)

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

### 2026-07-30 (score 68, −2)

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

### 2026-07-29 (score 70, +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 69, 0)

- [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

## MCP tools (14)

### `instatus_list_pages` (~95 tokens)

List pages

List all status pages on the account — each page's id, subdomain, name, status, url, custom domain, and timestamps. The page id is what every other tool takes as `page_id`. Instatus: GET /v2/pages.

Input parameters:

- `page` (integer): Page number to fetch (default 1).
- `per_page` (integer): Items per page (default 50, max 100).

### `instatus_list_components` (~109 tokens)

List components

List a status page's components — id, name, description, status, order, showUptime, grouped, archived. The component ids are what you set impact on. Instatus: GET /v2/{page_id}/components.

Input parameters:

- `page` (integer): Page number to fetch (default 1).
- `page_id` (string, required): The status page's id (from list_pages).
- `per_page` (integer): Items per page (default 50, max 100).

### `instatus_get_component` (~78 tokens)

Get component

Get a single component by id — its full state (name, description, status, order, showUptime, grouped, archived). Instatus: GET /v2/{page_id}/components/{component_id}.

Input parameters:

- `component_id` (string, required): The component's id.
- `page_id` (string, required): The status page's id.

### `instatus_list_incidents` (~135 tokens)

List incidents

List a status page's incidents, most recent first — optionally filtered by status. Each incident: id, name, status, impact, affected components, updates, timestamps. Instatus: GET /v1/{page_id}/incidents.

Input parameters:

- `page` (integer): Page number to fetch (default 1).
- `page_id` (string, required): The status page's id.
- `per_page` (integer): Items per page (default 50, max 100).
- `status` (string): Filter to incidents with this status (INVESTIGATING, IDENTIFIED, MONITORING, RESOLVED).

### `instatus_get_incident` (~71 tokens)

Get incident

Get a single incident by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/incidents/{incident_id}.

Input parameters:

- `incident_id` (string, required): The incident's id.
- `page_id` (string, required): The status page's id.

### `instatus_list_maintenances` (~103 tokens)

List maintenances

List a status page's scheduled maintenances, most recent first — id, name, status, affected components, start/end, updates. Instatus: GET /v2/{page_id}/maintenances.

Input parameters:

- `page` (integer): Page number to fetch (default 1).
- `page_id` (string, required): The status page's id.
- `per_page` (integer): Items per page (default 50, max 100).

### `instatus_get_maintenance` (~73 tokens)

Get maintenance

Get a single scheduled maintenance by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/maintenances/{maintenance_id}.

Input parameters:

- `maintenance_id` (string, required): The maintenance's id.
- `page_id` (string, required): The status page's id.

### `instatus_update_component` (~214 tokens)

Update component

UPDATES a component by id — this MODIFIES live status-page data. The key way to set a component's operational status (OPERATIONAL, UNDERMAINTENANCE, DEGRADEDPERFORMANCE, PARTIALOUTAGE, MAJOROUTAGE). Send only the fields you want to change. Instatus: PUT /v2/{page_id}/components/{component_id}. Returns the updated component.

Input parameters:

- `archived` (boolean): Whether the component is archived (hidden).
- `component_id` (string, required): The component's id to update.
- `description` (string): Free-form component description.
- `grouped` (boolean): Whether the component is displayed within a group.
- `name` (string): Component name.
- `order` (integer): Display order of the component on the page.
- `page_id` (string, required): The status page's id.
- `showUptime` (boolean): Whether to show the uptime graph for this component.
- `status` (string): Operational status of the component.

### `instatus_create_incident` (~216 tokens)

Create incident

CREATES a new incident — this MODIFIES live status-page data and can notify subscribers. Provide `name` (required); optionally set the initial `message`, affected `components`, per-component impact via `statuses`, `status`, `started`, `notify`, and `shouldPublish`. Instatus: POST /v1/{page_id}/incidents. Returns the created incident.

Input parameters:

- `components` (array): Component ids affected by this incident.
- `message` (string): Incident update message (Markdown supported).
- `name` (string, required): Incident title (required).
- `notify` (boolean): Whether to notify subscribers about this update.
- `page_id` (string, required): The status page's id.
- `shouldPublish` (boolean): Whether the incident should be published to the status page.
- `started` (string): ISO 8601 timestamp for when the incident started.
- `status` (string): Incident status.
- `statuses` (array): Per-component impact — set each listed component's status for this event.

### `instatus_update_incident` (~217 tokens)

Update incident

UPDATES an existing incident by id — this MODIFIES live status-page data and can notify subscribers (e.g. move it to MONITORING or RESOLVED). Send only the fields you want to change. Instatus: PUT /v1/{page_id}/incidents/{incident_id}. Returns the updated incident.

Input parameters:

- `components` (array): Component ids affected by this incident.
- `incident_id` (string, required): The incident's id to update.
- `message` (string): Incident update message (Markdown supported).
- `name` (string): Incident title.
- `notify` (boolean): Whether to notify subscribers about this update.
- `page_id` (string, required): The status page's id.
- `shouldPublish` (boolean): Whether the incident should be published to the status page.
- `started` (string): ISO 8601 timestamp for when the incident started.
- `status` (string): Incident status.
- `statuses` (array): Per-component impact — set each listed component's status for this event.

### `instatus_delete_incident` (~80 tokens)

Delete incident

PERMANENTLY DELETES an incident by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/incidents/{incident_id}.

Input parameters:

- `incident_id` (string, required): The incident's id to delete.
- `page_id` (string, required): The status page's id.

### `instatus_create_maintenance` (~229 tokens)

Create maintenance

CREATES a new scheduled maintenance — this MODIFIES live status-page data and can notify subscribers. Provide `name` (required); optionally set `message`, affected `components`, per-component impact via `statuses`, `status`, `start`/`end`, `duration`, and `notify`. Instatus: POST /v1/{page_id}/maintenances. Returns the created maintenance.

Input parameters:

- `components` (array): Component ids affected by this maintenance.
- `duration` (integer): Maintenance duration in minutes.
- `end` (string): ISO 8601 timestamp for when the maintenance ends.
- `message` (string): Maintenance update message (Markdown supported).
- `name` (string, required): Maintenance title (required).
- `notify` (boolean): Whether to notify subscribers about this update.
- `page_id` (string, required): The status page's id.
- `start` (string): ISO 8601 timestamp for when the maintenance starts.
- `status` (string): Maintenance status.
- `statuses` (array): Per-component impact — set each listed component's status for this event.

### `instatus_update_maintenance` (~215 tokens)

Update maintenance

UPDATES an existing scheduled maintenance by id — this MODIFIES live status-page data and can notify subscribers. Send only the fields you want to change. Instatus: PUT /v1/{page_id}/maintenances/{maintenance_id}. Returns the updated maintenance.

Input parameters:

- `components` (array): Component ids affected by this maintenance.
- `duration` (integer): Maintenance duration in minutes.
- `end` (string): ISO 8601 timestamp for when the maintenance ends.
- `maintenance_id` (string, required): The maintenance's id to update.
- `message` (string): Maintenance update message (Markdown supported).
- `name` (string): Maintenance title.
- `notify` (boolean): Whether to notify subscribers about this update.
- `page_id` (string, required): The status page's id.
- `start` (string): ISO 8601 timestamp for when the maintenance starts.
- `status` (string): Maintenance status.
- `statuses` (array): Per-component impact — set each listed component's status for this event.

### `instatus_delete_maintenance` (~82 tokens)

Delete maintenance

PERMANENTLY DELETES a scheduled maintenance by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/maintenances/{maintenance_id}.

Input parameters:

- `maintenance_id` (string, required): The maintenance's id to delete.
- `page_id` (string, required): The status page's id.

## Diagnostics

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

## Score history

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

## Links

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