io.usefulapiPublished by usefulapi.ioOfficial publisherv1.23.5Updated Nov 8, 2026
Read Status.io components, incidents, maintenance; post incidents, schedule maintenance, set status.
The publisher's own server: Ably MCP by usefulapi
Status.io MCP by usefulapi's hosted MCP server (status-io.usefulapi.io), published by usefulapi.io; no sign-in required; Streamable HTTP; 20 tools.
No AI overview yet: these facts come from the registry entry and the server itself.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.usefulapi%2Fstatus-io/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"status-io-by-usefulapi": {
"type": "http",
"url": "https://status-io.usefulapi.io/mcp"
}
}
}Use Status.io from Claude, Cursor, or any MCP client — status page components, incidents, maintenance windows and subscribers, plus incident and maintenance updates. Hosted, no local install: connect with your own Status.io credentials.
Live endpoint: https://status-io.usefulapi.io/mcp · Homepage: https://usefulapi.io/status-io
https://status-io.usefulapi.io/mcp.claude mcp add --transport http status-io https://status-io.usefulapi.io/mcp, then run /mcp to log in.Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Status.io credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/status-io/
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this server only. Subscribe with statusio_upgrade (it returns a Stripe Checkout link). Cancel any time with statusio_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running statusio_upgrade before then undoes the cancel. Or write to [email protected].
MIT © usefulapi. Not affiliated with or endorsed by Status.io.
Source: servers/status-io/README.md at commit 4046075
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}.
statuspage_idList 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}.
statuspage_idList incident ids
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}.
statuspage_idList active incidents
Active (unresolved) incidents with their messages and affected components. GET /incident/list/active/{statuspage_id}.
pagestatuspage_idList resolved incidents
Resolved incidents (history) with their messages and affected components. GET /incident/list/resolved/{statuspage_id}.
pagestatuspage_idGet incident
One incident in full: components, containers, infrastructure affected and all its messages. GET /incident/{statuspage_id}/{incident_id}.
incident_idrequiredstatuspage_idGet 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}.
message_idrequiredstatuspage_idList maintenance ids
The ids of all active, closed and upcoming maintenance events (ids only). Fetch one with statusio_get_maintenance. GET /maintenances/{statuspage_id}.
statuspage_idList 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}.
pagestaterequiredstatuspage_idGet maintenance
One maintenance event in full, with all messages and the infrastructure affected. GET /maintenance/{statuspage_id}/{maintenance_id}.
statuspage_idmaintenance_idrequiredGet maintenance message
One message of a maintenance event. GET /maintenance/message/{statuspage_id}/{message_id}.
message_idrequiredstatuspage_idList 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}.
statuspage_idUpdate 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.
statusrequireddetailsrequiredcomponent_idrequiredcontainer_idrequiredstatuspage_idCreate 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.
namerequiredstatestatusrequireddetailsrequirednotify_ircnotify_smsnotify_emailnotify_slackstatuspage_idnotify_msteamsnotify_webhookmessage_subject+3 moreUpdate 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.
staterequiredstatusrequireddetailsrequirednotify_ircnotify_smsincident_idrequirednotify_emailnotify_slackstatuspage_idnotify_msteamsnotify_webhookmessage_subject+1 moreResolve 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.
detailsrequirednotify_ircnotify_smsincident_idrequirednotify_emailnotify_slackstatuspage_idnotify_msteamsnotify_webhookmessage_subjectpost_to_twitterSchedule 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.
endrequirednamerequiredstartrequireddetailsrequiredautomationnotify_nownotify_1_hrnotify_24_hrnotify_72_hrstatuspage_idmessage_subjectautomation_stop_text+3 moreStart 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.
detailsrequirednotify_ircnotify_smsnotify_emailnotify_slackstatuspage_idmaintenance_idrequirednotify_msteamsnotify_webhookmessage_subjectpost_to_twitterUpdate 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.
detailsrequirednotify_ircnotify_smsnotify_emailnotify_slackstatuspage_idmaintenance_idrequirednotify_msteamsnotify_webhookmessage_subjectpost_to_twitterFinish 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.
detailsrequirednotify_ircnotify_smsnotify_emailnotify_slackstatuspage_idmaintenance_idrequirednotify_msteamsnotify_webhookmessage_subjectpost_to_twitter100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
io.usefulapiOfficial publisher
Ably MCP by usefulapi's hosted MCP server, published by usefulapi.io; no sign-in required; Streamable HTTP; 15 tools.
io.usefulapiOfficial publisher
Hosted read-only MCP server that lets an assistant read Tiltify campaigns, donations and top donor and fundraiser leaderboards.
io.usefulapiOfficial publisher
Hosted Termii server that lets an assistant send SMS, check wallet balance, DND status, sender IDs and message history.
io.usefulapiOfficial publisher
Hosted MCP server that lets an assistant read Temp Stick temperature and humidity sensors, their readings and alert notifications.
io.usefulapiOfficial publisher
Connects an assistant to a Stibee email marketing workspace to read address books, subscribers and email stats, and to add subscribers and group members.
{ "mcpServers": { "status-io": { "url": "https://status-io.usefulapi.io/mcp" } }}