Connect-MCP

Status.io MCP by usefulapi

io.usefulapi/status-io · v1.0.0

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

MCPremoteno credentialsMessaging

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 20 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 88/100

What it does: 20 tools · 12 read, 8 write (incl. delete/pay) · Messaging

Test call statusio_get_status_summary: needs a key: HTTP 401 (964 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://status-io.usefulapi.io/mcp

Tools

20 tools listed at last check
  • 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_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_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 /maintenance/list/{pending|active|closed}/{statuspage_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_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_i
  • 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_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
  • 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_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
  • 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_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.
  • 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.

Badge

Connect-MCP badge for io.usefulapi/status-io

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.usefulapi/status-io.svg)](https://clawy.uk/mcp/s/io.usefulapi/status-io)

Repository · Website