mcpbeat Sign in

Instatus MCP by usefulapi MCP Server

answering

Instatus MCP by usefulapi is answering right now. Last checked 14 min ago. It exposes 14 tools. Last commit 2 Nov 2026.

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

Uptime history 91 days of history · worst day 4%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
14
Tools
read from the server
162 ms
Response time
average over 24h
1
Stars
last commit 2 Nov 2026

What changed 45

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

2 Nov a tool changed version
31 Oct a tool changed version4 times that day
30 Oct a tool changed version2 times that day
29 Oct a tool changed version2 times that day
28 Oct a tool changed version2 times that day
27 Oct a tool changed version
25 Oct a tool changed version4 times that day
24 Oct a tool changed version3 times that day
23 Oct a tool changed version
22 Oct a tool changed version
and 35 more, back to 30 September 2026

Instatus MCP by usefulapi missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add instatus --transport http https://instatus.usefulapi.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://instatus.usefulapi.io/mcp
~/.codex/config.toml
[mcp_servers.instatus]
url = "https://instatus.usefulapi.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "instatus": {
      "url": "https://instatus.usefulapi.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "instatus": {
      "type": "http",
      "url": "https://instatus.usefulapi.io/mcp"
    }
  }
}

Available tools 14

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

instatus
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-component impact via `statuses`, `status`, `started`, `notify`, and `shouldPublish`. Instatus: POST /v1/{page_id}/incidents. Returns the created incident.
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`, per-component impact via `statuses`, `status`, `start`/`end`, `duration`, and `notify`. Instatus: POST /v1/{page_id}/maintenances. Returns the created maintenance.
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}.
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}.
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}.
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}.
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}.
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}/components.
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 /v1/{page_id}/incidents.
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.
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`. Instatus: GET /v2/pages.
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, PARTIALOUTAGE, MAJOROUTAGE). Send only the fields you want to change. Instatus: PUT /v2/{page_id}/components/{component_id}. Returns the updated component.
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 change. Instatus: PUT /v1/{page_id}/incidents/{incident_id}. Returns the updated incident.
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_id}/maintenances/{maintenance_id}. Returns the updated maintenance.

Endpoints

URLTransportStateLatencyChecked
https://instatus.usefulapi.io/mcp streamable-http answering 68 ms 14 min ago

Alternatives to Instatus MCP by usefulapi

same job, measured the same way
Statuspage MCP by usefulapi
by usefulapi

Read pages, components, incidents and maintenances; create and update incidents in Statuspage.

15 tools answering
Status.io MCP by usefulapi
by usefulapi

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

20 tools answering
StatusPage.me MCP by usefulapi
by usefulapi

Read status pages, incidents and monitors, and post incidents and maintenance in StatusPage.me.

14 tools answering
StatusCast MCP by usefulapi
by usefulapi

Read page status, components, uptime, incidents and content templates in StatusCast.

10 tools answering
Instatus
by instatus

Status pages, incidents, maintenance, components and subscribers on Instatus.

answering
openstatus
by openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

answering
StatusPal MCP by usefulapi
by usefulapi

Read status-page status, services, incidents and metrics; create, update and publish incidents.

11 tools answering
Sorry MCP by usefulapi
by usefulapi

Read status pages and incidents; make confirmed public changes and manage individual subscribers.

21 tools answering

Instatus MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Instatus MCP by usefulapi do?
It exposes 14 tools, read directly from the server on our last check. Among them: instatus_create_incident, instatus_create_maintenance, instatus_delete_incident, instatus_delete_maintenance, instatus_get_component, instatus_get_incident and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Instatus MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 162 ms. The bar chart above shows every period we have measured.
How do I connect Instatus MCP by usefulapi?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Instatus MCP by usefulapi need an API key?
No. Instatus MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Instatus MCP by usefulapi?
It answers our handshake in 162 ms on average, which is faster than 80% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Instatus MCP by usefulapi open source?
The code is open source: it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at instatus.usefulapi.io, which runs on its operator's own terms.