io.usefulapi/squadcast
REMOTE · SQUADCAST.USEFULAPI.IO · SCANNED SEP 20
Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1369 tokens (~85/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/squadcast MCP server?
io.usefulapi/squadcast is a hosted endpoint at https://squadcast.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · squadcast.usefulapi.io
claude mcp add --transport http io-usefulapi-squadcast 'https://squadcast.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-squadcast": {
"url": "https://squadcast.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-squadcast": {
"type": "http",
"url": "https://squadcast.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-squadcast] url = "https://squadcast.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-squadcast": {
"type": "remote",
"url": "https://squadcast.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-squadcast --url 'https://squadcast.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-squadcast:
url: "https://squadcast.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-squadcast": {
"Transport": "http",
"Url": "https://squadcast.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-squadcast -t streamable-http -u 'https://squadcast.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-squadcast": {
"type": "http",
"url": "https://squadcast.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 −6
- Stability: pass → 0.60 functional
- 3 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://squadcast.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 4ebd90eded478ab31305b93d7fb9a554 |
| SANs: usefulapi.io, squadcast.usefulapi.io, *.squadcast.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of squadcast.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://squadcast.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://squadcast.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://squadcast.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://squadcast.usefulapi.io/mcp |
| Authorisation server | https://squadcast.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://squadcast.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://squadcast.usefulapi.io/mcp | Inconclusive | 401 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
squadcast_acknowledge_incident Acknowledge incident ~64
Acknowledge a triggered incident on the LIVE account (stops escalation/paging for it). Squadcast: POST /v3/incidents/{incidentID}/acknowledge.
| Name | Type | Req | Description |
|---|---|---|---|
| incidentId | string | yes | The incident id to acknowledge (required). |
No output schema declared.
No examples provided.
squadcast_add_incident_note Add incident note ~87
Add a war-room note to a LIVE incident (optionally with attachment URLs). Squadcast: POST /v3/incidents/{IncidentId}/warroom.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | array | – | Attachment URLs (defaults to none). |
| incidentId | string | yes | The incident id to add a note to (required). |
| message | string | yes | The note message (required). |
No output schema declared.
No examples provided.
squadcast_get_incident Get incident ~45
Get a single incident by its id. Squadcast: GET /v3/incidents/{incidentID}.
| Name | Type | Req | Description |
|---|---|---|---|
| incidentId | string | yes | The incident id (required). |
No output schema declared.
No examples provided.
squadcast_get_incident_events Get incident events ~57
Get the timeline of events for a single incident (state changes, notifications, actions). Squadcast: GET /v3/incidents/{incidentID}/events.
| Name | Type | Req | Description |
|---|---|---|---|
| incidentId | string | yes | The incident id (required). |
No output schema declared.
No examples provided.
squadcast_get_service Get service ~43
Get a single service by its id. Squadcast: GET /v3/services/{serviceID}.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceId | string | yes | The service id (required). |
No output schema declared.
No examples provided.
squadcast_get_team Get team ~44
Get a single team by its id. Squadcast: GET /v3/teams/{teamId}.
| Name | Type | Req | Description |
|---|---|---|---|
| teamId | string | yes | The team id (required). |
No output schema declared.
No examples provided.
squadcast_get_user Get user ~43
Get a single user by their id. Squadcast: GET /v3/users/{userID}.
| Name | Type | Req | Description |
|---|---|---|---|
| userId | string | yes | The user id (required). |
No output schema declared.
No examples provided.
squadcast_list_escalation_policies List escalation policies ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ownerId | string | yes | Team id that owns the escalation policies (required) → owner_id. |
| pageNumber | number | – | Page number → page_number. |
| pageSize | number | – | Page size → page_size. |
No output schema declared.
No examples provided.
squadcast_list_incident_notes List incident notes ~51
List the war-room notes on a single incident. Squadcast: GET /v3/incidents/{IncidentId}/warroom.
| Name | Type | Req | Description |
|---|---|---|---|
| incidentId | string | yes | The incident id (required). |
No output schema declared.
No examples provided.
squadcast_list_incidents List incidents ~330
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.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedTo | array | – | Filter by assignee id(s) → assigned_to. |
| endTime | string | yes | ISO8601 end of the window (required) → end_time. |
| isStarred | string | – | Filter to starred incidents → is_starred. |
| ownerId | string | yes | Team id that owns the incidents (required) → owner_id. Use squadcast_list_teams to find it. |
| priority | array | – | Filter by priority (e.g. P1..P5) → priority. |
| services | array | – | Filter by service id(s) → services. |
| sloAffecting | string | – | Filter by SLO-affecting → slo_affecting. |
| sortBy | string | – | Sort field → sort_by. |
| sources | array | – | Filter by alert source(s) → sources. |
| startTime | string | yes | ISO8601 start of the window (required) → start_time. |
| status | array | – | Filter by incident status(es) → status. |
| tags | array | – | Filter by tag(s) → tags. |
| textFilter | string | – | Free-text filter → textFilter. |
No output schema declared.
No examples provided.
squadcast_list_schedules List schedules (on-call) ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor → cursor. |
| myOnCall | boolean | – | Only schedules where the token's user is on call now → myOnCall (the 'who's on call' lens). |
| pageSize | number | – | Page size → pageSize. |
| participants | array | – | Filter by participant user id(s) → participants. |
| scheduleName | string | – | Filter by schedule name → scheduleName. |
| search | string | – | Free-text search → search. |
| teamId | string | yes | Team id whose schedules to list (required) → teamID. |
No output schema declared.
No examples provided.
squadcast_list_services List services ~95
List services for a team. `owner_id` (a TEAM id — use squadcast_list_teams to find it) is REQUIRED. Squadcast: GET /v3/services.
| Name | Type | Req | Description |
|---|---|---|---|
| entityOwner | string | – | Filter by entity owner → entity_owner. |
| name | string | – | Filter by service name → name. |
| ownerId | string | yes | Team id that owns the services (required) → owner_id. |
No output schema declared.
No examples provided.
squadcast_list_squads List squads ~71
List squads for a team. `owner_id` (a TEAM id — use squadcast_list_teams to find it) is REQUIRED. Squadcast: GET /v4/squads.
| Name | Type | Req | Description |
|---|---|---|---|
| ownerId | string | yes | Team id that owns the squads (required) → owner_id. |
No output schema declared.
No examples provided.
squadcast_list_teams List teams ~47
List all teams in the organization. A team id is the `owner_id`/`teamID` several other tools require. Squadcast: GET /v3/teams.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
squadcast_list_users List users ~26
List all users in the organization. Squadcast: GET /v3/users.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
squadcast_resolve_incident Resolve incident ~67
Resolve an incident on the LIVE account, recording a resolution message. Squadcast: POST /v3/incidents/{incidentID}/resolve.
| Name | Type | Req | Description |
|---|---|---|---|
| incidentId | string | yes | The incident id to resolve (required). |
| message | string | yes | Resolution reason/message (required). |
No output schema declared.
No examples provided.
What is the io.usefulapi/squadcast MCP server?
io.usefulapi/squadcast is an MCP server listed in the public MCP registry as io.usefulapi/squadcast. Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents. This page covers its hosted endpoint (https://squadcast.usefulapi.io/mcp).
Is the io.usefulapi/squadcast MCP server safe to use?
io.usefulapi/squadcast scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.usefulapi/squadcast MCP server expose?
io.usefulapi/squadcast exposes 16 tools: squadcast_list_incidents, squadcast_get_incident, squadcast_get_incident_events, squadcast_list_incident_notes, squadcast_list_services, and 11 more. Their descriptions and schemas cost roughly 1,369 tokens of context every time the server is loaded.
Does the io.usefulapi/squadcast MCP server require authentication?
Yes. io.usefulapi/squadcast asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/squadcast MCP server still maintained?
io.usefulapi/squadcast is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.