Instatus MCP Server

by usefulapi Your server? Claim it

answering

Instatus is answering right now. Last checked 9 min ago. It exposes 14 tools. Last commit 1 Sep 2026.

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

Uptime history 47 days of history · worst day 4%

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

169 ms

Response time

average over 24h

Stars

last commit 1 Sep 2026

Nothing serious here today

Today is the operative word: we check Instatus every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add instatus --transport http https://instatus.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "instatus": {
      "url": "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

{
  "mcpServers": {
    "instatus": {
      "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

URL	Transport	State	Latency	Checked
https://instatus.usefulapi.io/mcp	streamable-http	answering	239 ms	9 min ago

Alternatives to Instatus

same job, measured the same way

openstatus

by openstatus

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

answering

Uptimely

by getuptimely

Uptime monitoring: monitors, incidents, alerts, maintenance, on-call, status pages and telemetry.

answering

Statuspal

by usefulapi

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

11 tools answering

Vantaj

by vantaj

Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages.

13 tools answering

Downtester Status

by downtester

Live service status, active incidents, search, and outage history from Downtester.

answering

Betterstack

by usefulapi

Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.

9 tools answering

Vendor Status MCP

by approj

Live status-page map for 1,127 SaaS/cloud vendors plus 15,418 historical incidents.

local only

All Quiet

by usefulapi

Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides.

11 tools answering

Instatus — questions

Answers built from our own checks of this server.

What can Instatus 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 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 169 ms. The bar chart above shows every period we have measured.

How do I connect Instatus?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Instatus need an API key?

No. Instatus 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?

It answers our handshake in 169 ms on average, which is faster than 72% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Instatus open source?

Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.