Skip to content

Instatus MCP by usefulapi

io.usefulapi/instatususefulapi.iostreamable-httpv1.40.4Scanned

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

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

Tools: 7 delete, 0 irreversible, 0 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

The remote endpoint did not answer the last look. Remote posture

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 Radar 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 →

What the Instatus MCP by usefulapi can do

The Instatus MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (7 tools: instatus_update_component, instatus_create_incident, instatus_update_incident, instatus_delete_incident and 3 more). 7 tools only read.

1 tool brings in text other people can write (instatus_list_pages).

The fixed checks matched 1 finding (tool-shadowing). Each one comes with the text it matched.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Deletes or cancels 7Claude 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 7Show 7 read-only tools
  • 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.Reads text others write1 finding

    Why it is in this group

    • The name "instatus_list_pages" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.

    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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://instatus.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://instatus.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

1 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

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://instatus.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://instatus.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

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

claude mcp add --transport http instatus https://instatus.usefulapi.io/mcp
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as instatus. Review it before you use it.

Capability tags behind 1 rule
  • mcp__instatus__instatus_list_pages untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/instatus/verify?hash=815fba32538bd99ac027a4ba1b7baa5d5233cc8aff973f4ec055f0ef24b824b9" | jq -e '.changed == false'

Pinned hash 815fba32538b, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/instatus/changes.xml

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

Badge

Anlyon Radar badge for io.usefulapi/instatus
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/instatus.svg)](https://radar.anlyon.com/servers/io.usefulapi/instatus)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Instatus MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Instatus MCP by usefulapi safe?

No scan can promise that. What its definitions show: 14 tools, 7 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Instatus MCP by usefulapi delete data?

Yes. 7 tools can delete, cancel or revoke something: instatus_update_component, instatus_create_incident, instatus_update_incident, instatus_delete_incident, instatus_create_maintenance, instatus_update_maintenance and 1 more.

Can the Instatus MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Instatus MCP by usefulapi have?

14 tools: 7 destructive, 7 read. instatus_update_component, instatus_create_incident, instatus_update_incident, instatus_delete_incident, instatus_create_maintenance, instatus_update_maintenance, instatus_delete_maintenance, instatus_list_pages and 6 more.

Does the Instatus MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Instatus MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Instatus MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.