Instatus MCP by usefulapi

Server Details

Manage status pages: components, incidents and maintenances; set live component status.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 80.9% over 54 days
Last Tested: 2026-10-10 23:49
Transport: Streamable HTTP · MCP 2025-06-18
URL
Repository: m190/usefulapi-mcp
GitHub Stars: 0

TDQS

A4.2/5.0

Scored 2026-09-09 19:51 across 14 tools

Disambiguation5/5

Each tool targets a distinct resource-action pair: incidents, maintenances, components, and pages are clearly separated, with list/get/create/update/delete operations mapping cleanly to specific objects. There is no overlap between tools—even the similar create_incident and create_maintenance are differentiated by resource type and purpose.

Naming Consistency5/5

All tools follow the identical `instatus_<verb>_<noun>` pattern with snake_case throughout. The verbs list/get/create/update/delete are applied consistently across incidents, maintenances, and components, making the API surface predictable.

Tool Count5/5

14 tools is well within the ideal range for a status-page management server. Each tool maps to a distinct REST operation on a core resource (pages, components, incidents, maintenances), and none feel redundant or unnecessary.

Completeness4/5

Incidents and maintenances have full CRUD coverage, and components have list/get/update which covers the primary use case of changing operational status. Missing create/delete for components and pages, but those are less central and can be worked around; the core incident/maintenance workflow is complete.

Available Tools

14 tools

instatus_create_incidentCreate incident

Destructive

Inspect

CREATES a new incident — this MODIFIES live status-page data and can notify subscribers. Provide name (required); optionally set the initial message, affected components, per-component impact via statuses, status, started, notify, and shouldPublish. Instatus: POST /v1/{page_id}/incidents. Returns the created incident.

ParametersJSON Schema

Name	Required	Description
`name`	Yes	Incident title (required).
`notify`	No	Whether to notify subscribers about this update.
`status`	No	Incident status.
`message`	No	Incident update message (Markdown supported).
`page_id`	Yes	The status page's id.
`started`	No	ISO 8601 timestamp for when the incident started.
`statuses`	No	Per-component impact — set each listed component's status for this event.
`components`	No	Component ids affected by this incident.
`shouldPublish`	No	Whether the incident should be published to the status page.

instatus_create_maintenanceCreate maintenance

Destructive

Inspect

CREATES a new scheduled maintenance — this MODIFIES live status-page data and can notify subscribers. Provide name (required); optionally set message, affected components, per-component impact via statuses, status, start/end, duration, and notify. Instatus: POST /v1/{page_id}/maintenances. Returns the created maintenance.

ParametersJSON Schema

Name	Required	Description
`end`	No	ISO 8601 timestamp for when the maintenance ends.
`name`	Yes	Maintenance title (required).
`start`	No	ISO 8601 timestamp for when the maintenance starts.
`notify`	No	Whether to notify subscribers about this update.
`status`	No	Maintenance status.
`message`	No	Maintenance update message (Markdown supported).
`page_id`	Yes	The status page's id.
`duration`	No	Maintenance duration in minutes.
`statuses`	No	Per-component impact — set each listed component's status for this event.
`components`	No	Component ids affected by this maintenance.

instatus_delete_incidentDelete incident

Destructive

Inspect

PERMANENTLY DELETES an incident by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/incidents/{incident_id}.

ParametersJSON Schema

Name	Required	Description	Default
`page_id`	Yes	The status page's id.
`incident_id`	Yes	The incident's id to delete.

instatus_delete_maintenanceDelete maintenance

Destructive

Inspect

PERMANENTLY DELETES a scheduled maintenance by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/maintenances/{maintenance_id}.

ParametersJSON Schema

Name	Required	Description	Default
`page_id`	Yes	The status page's id.
`maintenance_id`	Yes	The maintenance's id to delete.

instatus_get_componentGet component

Read-only

Inspect

Get a single component by id — its full state (name, description, status, order, showUptime, grouped, archived). Instatus: GET /v2/{page_id}/components/{component_id}.

ParametersJSON Schema

Name	Required	Description	Default
`page_id`	Yes	The status page's id.
`component_id`	Yes	The component's id.

instatus_get_incidentGet incident

Read-only

Inspect

Get a single incident by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/incidents/{incident_id}.

ParametersJSON Schema

Name	Required	Description	Default
`page_id`	Yes	The status page's id.
`incident_id`	Yes	The incident's id.

instatus_get_maintenanceGet maintenance

Read-only

Inspect

Get a single scheduled maintenance by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/maintenances/{maintenance_id}.

ParametersJSON Schema

Name	Required	Description	Default
`page_id`	Yes	The status page's id.
`maintenance_id`	Yes	The maintenance's id.

instatus_list_componentsList components

Read-only

Inspect

List a status page's components — id, name, description, status, order, showUptime, grouped, archived. The component ids are what you set impact on. Instatus: GET /v2/{page_id}/components.

ParametersJSON Schema

Name	Required	Description
`page`	No	Page number to fetch (default 1).
`page_id`	Yes	The status page's id (from list_pages).
`per_page`	No	Items per page (default 50, max 100).

instatus_list_incidentsList incidents

Read-only

Inspect

List a status page's incidents, most recent first — optionally filtered by status. Each incident: id, name, status, impact, affected components, updates, timestamps. Instatus: GET /v1/{page_id}/incidents.

ParametersJSON Schema

Name	Required	Description
`page`	No	Page number to fetch (default 1).
`status`	No	Filter to incidents with this status (INVESTIGATING, IDENTIFIED, MONITORING, RESOLVED).
`page_id`	Yes	The status page's id.
`per_page`	No	Items per page (default 50, max 100).

instatus_list_maintenancesList maintenances

Read-only

Inspect

List a status page's scheduled maintenances, most recent first — id, name, status, affected components, start/end, updates. Instatus: GET /v2/{page_id}/maintenances.

ParametersJSON Schema

Name	Required	Description
`page`	No	Page number to fetch (default 1).
`page_id`	Yes	The status page's id.
`per_page`	No	Items per page (default 50, max 100).

instatus_list_pagesList pages

Read-only

Inspect

List all status pages on the account — each page's id, subdomain, name, status, url, custom domain, and timestamps. The page id is what every other tool takes as page_id. Instatus: GET /v2/pages.

ParametersJSON Schema

Name	Required	Description	Default
`page`	No	Page number to fetch (default 1).
`per_page`	No	Items per page (default 50, max 100).

instatus_update_componentUpdate component

Destructive

Inspect

UPDATES a component by id — this MODIFIES live status-page data. The key way to set a component's operational status (OPERATIONAL, UNDERMAINTENANCE, DEGRADEDPERFORMANCE, PARTIALOUTAGE, MAJOROUTAGE). Send only the fields you want to change. Instatus: PUT /v2/{page_id}/components/{component_id}. Returns the updated component.

ParametersJSON Schema

Name	Required	Description
`name`	No	Component name.
`order`	No	Display order of the component on the page.
`status`	No	Operational status of the component.
`grouped`	No	Whether the component is displayed within a group.
`page_id`	Yes	The status page's id.
`archived`	No	Whether the component is archived (hidden).
`showUptime`	No	Whether to show the uptime graph for this component.
`description`	No	Free-form component description.
`component_id`	Yes	The component's id to update.

instatus_update_incidentUpdate incident

Destructive

Inspect

UPDATES an existing incident by id — this MODIFIES live status-page data and can notify subscribers (e.g. move it to MONITORING or RESOLVED). Send only the fields you want to change. Instatus: PUT /v1/{page_id}/incidents/{incident_id}. Returns the updated incident.

ParametersJSON Schema

Name	Required	Description
`name`	No	Incident title.
`notify`	No	Whether to notify subscribers about this update.
`status`	No	Incident status.
`message`	No	Incident update message (Markdown supported).
`page_id`	Yes	The status page's id.
`started`	No	ISO 8601 timestamp for when the incident started.
`statuses`	No	Per-component impact — set each listed component's status for this event.
`components`	No	Component ids affected by this incident.
`incident_id`	Yes	The incident's id to update.
`shouldPublish`	No	Whether the incident should be published to the status page.

instatus_update_maintenanceUpdate maintenance

Destructive

Inspect

UPDATES an existing scheduled maintenance by id — this MODIFIES live status-page data and can notify subscribers. Send only the fields you want to change. Instatus: PUT /v1/{page_id}/maintenances/{maintenance_id}. Returns the updated maintenance.

ParametersJSON Schema

Name	Required	Description
`end`	No	ISO 8601 timestamp for when the maintenance ends.
`name`	No	Maintenance title.
`start`	No	ISO 8601 timestamp for when the maintenance starts.
`notify`	No	Whether to notify subscribers about this update.
`status`	No	Maintenance status.
`message`	No	Maintenance update message (Markdown supported).
`page_id`	Yes	The status page's id.
`duration`	No	Maintenance duration in minutes.
`statuses`	No	Per-component impact — set each listed component's status for this event.
`components`	No	Component ids affected by this maintenance.
`maintenance_id`	Yes	The maintenance's id to update.