MCP server

Status.io MCP by usefulapi

io.usefulapi/status-io

Checked 26 Oct 2026, 08:29 UTC · Connected to it and listed its tools

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

Website Source

At a glance

Type

MCP server

Publisher

usefulapi.io (verified by the MCP Registry)

Status

Working at last check

Tools

20

Token cost

About 6,412 tokens per request

Sets up in

Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok

Last checked

26 Oct 2026, 08:29 UTC

Connect it to your agent

Add to CursorAdd to VS CodeVS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

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

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

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

Gemini CLI

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

Cursor

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

VS Code

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

Antigravity

agy mcp add status-io https://status-io.usefulapi.io/mcp

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"status-io","server_url":"https://status-io.usefulapi.io/mcp","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"status-io","server_url":"https://status-io.usefulapi.io/mcp"}

Tools

• statusio_create_incident ~727 tokens
  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
• statusio_finish_maintenance ~481 tokens
  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 ~180 tokens
  One incident in full: components, containers, infrastructure affected and all its messages. GET /incident/{statuspage_id}/{incident_id}.
• statusio_get_incident_message ~176 tokens
  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 ~184 tokens
  One maintenance event in full, with all messages and the infrastructure affected. GET /maintenance/{statuspage_id}/{maintenance_id}.
• statusio_get_maintenance_message ~164 tokens
  One message of a maintenance event. GET /maintenance/message/{statuspage_id}/{message_id}.
• statusio_get_status_summary ~156 tokens
  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 ~180 tokens
  Active (unresolved) incidents with their messages and affected components. GET /incident/list/active/{statuspage_id}.
• statusio_list_components ~169 tokens
  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 ~141 tokens
  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 ~257 tokens
  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 ~134 tokens
  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 ~181 tokens
  Resolved incidents (history) with their messages and affected components. GET /incident/list/resolved/{statuspage_id}.
• statusio_list_subscribers ~176 tokens
  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_i
• statusio_resolve_incident ~471 tokens
  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 ~749 tokens
  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
• statusio_start_maintenance ~485 tokens
  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 ~351 tokens
  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 ~583 tokens
  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 ~467 tokens
  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.

Browse

• Website monitoring
• Email
• Team chat
• Social media

Related MCP servers

• Instatus MCP by usefulapi
  Manage status pages: components, incidents and maintenances; set live component status.
• StatusPal MCP by usefulapi
  Read status-page status, services, incidents and metrics; create, update and publish incidents.
• Web Reader & Search (Tanod)
  Web search for agents: page to Markdown, screenshots, news search, metadata, sitemaps and RDAP.
• Nslookup
  DNS lookups, health reports, SSL certs, security scans, GEO scoring, uptime checks
• Uptimepage
  Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.
• Devops Status
  Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.
• StatusCake MCP by usefulapi
  Review uptime, SSL, pagespeed and heartbeat checks, alerts and maintenance windows; create checks.
• Squadcast MCP by usefulapi
  Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents.

Badge for your README

[![AptLynx](https://aptlynx.net/badge/io.usefulapi/status-io.svg)](https://aptlynx.net/servers/io.usefulapi/status-io)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents