Instatus MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.16.3 · published by io.usefulapi

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

Deletes · 7

Compare Registry entry

14 tools: 7 can delete or cancel things and 7 only read.

Scanned Oct 21, 2026

Deletes or cancels7Claude Code: deny: see these tools
Can't be undone0Claude Code: ask
Changes things0Claude Code: ask
Only reads7Claude Code: allow: see these tools

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Findings

Matches of fixed checks, with the text they matched.

1 warn

Warninstatus_list_pages
The description contains "every other tool", wording about other tools or servers.
Matched text
description: "...in, and timestamps. The page id is what every other tool takes as `page_id`. Instatus: GET /v2/p..."
What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

14 tools

Deletes or cancels 7Removes, cancels or revokes something.Claude Code: deny

instatus_create_incidentCREATES a new incident — this MODIFIES live status-page data and can notify subscribers.No findings
Why it is in this group
- The name "instatus_create_incident" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- title: Create incident
- destructiveHint: true
instatus_create_maintenanceCREATES a new scheduled maintenance — this MODIFIES live status-page data and can notify subscribers.No findings
Why it is in this group
- The name "instatus_create_maintenance" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- title: Create maintenance
- destructiveHint: true
instatus_delete_incidentPERMANENTLY DELETES an incident by id — this MODIFIES live status-page data and cannot be undone.No findings
Why it is in this group
- The name "instatus_delete_incident" says "delete": a word for removing or ending something.
- The description says "PERMANENTLY DELETES".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
PERMANENTLY DELETES an incident by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/incidents/{incident_id}.
Annotations the server declares
- title: Delete incident
- destructiveHint: true
instatus_delete_maintenancePERMANENTLY DELETES a scheduled maintenance by id — this MODIFIES live status-page data and cannot be undone.No findings
Why it is in this group
- The name "instatus_delete_maintenance" says "delete": a word for removing or ending something.
- The description says "PERMANENTLY DELETES".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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}.
Annotations the server declares
- title: Delete maintenance
- destructiveHint: true
instatus_update_componentUPDATES a component by id — this MODIFIES live status-page data.No findings
Why it is in this group
- The name "instatus_update_component" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- title: Update component
- destructiveHint: true
instatus_update_incidentUPDATES an existing incident by id — this MODIFIES live status-page data and can notify subscribers (e.g.No findings
Why it is in this group
- The name "instatus_update_incident" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- title: Update incident
- destructiveHint: true
instatus_update_maintenanceUPDATES an existing scheduled maintenance by id — this MODIFIES live status-page data and can notify subscribers.No findings
Why it is in this group
- The name "instatus_update_maintenance" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- title: Update maintenance
- destructiveHint: true

Only reads 7Looks things up and changes nothing.Claude Code: allow

instatus_get_componentGet a single component by id — its full state (name, description, status, order, showUptime, grouped, archived).No findings
Why it is in this group
- The name "instatus_get_component" says "get": a word for reading.
Description, as the server wrote it
Get a single component by id — its full state (name, description, status, order, showUptime, grouped, archived). Instatus: GET /v2/{page_id}/components/{component_id}.
Annotations the server declares
- title: Get component
- readOnlyHint: true
instatus_get_incidentGet a single incident by id — its full state including its update timeline and affected components.No findings
Why it is in this group
- The name "instatus_get_incident" says "get": a word for reading.
Description, as the server wrote it
Get a single incident by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/incidents/{incident_id}.
Annotations the server declares
- title: Get incident
- readOnlyHint: true
instatus_get_maintenanceGet a single scheduled maintenance by id — its full state including its update timeline and affected components.No findings
Why it is in this group
- The name "instatus_get_maintenance" says "get": a word for reading.
Description, as the server wrote it
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}.
Annotations the server declares
- title: Get maintenance
- readOnlyHint: true
instatus_list_componentsList a status page's components — id, name, description, status, order, showUptime, grouped, archived.No findings
Why it is in this group
- The name "instatus_list_components" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: List components
- readOnlyHint: true
instatus_list_incidentsList a status page's incidents, most recent first — optionally filtered by status.No findings
Why it is in this group
- The name "instatus_list_incidents" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: List incidents
- readOnlyHint: true
instatus_list_maintenancesList a status page's scheduled maintenances, most recent first — id, name, status, affected components, start/end, updates.No findings
Why it is in this group
- The name "instatus_list_maintenances" says "list": a word for reading.
Description, as the server wrote it
List a status page's scheduled maintenances, most recent first — id, name, status, affected components, start/end, updates. Instatus: GET /v2/{page_id}/maintenances.
Annotations the server declares
- title: List maintenances
- readOnlyHint: true
instatus_list_pagesList all status pages on the account — each page's id, subdomain, name, status, url, custom domain, and timestamps.1 finding
Why it is in this group
- The name "instatus_list_pages" says "list": a word for reading.
Findings
- Warn
  The description contains "every other tool", wording about other tools or servers.
  Matched text
  description: "...in, and timestamps. The page id is what every other tool takes as `page_id`. Instatus: GET /v2/p..."
  What this check looks for
Description, as the server wrote it
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.
Annotations the server declares
- title: List pages
- readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.16.3. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__instatus__instatus_list_pages",
      "mcp__instatus__instatus_list_components",
      "mcp__instatus__instatus_get_component",
      "mcp__instatus__instatus_list_incidents",
      "mcp__instatus__instatus_get_incident",
      "mcp__instatus__instatus_list_maintenances",
      "mcp__instatus__instatus_get_maintenance"
    ],
    "ask": [],
    "deny": [
      "mcp__instatus__instatus_update_component",
      "mcp__instatus__instatus_create_incident",
      "mcp__instatus__instatus_update_incident",
      "mcp__instatus__instatus_delete_incident",
      "mcp__instatus__instatus_create_maintenance",
      "mcp__instatus__instatus_update_maintenance",
      "mcp__instatus__instatus_delete_maintenance"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as instatus. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.usefulapi/instatus/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

7 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 19:23 UTC.

For agents: Markdown · JSON · report this listing