Instatus MCP by usefulapi
REMOTE · INSTATUS.USEFULAPI.IO
Manage status pages: components, incidents and maintenances; set live component status.
Available components
Last scanned (18 minutes ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Monitoring and Observability
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “check_scheduled_maintenances_on_a_status_page” functional
- New prompt “check_the_status_of_each_component_on_a_status_page” functional
- New prompt “open_an_incident_and_set_component_status” functional
- New prompt “review_recent_incidents_and_their_update_timeline” functional
- New prompt “update_or_resolve_an_incident_or_schedule_maintenance” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://instatus.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of instatus.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://instatus.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/instatus/ |
| http (plaintext) | http://instatus.usefulapi.io/mcp | Inconclusive | 302 | http://instatus.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
instatus_create_incident Create incident ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| components | array | – | Component ids affected by this incident. |
| message | string | – | Incident update message (Markdown supported). |
| name | string | yes | Incident title (required). |
| notify | boolean | – | Whether to notify subscribers about this update. |
| page_id | string | yes | 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. |
No output schema declared.
No examples provided.
instatus_create_maintenance Create maintenance ~229
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Maintenance title (required). |
| notify | boolean | – | Whether to notify subscribers about this update. |
| page_id | string | yes | 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. |
No output schema declared.
No examples provided.
instatus_delete_incident Delete incident ~80
PERMANENTLY DELETES an incident by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/incidents/{incident_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | string | yes | The incident's id to delete. |
| page_id | string | yes | The status page's id. |
No output schema declared.
No examples provided.
instatus_delete_maintenance Delete maintenance ~82
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| maintenance_id | string | yes | The maintenance's id to delete. |
| page_id | string | yes | The status page's id. |
No output schema declared.
No examples provided.
instatus_get_component Get component ~78
Get a single component by id — its full state (name, description, status, order, showUptime, grouped, archived). Instatus: GET /v2/{page_id}/components/{component_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| component_id | string | yes | The component's id. |
| page_id | string | yes | The status page's id. |
No output schema declared.
No examples provided.
instatus_get_incident Get incident ~71
Get a single incident by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/incidents/{incident_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | string | yes | The incident's id. |
| page_id | string | yes | The status page's id. |
No output schema declared.
No examples provided.
instatus_get_maintenance Get maintenance ~73
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| maintenance_id | string | yes | The maintenance's id. |
| page_id | string | yes | The status page's id. |
No output schema declared.
No examples provided.
instatus_list_components List components ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number to fetch (default 1). |
| page_id | string | yes | The status page's id (from list_pages). |
| per_page | integer | – | Items per page (default 50, max 100). |
No output schema declared.
No examples provided.
instatus_list_incidents List incidents ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number to fetch (default 1). |
| page_id | string | yes | 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). |
No output schema declared.
No examples provided.
instatus_list_maintenances List maintenances ~103
List a status page's scheduled maintenances, most recent first — id, name, status, affected components, start/end, updates. Instatus: GET /v2/{page_id}/maintenances.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number to fetch (default 1). |
| page_id | string | yes | The status page's id. |
| per_page | integer | – | Items per page (default 50, max 100). |
No output schema declared.
No examples provided.
instatus_list_pages List pages ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number to fetch (default 1). |
| per_page | integer | – | Items per page (default 50, max 100). |
No output schema declared.
No examples provided.
instatus_update_component Update component ~214
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.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | Whether the component is archived (hidden). |
| component_id | string | yes | 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 | yes | The status page's id. |
| showUptime | boolean | – | Whether to show the uptime graph for this component. |
| status | string | – | Operational status of the component. |
No output schema declared.
No examples provided.
instatus_update_incident Update incident ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| components | array | – | Component ids affected by this incident. |
| incident_id | string | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
instatus_update_maintenance Update maintenance ~215
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
How do I install the Instatus MCP by usefulapi server?
Instatus MCP by usefulapi is a hosted endpoint at https://instatus.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.
remote · instatus.usefulapi.io
claude mcp add --transport http io-usefulapi-instatus 'https://instatus.usefulapi.io/mcp'
What is the Instatus MCP by usefulapi server?
Instatus MCP by usefulapi is listed in the public MCP registry as io.usefulapi/instatus. Manage status pages: components, incidents and maintenances; set live component status. This page covers its hosted endpoint (https://instatus.usefulapi.io/mcp).
Is the Instatus MCP by usefulapi server safe to use?
Instatus MCP by usefulapi scores 18 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 Instatus MCP by usefulapi server expose?
Instatus MCP by usefulapi exposes 14 tools: instatus_list_pages, instatus_list_components, instatus_get_component, instatus_list_incidents, instatus_get_incident, and 9 more. Their descriptions and schemas cost roughly 1,917 tokens of context every time the server is loaded.
Does the Instatus MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Instatus MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Instatus MCP by usefulapi server still maintained?
Instatus MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.