io.usefulapi/status-io

up checked 2026-11-11T15:37:53.470Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

Status.io MCP by usefulapi

Publisher-provided description

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

Summary by lookupd

Lets agents read and manage a Status.io page: view components, incidents and maintenance, and publish public status changes.

Install

Claude Code, remote (streamable-http)

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

Codex, remote (streamable-http)

codex mcp add status-io --url https://status-io.usefulapi.io/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

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

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (20 tools)

Publisher-provided text

• 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/
• 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 updat
• 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 /incide
• statusio_list_active_incidents Active (unresolved) incidents with their messages and affected components. GET /incident/list/active/{statuspage_id}.
• statusio_list_resolved_incidents Resolved incidents (history) with their messages and affected components. GET /incident/list/resolved/{statuspage_id}.
• 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_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_maintenance Maintenance events in one state, with messages and affected components: pending (scheduled, not started), active (in progress) or closed (finished). GET /mainte
• 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_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 per
• 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
• 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,
• 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 notific
• 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 unle
• 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 n
• 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. N
• 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
• 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

Details

• Version: 1.24.3
• Transports: streamable-http
• Uptime (7 days): 100%
• Median latency: 402 ms
• First indexed: 2026-11-01T10:06:19.189Z
• Last seen in registry: 2026-11-11T00:17:34.645Z
• Repository: https://github.com/m190/usefulapi-mcp
• Website: https://usefulapi.io/status-io/

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/io.usefulapi/status-io.svg)](https://lookupd.com/servers/io.usefulapi/status-io)

• 62071 servers
• Last crawl: 2026-11-11T16:39:06.253Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp