StatusPal MCP by usefulapi
io.usefulapi/statuspalusefulapi.iostreamable-httpv1.40.4Scanned
Read status-page status, services, incidents and metrics; create, update and publish incidents.
11 tools: 4 can delete or cancel things and 7 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
4 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 StatusPal MCP by usefulapi can do
The StatusPal MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 11 tools. It can delete or cancel things (4 tools: statuspal_create_incident, statuspal_update_incident, statuspal_create_incident_update and statuspal_delete_incident). 7 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
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.
11 tools
Deletes or cancels 4Claude Code: deny
statuspal_create_incidentPUBLISHES a new incident to the LIVE public status page (and, with notify=true, emails/notifies subscribers).No findings
Why it is in this group
- The name "statuspal_create_incident" says "create": a word for a change.
- The description's first verb is "publish": a word for a change that another call does not undo.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it PUBLISHES a new incident to the LIVE public status page (and, with notify=true, emails/notifies subscribers). type="major" or "minor" is an outage incident; type="scheduled" creates a scheduled maintenance window. StatusPal: POST /status_pages/{subdomain}/incidents.
Annotations the server declares
- title: Create incident
- destructiveHint: true
statuspal_create_incident_updatePOSTS an update (e.g.No findings
Why it is in this group
- The name "statuspal_create_incident_update" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it POSTS an update (e.g. investigating → identified → monitoring → resolved) to an existing incident on the LIVE public status page (and, with notify=true, notifies subscribers). StatusPal: POST /status_pages/{subdomain}/incidents/{incident_id}/updates.
Annotations the server declares
- title: Post incident update
- destructiveHint: true
statuspal_delete_incidentDELETES an incident from the LIVE public status page — this permanently removes it.No findings
Why it is in this group
- The name "statuspal_delete_incident" says "delete": a word for removing or ending something.
- The description says "permanently removes".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it DELETES an incident from the LIVE public status page — this permanently removes it. StatusPal: DELETE /status_pages/{subdomain}/incidents/{incident_id}.
Annotations the server declares
- title: Delete incident
- destructiveHint: true
statuspal_update_incidentUPDATES an existing incident on the LIVE public status page (title/type/services/timing).No findings
Why it is in this group
- The name "statuspal_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 on the LIVE public status page (title/type/services/timing). StatusPal: PUT /status_pages/{subdomain}/incidents/{incident_id}.
Annotations the server declares
- title: Update incident
- destructiveHint: true
Only reads 7Show 7 read-only tools
statuspal_get_incidentGet a single incident by its id.No findings
Why it is in this group
- The name "statuspal_get_incident" says "get": a word for reading.
Description, as the server wrote it Get a single incident by its id. StatusPal: GET /status_pages/{subdomain}/incidents/{incident_id}.
Annotations the server declares
- title: Get incident
- readOnlyHint: true
statuspal_get_service_statusGet the current status of a single service by its id.No findings
Why it is in this group
- The name "statuspal_get_service_status" says "get": a word for reading.
Description, as the server wrote it Get the current status of a single service by its id. StatusPal: GET /status_pages/{subdomain}/services/{service_id}/status.
Annotations the server declares
- title: Get service status
- readOnlyHint: true
statuspal_get_statusGet the current overall status of the status page (the aggregate status type).No findings
Why it is in this group
- The name "statuspal_get_status" says "get": a word for reading.
Description, as the server wrote it Get the current overall status of the status page (the aggregate status type). StatusPal: GET /status_pages/{subdomain}/status.
Annotations the server declares
- title: Get overall status
- readOnlyHint: true
statuspal_get_summaryGet the FULL status-page summary — status_page, services[], incidents[], maintenances[], upcoming_maintenances[], info_notices[], and current_status_type.No findings
Why it is in this group
- The name "statuspal_get_summary" says "get": a word for reading.
Description, as the server wrote it Get the FULL status-page summary — status_page, services[], incidents[], maintenances[], upcoming_maintenances[], info_notices[], and current_status_type. StatusPal: GET /status_pages/{subdomain}/summary.
Annotations the server declares
- title: Get status page summary
- readOnlyHint: true
statuspal_list_incidentsList incidents for a status page.No findings
Why it is in this group
- The name "statuspal_list_incidents" says "list": a word for reading.
Description, as the server wrote it List incidents for a status page. Returns {incidents[], links:{next,prev}, meta:{total_count}}. Use `before`/`after` cursors to paginate and `type` to filter. StatusPal: GET /status_pages/{subdomain}/incidents.
Annotations the server declares
- title: List incidents
- readOnlyHint: true
statuspal_list_metricsList the metrics configured on a status page.No findings
Why it is in this group
- The name "statuspal_list_metrics" says "list": a word for reading.
Description, as the server wrote it List the metrics configured on a status page. Use `before`/`after` cursors to paginate. StatusPal: GET /status_pages/{subdomain}/metrics.
Annotations the server declares
- title: List metrics
- readOnlyHint: true
statuspal_list_servicesList the services on a status page — each with {id, name, current_incident_type, children[]}.No findings
Why it is in this group
- The name "statuspal_list_services" says "list": a word for reading.
Description, as the server wrote it List the services on a status page — each with {id, name, current_incident_type, children[]}. StatusPal: GET /status_pages/{subdomain}/services.
Annotations the server declares
- title: List services
- 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 untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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.
Looked at Nov 20, 2026, 19:37 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
- 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: 4 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://statuspal.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://statuspal.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.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
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: 4 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://statuspal.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://statuspal.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 statuspal https://statuspal.usefulapi.io/mcpclaude mcp add --transport http statuspal https://statuspal.usefulapi.io/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__statuspal__statuspal_get_summary",
"mcp__statuspal__statuspal_get_status",
"mcp__statuspal__statuspal_list_services",
"mcp__statuspal__statuspal_get_service_status",
"mcp__statuspal__statuspal_list_incidents",
"mcp__statuspal__statuspal_get_incident",
"mcp__statuspal__statuspal_list_metrics"
],
"ask": [],
"deny": [
"mcp__statuspal__statuspal_create_incident",
"mcp__statuspal__statuspal_update_incident",
"mcp__statuspal__statuspal_create_incident_update",
"mcp__statuspal__statuspal_delete_incident"
]
}
}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 statuspal. Review it before you use it.
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/statuspal/verify?hash=aebd294129f1692f75a7308990572c3c41c0de941d3a139c4cdecddd05ecb753" | jq -e '.changed == false'Pinned hash aebd294129f1, 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/statuspal/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/statuspal)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.
StatusPal MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the StatusPal MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 11 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the StatusPal MCP by usefulapi delete data?
- Yes. 4 tools can delete, cancel or revoke something: statuspal_create_incident, statuspal_update_incident, statuspal_create_incident_update and statuspal_delete_incident.
Can the StatusPal 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 StatusPal MCP by usefulapi have?
- 11 tools: 4 destructive, 7 read. statuspal_create_incident, statuspal_update_incident, statuspal_create_incident_update, statuspal_delete_incident, statuspal_get_summary, statuspal_get_status, statuspal_list_services, statuspal_get_service_status and 3 more.
Does the StatusPal MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the StatusPal 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 StatusPal MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.