Status.io MCP by usefulapi
REMOTE · STATUS-IO.USEFULAPI.IO
Read Status.io components, incidents, maintenance; post incidents, schedule maintenance, set status.
Available components
Last scanned (4 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 17 Oct 26 +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.
- 14 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 59
First indexed and scored.
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 17 Oct 2026 · Probed https://status-io.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 status-io.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://status-io.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://status-io.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://status-io.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://status-io.usefulapi.io/mcp |
| Authorisation server | https://status-io.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://status-io.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/status-io/ |
| http (plaintext) | http://status-io.usefulapi.io/mcp | Inconclusive | 302 | http://status-io.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 →
statusio_create_incident Create incident ~352
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.
| Name | Type | Req | Description |
|---|---|---|---|
| all_infrastructure_affected | boolean | – | true = every component and container is affected. Otherwise give infrastructure_affected. |
| details | string | yes | 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 | yes | 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 | yes | Status the affected components get. |
| statuspage_id | string | – | Status page id. Defaults to the status page chosen when you connected. |
No output schema declared.
No examples provided.
statusio_finish_maintenance Finish maintenance ~244
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.
| Name | Type | Req | Description |
|---|---|---|---|
| details | string | yes | Message describing this maintenance update. |
| maintenance_id | string | yes | 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. |
No output schema declared.
No examples provided.
statusio_get_incident Get incident ~83
One incident in full: components, containers, infrastructure affected and all its messages. GET /incident/{statuspage_id}/{incident_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | string | yes | 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. |
No output schema declared.
No examples provided.
statusio_get_incident_message Get incident message ~87
One message (update) of an incident: text, state, status, time and the user who posted it. GET /incident/message/{statuspage_id}/{message_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | Incident message id (from statusio_get_incident). |
| statuspage_id | string | – | Status page id. Defaults to the status page chosen when you connected. |
No output schema declared.
No examples provided.
statusio_get_maintenance Get maintenance ~82
One maintenance event in full, with all messages and the infrastructure affected. GET /maintenance/{statuspage_id}/{maintenance_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| maintenance_id | string | yes | 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. |
No output schema declared.
No examples provided.
statusio_get_maintenance_message Get maintenance message ~71
One message of a maintenance event. GET /maintenance/message/{statuspage_id}/{message_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | Maintenance message id (from statusio_get_maintenance). |
| statuspage_id | string | – | Status page id. Defaults to the status page chosen when you connected. |
No output schema declared.
No examples provided.
statusio_get_status_summary Get status summary ~80
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| statuspage_id | string | – | Status page id. Defaults to the status page chosen when you connected. |
No output schema declared.
No examples provided.
statusio_list_active_incidents List active incidents ~93
Active (unresolved) incidents with their messages and affected components. GET /incident/list/active/{statuspage_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
statusio_list_components List components ~90
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| statuspage_id | string | – | Status page id. Defaults to the status page chosen when you connected. |
No output schema declared.
No examples provided.
statusio_list_incidents List incident ids ~75
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| statuspage_id | string | – | Status page id. Defaults to the status page chosen when you connected. |
No output schema declared.
No examples provided.
statusio_list_maintenance List maintenance ~134
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
statusio_list_maintenance_ids List maintenance ids ~68
The ids of all active, closed and upcoming maintenance events (ids only). Fetch one with statusio_get_maintenance. GET /maintenances/{statuspage_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| statuspage_id | string | – | Status page id. Defaults to the status page chosen when you connected. |
No output schema declared.
No examples provided.
statusio_list_resolved_incidents List resolved incidents ~94
Resolved incidents (history) with their messages and affected components. GET /incident/list/resolved/{statuspage_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
statusio_list_subscribers List subscribers ~92
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| statuspage_id | string | – | Status page id. Defaults to the status page chosen when you connected. |
No output schema declared.
No examples provided.
statusio_resolve_incident Resolve incident ~240
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.
| Name | Type | Req | Description |
|---|---|---|---|
| details | string | yes | Message describing the resolution. |
| incident_id | string | yes | 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. |
No output schema declared.
No examples provided.
statusio_schedule_maintenance Schedule maintenance ~403
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Message describing the maintenance. |
| end | string | yes | 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 | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
statusio_start_maintenance Start maintenance ~245
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.
| Name | Type | Req | Description |
|---|---|---|---|
| details | string | yes | Message describing this maintenance update. |
| maintenance_id | string | yes | 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. |
No output schema declared.
No examples provided.
statusio_update_component_status Update component status ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| component_id | string | yes | Component id. |
| container_id | string | yes | Container id; it must be attached to that component. |
| details | string | yes | Short message shown with the status change. |
| status | string | yes | New status level. |
| statuspage_id | string | – | Status page id. Defaults to the status page chosen when you connected. |
No output schema declared.
No examples provided.
statusio_update_incident Update incident ~279
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.
| Name | Type | Req | Description |
|---|---|---|---|
| details | string | yes | Message describing this update. |
| incident_id | string | yes | 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 | yes | Incident state now. |
| status | string | yes | Status the affected components get now. |
| statuspage_id | string | – | Status page id. Defaults to the status page chosen when you connected. |
No output schema declared.
No examples provided.
statusio_update_maintenance Update maintenance ~236
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.
| Name | Type | Req | Description |
|---|---|---|---|
| details | string | yes | Message describing this maintenance update. |
| maintenance_id | string | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · status-io.usefulapi.io
claude mcp add --transport http io-usefulapi-status-io 'https://status-io.usefulapi.io/mcp'
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.