Skip to content

Status.io MCP by usefulapi

io.usefulapi/status-iousefulapi.iostreamable-httpv1.27.4Scanned

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

20 tools: 8 can delete or cancel things and 12 only read.

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

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

Anlyon alternative

8 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 Status.io MCP by usefulapi can do

The Status.io MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 20 tools. It can delete or cancel things (8 tools: statusio_update_component_status, statusio_create_incident, statusio_update_incident, statusio_resolve_incident and 4 more). 12 tools only read.

9 tools read private data (statusio_list_active_incidents, statusio_list_resolved_incidents, statusio_get_incident and 6 more); 20 tools bring in text other people can write (statusio_get_status_summary, statusio_list_components, statusio_list_incidents and 17 more).

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

Last scanned Oct 25, 2026, version 1.27.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.

20 tools

Deletes or cancels 8Claude Code: deny
  • statusio_create_incidentWRITE: open a new incident on the PUBLIC status page.Reads text others writeNo findings

    Why it is in this group

    • The name "statusio_create_incident" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: open a new incident on the PUBLIC status page. It is visible to every visitor immediately and sets the status of the affected components. No subscriber, Slack, Teams, IRC or Twitter notification is sent unless you switch it on (notify_*). Returns the new incident id. Say what is affected with all_infrastructure_affected or infrastructure_affected pairs. POST /incident/create.

    Annotations the server declares

    • title: Create incident
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • statusio_finish_maintenanceWRITE: finish an active maintenance event; it moves to history and the affected components return to operational.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "write": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: finish an active maintenance event; it moves to history and the affected components return to operational. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/finish.

    Annotations the server declares

    • title: Finish maintenance
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • statusio_resolve_incidentWRITE: resolve an incident with a closing message.Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "statusio_resolve_incident" says "resolve": a word for reading.
    • The description's first verb is "write": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "write" and "message": it reads messages, which other people can write.

    Findings

    • Warn

      The server marks "statusio_resolve_incident" destructive (destructiveHint: true), and its name says "resolve", a word for reading.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true,"openWorldHint":true}; The name "statusio_resolve_incident" says "resolve": a word for reading.

      What this check looks for
    Description, as the server wrote it
    WRITE: resolve an incident with a closing message. The affected components return to operational and the incident moves to history. No notification is sent unless you switch it on (notify_*). POST /incident/resolve.

    Annotations the server declares

    • title: Resolve incident
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • statusio_schedule_maintenanceWRITE: schedule a planned maintenance on the PUBLIC status page.Reads text others writeNo findings

    Why it is in this group

    • The name "statusio_schedule_maintenance" says "schedule": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: schedule a planned maintenance on the PUBLIC status page. It is visible to visitors as upcoming maintenance. Subscribers are told only if you switch on notify_now / notify_72_hr / notify_24_hr / notify_1_hr (all default off). With automation true Status.io starts and ends it by itself at the planned times. Returns the maintenance id. POST /maintenance/schedule.

    Annotations the server declares

    • title: Schedule maintenance
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • statusio_start_maintenanceWRITE: start a scheduled maintenance now; it moves from pending to active and the affected components show planned maintenance.Reads text others writeNo findings

    Why it is in this group

    • The name "statusio_start_maintenance" says "start": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: start a scheduled maintenance now; it moves from pending to active and the affected components show planned maintenance. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/start.

    Annotations the server declares

    • title: Start maintenance
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • statusio_update_component_statusWRITE: change the PUBLIC status of one component/container pair (for example to degraded_performance) without creating an incident.Reads text others writeNo findings

    Why it is in this group

    • The name "statusio_update_component_status" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: change the PUBLIC status of one component/container pair (for example to degraded_performance) without creating an incident. It changes what visitors of your status page see right away. Set it back to operational when done. Ids from statusio_list_components. POST /component/status/update.

    Annotations the server declares

    • title: Update component status
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • statusio_update_incidentWRITE: post a new update message on an existing incident and set its state and component status.Reads text others writeNo findings

    Why it is in this group

    • The name "statusio_update_incident" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: post a new update message on an existing incident and set its state and component status. The message is public at once. No subscriber or channel notification is sent unless you switch it on (notify_*). To close an incident use statusio_resolve_incident. POST /incident/update.

    Annotations the server declares

    • title: Update incident
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • statusio_update_maintenanceWRITE: post a new status message on an active maintenance event.Reads text others writeNo findings

    Why it is in this group

    • The name "statusio_update_maintenance" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: post a new status message on an active maintenance event. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/update.

    Annotations the server declares

    • title: Update maintenance
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Only reads 12Show 12 read-only tools
  • statusio_get_incidentOne incident in full: components, containers, infrastructure affected and all its messages.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "statusio_get_incident" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    One incident in full: components, containers, infrastructure affected and all its messages. GET /incident/{statuspage_id}/{incident_id}.

    Annotations the server declares

    • title: Get incident
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • statusio_get_incident_messageOne message (update) of an incident: text, state, status, time and the user who posted it.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "statusio_get_incident_message" says "get": a word for reading.

    What it can reach

    • private-dataThe name "statusio_get_incident_message" says "get" and "message": it reads messages.
    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "statusio_get_incident_message" says "get" and "message": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    One message (update) of an incident: text, state, status, time and the user who posted it. GET /incident/message/{statuspage_id}/{message_id}.

    Annotations the server declares

    • title: Get incident message
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • statusio_get_maintenanceOne maintenance event in full, with all messages and the infrastructure affected.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "statusio_get_maintenance" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    One maintenance event in full, with all messages and the infrastructure affected. GET /maintenance/{statuspage_id}/{maintenance_id}.

    Annotations the server declares

    • title: Get maintenance
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • statusio_get_maintenance_messageOne message of a maintenance event.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "statusio_get_maintenance_message" says "get": a word for reading.

    What it can reach

    • private-dataThe name "statusio_get_maintenance_message" says "get" and "message": it reads messages.
    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "statusio_get_maintenance_message" says "get" and "message": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    One message of a maintenance event. GET /maintenance/message/{statuspage_id}/{message_id}.

    Annotations the server declares

    • title: Get maintenance message
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • statusio_get_status_summaryThe current state of the status page in one call: overall status, every component and container with its status code and last update, open incidents and active/upcoming maintenance…Reads text others writeNo findings

    Why it is in this group

    • The name "statusio_get_status_summary" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The current state of the status page in one call: overall status, every component and container with its status code and last update, open incidents and active/upcoming maintenance. Start here. GET /status/summary/{statuspage_id}.

    Annotations the server declares

    • title: Get status summary
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • statusio_list_active_incidentsActive (unresolved) incidents with their messages and affected components.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    Active (unresolved) incidents with their messages and affected components. GET /incident/list/active/{statuspage_id}.

    Annotations the server declares

    • title: List active incidents
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • statusio_list_componentsList the components of the status page and the containers (data centers / locations) attached to each, with ids.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List the components of the status page and the containers (data centers / locations) attached to each, with ids. Component and container ids are needed to update a status or to say what an incident affects ('<component_id>-<container_id>'). GET /component/list/{statuspage_id}.

    Annotations the server declares

    • title: List components
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • statusio_list_incidentsThe ids of all active and resolved incidents (ids only, no details): a quick way to see which incidents exist.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The ids of all active and resolved incidents (ids only, no details): a quick way to see which incidents exist. Fetch one with statusio_get_incident. GET /incidents/{statuspage_id}.

    Annotations the server declares

    • title: List incident ids
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • statusio_list_maintenanceMaintenance events in one state, with messages and affected components: pending (scheduled, not started), active (in progress) or closed (finished).Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    Maintenance events in one state, with messages and affected components: pending (scheduled, not started), active (in progress) or closed (finished). GET /maintenance/list/{pending|active|closed}/{statuspage_id}.

    Annotations the server declares

    • title: List maintenance
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • statusio_list_maintenance_idsThe ids of all active, closed and upcoming maintenance events (ids only).Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The ids of all active, closed and upcoming maintenance events (ids only). Fetch one with statusio_get_maintenance. GET /maintenances/{statuspage_id}.

    Annotations the server declares

    • title: List maintenance ids
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • statusio_list_resolved_incidentsResolved incidents (history) with their messages and affected components.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    Resolved incidents (history) with their messages and affected components. GET /incident/list/resolved/{statuspage_id}.

    Annotations the server declares

    • title: List resolved incidents
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • statusio_list_subscribersList the people and endpoints subscribed to the status page (email addresses, phone numbers, webhook hosts) with ids and their granular preferences.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    List the people and endpoints subscribed to the status page (email addresses, phone numbers, webhook hosts) with ids and their granular preferences. This is personal data of your subscribers. Webhook URLs are shortened to their host, because they can carry secrets. GET /subscriber/list/{statuspage_id}.

    Annotations the server declares

    • title: List subscribers
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: 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 outbound.

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:38 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: 8 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://status-io.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://status-io.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 server marks "statusio_resolve_incident" destructive (destructiveHint: true), and its name says "resolve", a word for reading.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true,"openWorldHint":true}; The name "statusio_resolve_incident" says "resolve": a word for reading.

    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: 8 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://status-io.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://status-io.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

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

claude mcp add --transport http status-io https://status-io.usefulapi.io/mcp
claude mcp add --transport http status-io https://status-io.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__status-io__statusio_get_status_summary",
      "mcp__status-io__statusio_list_components",
      "mcp__status-io__statusio_list_incidents",
      "mcp__status-io__statusio_list_active_incidents",
      "mcp__status-io__statusio_list_resolved_incidents",
      "mcp__status-io__statusio_get_incident",
      "mcp__status-io__statusio_get_incident_message",
      "mcp__status-io__statusio_list_maintenance_ids",
      "mcp__status-io__statusio_list_maintenance",
      "mcp__status-io__statusio_get_maintenance",
      "mcp__status-io__statusio_get_maintenance_message",
      "mcp__status-io__statusio_list_subscribers"
    ],
    "ask": [],
    "deny": [
      "mcp__status-io__statusio_update_component_status",
      "mcp__status-io__statusio_create_incident",
      "mcp__status-io__statusio_update_incident",
      "mcp__status-io__statusio_resolve_incident",
      "mcp__status-io__statusio_schedule_maintenance",
      "mcp__status-io__statusio_start_maintenance",
      "mcp__status-io__statusio_update_maintenance",
      "mcp__status-io__statusio_finish_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 status-io. Review it before you use it.

Capability tags behind 20 rules
  • mcp__status-io__statusio_get_status_summary untrusted-input
  • mcp__status-io__statusio_list_components untrusted-input
  • mcp__status-io__statusio_list_incidents untrusted-input
  • mcp__status-io__statusio_list_active_incidents private-data, untrusted-input
  • mcp__status-io__statusio_list_resolved_incidents private-data, untrusted-input
  • mcp__status-io__statusio_get_incident private-data, untrusted-input
  • mcp__status-io__statusio_get_incident_message private-data, untrusted-input
  • mcp__status-io__statusio_list_maintenance_ids untrusted-input
  • mcp__status-io__statusio_list_maintenance private-data, untrusted-input
  • mcp__status-io__statusio_get_maintenance private-data, untrusted-input
  • mcp__status-io__statusio_get_maintenance_message private-data, untrusted-input
  • mcp__status-io__statusio_list_subscribers private-data, untrusted-input
  • mcp__status-io__statusio_update_component_status untrusted-input
  • mcp__status-io__statusio_create_incident untrusted-input
  • mcp__status-io__statusio_update_incident untrusted-input
  • mcp__status-io__statusio_resolve_incident private-data, untrusted-input
  • mcp__status-io__statusio_schedule_maintenance untrusted-input
  • mcp__status-io__statusio_start_maintenance untrusted-input
  • mcp__status-io__statusio_update_maintenance untrusted-input
  • mcp__status-io__statusio_finish_maintenance 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/status-io/verify?hash=a717c29c896bbe3d120612cee906cf1ae91fd0698460b3ff8fa5517d3943633a" | jq -e '.changed == false'

Pinned hash a717c29c896b, from Oct 25, 2026, 23:18 UTC.

Watch

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

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

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

Badge

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

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

Status.io MCP by usefulapi: questions and answers

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

Is the Status.io MCP by usefulapi safe?

No scan can promise that. What its definitions show: 20 tools, 8 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 Status.io MCP by usefulapi delete data?

Yes. 8 tools can delete, cancel or revoke something: statusio_update_component_status, statusio_create_incident, statusio_update_incident, statusio_resolve_incident, statusio_schedule_maintenance, statusio_start_maintenance and 2 more.

Can the Status.io 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 Status.io MCP by usefulapi have?

20 tools: 8 destructive, 12 read. statusio_update_component_status, statusio_create_incident, statusio_update_incident, statusio_resolve_incident, statusio_schedule_maintenance, statusio_start_maintenance, statusio_update_maintenance, statusio_finish_maintenance and 12 more.

Does the Status.io MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Status.io 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 Status.io MCP by usefulapi changed its tools?

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