Status.io MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Status.io MCP by usefulapi is answering right now. Last checked 4 min ago. It exposes 20 tools. Last commit 12 Oct 2026.

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

Uptime history 4 hours of history

4 hours agonow

100.0%

Uptime 24h

12 of 12 checks

Tools

read from the server

123 ms

Response time

average over 24h

Stars

last commit 12 Oct 2026

Nothing serious here today

Today is the operative word: we check Status.io MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 20

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

statusio

statusio_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.

statusio_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.

statusio_get_incident

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

statusio_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}.

statusio_get_maintenance

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

statusio_get_maintenance_message

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

statusio_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}.

statusio_list_active_incidents

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

statusio_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}.

statusio_list_incidents

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}.

statusio_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}.

statusio_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}.

statusio_list_resolved_incidents

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

statusio_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}.

statusio_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.

statusio_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.

statusio_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.

statusio_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.

statusio_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.

statusio_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.

Endpoints

URL	Transport	State	Latency	Checked
https://status-io.usefulapi.io/mcp	streamable-http	answering	168 ms	4 min ago

Alternatives to Status.io MCP by usefulapi

same job, measured the same way

Instatus MCP by usefulapi

by usefulapi

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

14 tools answering

StatusPal MCP by usefulapi

by usefulapi

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

11 tools answering

Squadcast MCP by usefulapi

by usefulapi

Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents.

16 tools answering

Better Stack MCP by usefulapi

by usefulapi

Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.

9 tools answering

StatusCake MCP by usefulapi

by usefulapi

Review uptime, SSL, pagespeed and heartbeat checks, alerts and maintenance windows; create checks.

21 tools answering

Dead Man's Snitch MCP by usefulapi

by usefulapi

Read Dead Man's Snitch monitors and status; create, tag, pause and unpause snitches.

8 tools answering

Spike.sh MCP by usefulapi

by usefulapi

Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.

16 tools answering

updown.io MCP by usefulapi

by usefulapi

Check updown.io uptime checks, downtimes, response metrics and status pages, and create checks.

14 tools answering

Status.io MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Status.io MCP by usefulapi do?

It exposes 20 tools, read directly from the server on our last check. Among them: statusio_create_incident, statusio_finish_maintenance, statusio_get_incident, statusio_get_incident_message, statusio_get_maintenance, statusio_get_maintenance_message and 14 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Status.io MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 12 of 12 checks got a reply (100.0%), average response time 123 ms. The bar chart above shows every period we have measured.

How do I connect Status.io MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Status.io MCP by usefulapi need an API key?

No. Status.io MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 20 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Status.io MCP by usefulapi?

It answers our handshake in 123 ms on average, which is faster than 78% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Status.io MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.