Skip to content

Squadcast MCP by usefulapi

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

Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents.

16 tools: 3 can delete or cancel things and 13 only read.

Tools: 3 delete, 0 irreversible, 0 write, 13 read.
  • Reads private data · 2
  • 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

3 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 Squadcast MCP by usefulapi can do

The Squadcast MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 16 tools. It can delete or cancel things (3 tools: squadcast_acknowledge_incident, squadcast_resolve_incident and squadcast_add_incident_note). 13 tools only read.

2 tools read private data (squadcast_list_incident_notes and squadcast_resolve_incident); 1 tool brings in text other people can write (squadcast_resolve_incident).

The fixed checks matched 1 finding (annotation-conflict). 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.

16 tools

Deletes or cancels 3Claude Code: deny
  • squadcast_acknowledge_incidentAcknowledge a triggered incident on the LIVE account (stops escalation/paging for it).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Acknowledge a triggered incident on the LIVE account (stops escalation/paging for it). Squadcast: POST /v3/incidents/{incidentID}/acknowledge.

    Annotations the server declares

    • title: Acknowledge incident
    • destructiveHint: true
  • squadcast_add_incident_noteAdd a war-room note to a LIVE incident (optionally with attachment URLs).No findings

    Why it is in this group

    • The name "squadcast_add_incident_note" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Add a war-room note to a LIVE incident (optionally with attachment URLs). Squadcast: POST /v3/incidents/{IncidentId}/warroom.

    Annotations the server declares

    • title: Add incident note
    • destructiveHint: true
  • squadcast_resolve_incidentResolve an incident on the LIVE account, recording a resolution message.Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "squadcast_resolve_incident" says "resolve": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • private-dataThe description's first sentence says "resolve" and "message": it reads messages.
    • untrusted-inputThe description's first sentence says "resolve" and "message": it reads messages, which other people can write.

    Findings

    • Warn

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

      Matched text

      annotations: {"destructiveHint":true}; The name "squadcast_resolve_incident" says "resolve": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Resolve an incident on the LIVE account, recording a resolution message. Squadcast: POST /v3/incidents/{incidentID}/resolve.

    Annotations the server declares

    • title: Resolve incident
    • destructiveHint: true
Only reads 13Show 13 read-only tools
  • squadcast_get_incidentGet a single incident by its id.No findings

    Why it is in this group

    • The name "squadcast_get_incident" says "get": a word for reading.
    Description, as the server wrote it
    Get a single incident by its id. Squadcast: GET /v3/incidents/{incidentID}.

    Annotations the server declares

    • title: Get incident
    • readOnlyHint: true
  • squadcast_get_incident_eventsGet the timeline of events for a single incident (state changes, notifications, actions).No findings

    Why it is in this group

    • The name "squadcast_get_incident_events" says "get": a word for reading.
    Description, as the server wrote it
    Get the timeline of events for a single incident (state changes, notifications, actions). Squadcast: GET /v3/incidents/{incidentID}/events.

    Annotations the server declares

    • title: Get incident events
    • readOnlyHint: true
  • squadcast_get_serviceGet a single service by its id.No findings

    Why it is in this group

    • The name "squadcast_get_service" says "get": a word for reading.
    Description, as the server wrote it
    Get a single service by its id. Squadcast: GET /v3/services/{serviceID}.

    Annotations the server declares

    • title: Get service
    • readOnlyHint: true
  • squadcast_get_teamGet a single team by its id.No findings

    Why it is in this group

    • The name "squadcast_get_team" says "get": a word for reading.
    Description, as the server wrote it
    Get a single team by its id. Squadcast: GET /v3/teams/{teamId}.

    Annotations the server declares

    • title: Get team
    • readOnlyHint: true
  • squadcast_get_userGet a single user by their id.No findings

    Why it is in this group

    • The name "squadcast_get_user" says "get": a word for reading.
    Description, as the server wrote it
    Get a single user by their id. Squadcast: GET /v3/users/{userID}.

    Annotations the server declares

    • title: Get user
    • readOnlyHint: true
  • squadcast_list_escalation_policiesList escalation policies for a team.No findings

    Why it is in this group

    • The name "squadcast_list_escalation_policies" says "list": a word for reading.
    Description, as the server wrote it
    List escalation policies for a team. `owner_id` (a TEAM id — use squadcast_list_teams to find it) is REQUIRED. Squadcast: GET /v3/escalation-policies.

    Annotations the server declares

    • title: List escalation policies
    • readOnlyHint: true
  • squadcast_list_incident_notesList the war-room notes on a single incident.Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "squadcast_list_incident_notes" says "list" and "note": it reads notes.
    • private-dataThe description's first sentence says "list" and "note": it reads notes.
    Description, as the server wrote it
    List the war-room notes on a single incident. Squadcast: GET /v3/incidents/{IncidentId}/warroom.

    Annotations the server declares

    • title: List incident notes
    • readOnlyHint: true
  • squadcast_list_incidentsSearch/list incidents over a time window with filters (status, service, priority, assignee, tags, sources, starred, SLO-affecting) and sorting.No findings

    Why it is in this group

    • The name "squadcast_list_incidents" says "list": a word for reading.
    Description, as the server wrote it
    Search/list incidents over a time window with filters (status, service, priority, assignee, tags, sources, starred, SLO-affecting) and sorting. `start_time`, `end_time` (both ISO8601) and `owner_id` (a TEAM id — use squadcast_list_teams to find it) are REQUIRED. Squadcast: GET /v3/incidents/export.

    Annotations the server declares

    • title: List incidents
    • readOnlyHint: true
  • squadcast_list_schedulesList on-call schedules for a team.No findings

    Why it is in this group

    • The name "squadcast_list_schedules" says "list": a word for reading.
    Description, as the server wrote it
    List on-call schedules for a team. `teamID` is REQUIRED (use squadcast_list_teams to find it). Set `myOnCall` to filter to schedules where the token's own user is currently on call — the 'who's on call' lens. Squadcast: GET /v4/schedules.

    Annotations the server declares

    • title: List schedules (on-call)
    • readOnlyHint: true
  • squadcast_list_servicesList services for a team.No findings

    Why it is in this group

    • The name "squadcast_list_services" says "list": a word for reading.
    Description, as the server wrote it
    List services for a team. `owner_id` (a TEAM id — use squadcast_list_teams to find it) is REQUIRED. Squadcast: GET /v3/services.

    Annotations the server declares

    • title: List services
    • readOnlyHint: true
  • squadcast_list_squadsList squads for a team.No findings

    Why it is in this group

    • The name "squadcast_list_squads" says "list": a word for reading.
    Description, as the server wrote it
    List squads for a team. `owner_id` (a TEAM id — use squadcast_list_teams to find it) is REQUIRED. Squadcast: GET /v4/squads.

    Annotations the server declares

    • title: List squads
    • readOnlyHint: true
  • squadcast_list_teamsList all teams in the organization.No findings

    Why it is in this group

    • The name "squadcast_list_teams" says "list": a word for reading.
    Description, as the server wrote it
    List all teams in the organization. A team id is the `owner_id`/`teamID` several other tools require. Squadcast: GET /v3/teams.

    Annotations the server declares

    • title: List teams
    • readOnlyHint: true
  • squadcast_list_usersList all users in the organization.No findings

    Why it is in this group

    • The name "squadcast_list_users" says "list": a word for reading.
    Description, as the server wrote it
    List all users in the organization. Squadcast: GET /v3/users.

    Annotations the server declares

    • title: List users
    • 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 outbound.

Reads private data2
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: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

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

    Matched text

    annotations: {"destructiveHint":true}; The name "squadcast_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: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://squadcast.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://squadcast.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 squadcast https://squadcast.usefulapi.io/mcp
claude mcp add --transport http squadcast https://squadcast.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__squadcast__squadcast_list_incidents",
      "mcp__squadcast__squadcast_get_incident",
      "mcp__squadcast__squadcast_get_incident_events",
      "mcp__squadcast__squadcast_list_incident_notes",
      "mcp__squadcast__squadcast_list_services",
      "mcp__squadcast__squadcast_get_service",
      "mcp__squadcast__squadcast_list_users",
      "mcp__squadcast__squadcast_get_user",
      "mcp__squadcast__squadcast_list_teams",
      "mcp__squadcast__squadcast_get_team",
      "mcp__squadcast__squadcast_list_squads",
      "mcp__squadcast__squadcast_list_schedules",
      "mcp__squadcast__squadcast_list_escalation_policies"
    ],
    "ask": [],
    "deny": [
      "mcp__squadcast__squadcast_acknowledge_incident",
      "mcp__squadcast__squadcast_resolve_incident",
      "mcp__squadcast__squadcast_add_incident_note"
    ]
  }
}

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 squadcast. Review it before you use it.

Capability tags behind 2 rules
  • mcp__squadcast__squadcast_list_incident_notes private-data
  • mcp__squadcast__squadcast_resolve_incident private-data, 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/squadcast/verify?hash=bbfae01e39d10a7e89e43fe63a5875abf7ccb089aab52cbd6c644a7ade55662a" | jq -e '.changed == false'

Pinned hash bbfae01e39d1, 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/squadcast/changes.xml

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

Badge

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

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

Squadcast MCP by usefulapi: questions and answers

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

Is the Squadcast MCP by usefulapi safe?

No scan can promise that. What its definitions show: 16 tools, 3 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 Squadcast MCP by usefulapi delete data?

Yes. 3 tools can delete, cancel or revoke something: squadcast_acknowledge_incident, squadcast_resolve_incident and squadcast_add_incident_note.

Can the Squadcast 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 Squadcast MCP by usefulapi have?

16 tools: 3 destructive, 13 read. squadcast_acknowledge_incident, squadcast_resolve_incident, squadcast_add_incident_note, squadcast_list_incidents, squadcast_get_incident, squadcast_get_incident_events, squadcast_list_incident_notes, squadcast_list_services and 8 more.

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

Its remote endpoint did not answer the last anonymous look.

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

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