MCP serverio.usefulapi/instatus

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

UNRATEDActivestreamable-httpinstatus.usefulapi.io

Overview

Score?

UNRATED 0.143

of what a free look can see, on 17 looks

Looks

last 10 hr ago

Tools

More info

URL

instatus.usefulapi.io/mcp

streamable-http

Says it is

instatus-mcp 1.0.0

protocol 2025-06-18

In the record since

32 days ago

Among servers18,413 with a card

0median 0.606 · this server 0.143 · highest on record 0.8561

Toolsfrom sha256:0e630c0d3f…a23e32

The tools this server lists, read out of the definition it returned
Tool	Schema
instatus_create_incident 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	input · no output
instatus_create_maintenance CREATES a new scheduled maintenance — this MODIFIES live status-page data and can notify subscribers. Provide `name` (required); optionally set `message`, affected `components`, pe	input · no output
instatus_delete_incident PERMANENTLY DELETES an incident by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/incidents/{incident_id}.	input · no output
instatus_delete_maintenance 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}.	input · no output
instatus_get_component Get a single component by id — its full state (name, description, status, order, showUptime, grouped, archived). Instatus: GET /v2/{page_id}/components/{component_id}.	input · no output
instatus_get_incident Get a single incident by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/incidents/{incident_id}.	input · no output
instatus_get_maintenance 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}.	input · no output
instatus_list_components 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}/com	input · no output
instatus_list_incidents 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	input · no output
instatus_list_maintenances List a status page's scheduled maintenances, most recent first — id, name, status, affected components, start/end, updates. Instatus: GET /v2/{page_id}/maintenances.	input · no output
instatus_list_pages 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`. Instatu	input · no output
instatus_update_component UPDATES a component by id — this MODIFIES live status-page data. The key way to set a component's operational status (OPERATIONAL, UNDERMAINTENANCE, DEGRADEDPERFORMANCE, PARTIALOUT	input · no output
instatus_update_incident 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 chang	input · no output
instatus_update_maintenance 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_i	input · no output

Verify it yourselfnpx teppi-check https://instatus.usefulapi.io/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1FZ2PK6DWFNSB62DVJC8SZJ