← All launches
Status.io MCP by usefulapi logo
0 Report

Status.io MCP by usefulapi

by FastDrop

MCP Verified 2 hours ago Registry import free

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

Read Status.io components, incidents, maintenance; post incidents, schedule maintenance, set status. Official MCP Registry: io.usefulapi/status-io@1.0.0. Remote endpoint: https://status-io.usefulapi.io/mcp

Problem it solves

Discoverable MCP server listed in the official MCP Registry.

How it's different

Remote MCP endpoint ingested from the official registry and probed by FastDrop.

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.usefulapi/status-io and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Claim this listing

Tools this endpoint exposes

Read directly from the endpoint on 12 Oct 2026. Not supplied by the maker.

  • 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 /s

  • 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 af

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

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.

Sign in to claim this listing

Matched on shared tags and the tools their MCP servers actually expose.

Reviews

Sign in to leave a review.

No reviews yet.

Comments

Sign in to join the discussion.

No comments yet - start the discussion.