Skip to content

All Quiet MCP by usefulapi

io.usefulapi/all-quietusefulapi.iostreamable-httpv1.40.4Scanned

Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides.

11 tools: 3 can delete or cancel things, 2 change things and 6 only read.

Tools: 3 delete, 0 irreversible, 2 write, 6 read.
  • Reads private data · 2
  • Reads text others write · 2
  • Can send data out · 0
  • 2 findings

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

Anlyon alternative

5 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 All Quiet MCP by usefulapi can do

The All Quiet MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 11 tools. It can delete or cancel things (3 tools: allquiet_create_incident, allquiet_update_incident and allquiet_create_on_call_override) and create or change data (2 tools: allquiet_who_is_on_call and allquiet_on_call_report). 6 tools only read.

2 tools read private data (allquiet_get_incident_markdown and allquiet_list_users); 2 tools bring in text other people can write (allquiet_get_incident_markdown and allquiet_list_users).

The fixed checks matched 2 findings (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.

11 tools

Deletes or cancels 3Claude Code: deny
  • allquiet_create_incidentCreates a new incident on the LIVE account (may trigger alerting/paging).No findings

    Why it is in this group

    • The name "allquiet_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 on the LIVE account (may trigger alerting/paging). `status` and `severity` are free-form strings the API validates against your account's configuration — common `severity` values include "Warning", "Minor", "Major", "Critical", and `status` reflects the incident lifecycle (e.g. "Open"/"Resolved"); confirm the valid values for your account before calling. All Quiet: POST /v1/incident.

    Annotations the server declares

    • title: Create incident
    • destructiveHint: true
  • allquiet_create_on_call_overrideCreates an on-call override for a user on the LIVE account (temporarily changes who is on call).No findings

    Why it is in this group

    • The name "allquiet_create_on_call_override" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Creates an on-call override for a user on the LIVE account (temporarily changes who is on call). `type` is a free-form override kind and `start`/`end` govern the override window — confirm the valid `type` values for your account. All Quiet: POST /v1/on-call-override.

    Annotations the server declares

    • title: Create on-call override
    • destructiveHint: true
  • allquiet_update_incidentApplies an operation to an existing LIVE incident: change its severity and/or append an intent (a lifecycle action such as acknowledge/resolve/reopen/snooze — a status transition).No findings

    Why it is in this group

    • The name "allquiet_update_incident" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Applies an operation to an existing LIVE incident: change its severity and/or append an intent (a lifecycle action such as acknowledge/resolve/reopen/snooze — a status transition). At least one of `changeSeverity` or `appendIntent` is required. All Quiet: PATCH /v1/incident/{incidentId}.

    Annotations the server declares

    • title: Update incident
    • destructiveHint: true
Changes things 2Claude Code: ask
  • allquiet_on_call_reportGet a summed on-call duration report over a time window, optionally filtered by user/team/escalation tier.1 finding

    Why it is in this group

    • The name "allquiet_on_call_report" says "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "allquiet_on_call_report" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "allquiet_on_call_report" says "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Get a summed on-call duration report over a time window, optionally filtered by user/team/escalation tier. All Quiet: GET /v1/on-call-report/sum.

    Annotations the server declares

    • title: On-call report
    • readOnlyHint: true
  • allquiet_who_is_on_callGet who is currently (or at a given point in time) on call, optionally filtered by team/user.1 finding

    Why it is in this group

    • The name "allquiet_who_is_on_call" says "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "allquiet_who_is_on_call" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "allquiet_who_is_on_call" says "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Get who is currently (or at a given point in time) on call, optionally filtered by team/user. All Quiet: GET /v1/on-call.

    Annotations the server declares

    • title: Who is on call
    • readOnlyHint: true
Only reads 6Show 6 read-only tools
  • allquiet_get_incidentGet a single incident by its id.No findings

    Why it is in this group

    • The name "allquiet_get_incident" says "get": a word for reading.
    Description, as the server wrote it
    Get a single incident by its id. All Quiet: GET /v1/incident/search/{incidentId}.

    Annotations the server declares

    • title: Get incident
    • readOnlyHint: true
  • allquiet_get_incident_markdownGet a markdown rendering of a single incident by its id (useful for pasting into a doc or chat).Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "get" and "doc": it reads documents.
    • untrusted-inputThe description's first sentence says "get" and "chat": it reads messages, which other people can write.
    Description, as the server wrote it
    Get a markdown rendering of a single incident by its id (useful for pasting into a doc or chat). All Quiet: GET /v1/incident/search/{incidentId}/markdown.

    Annotations the server declares

    • title: Get incident as markdown
    • readOnlyHint: true
  • allquiet_list_incidentsSearch/list incidents with filters (status, severity, team, user, search term, archived/snoozed, date range) and pagination.No findings

    Why it is in this group

    • The name "allquiet_list_incidents" says "list": a word for reading.
    Description, as the server wrote it
    Search/list incidents with filters (status, severity, team, user, search term, archived/snoozed, date range) and pagination. All Quiet: GET /v1/incident/search/list.

    Annotations the server declares

    • title: List incidents
    • readOnlyHint: true
  • allquiet_list_on_call_overridesSearch/list on-call overrides for a given user.No findings

    Why it is in this group

    • The name "allquiet_list_on_call_overrides" says "list": a word for reading.
    Description, as the server wrote it
    Search/list on-call overrides for a given user. All Quiet: GET /v1/on-call-override/search/list.

    Annotations the server declares

    • title: List on-call overrides
    • readOnlyHint: true
  • allquiet_list_teamsSearch/list teams, optionally filtered by display name.No findings

    Why it is in this group

    • The name "allquiet_list_teams" says "list": a word for reading.
    Description, as the server wrote it
    Search/list teams, optionally filtered by display name. All Quiet: GET /v1/team/search/list.

    Annotations the server declares

    • title: List teams
    • readOnlyHint: true
  • allquiet_list_usersSearch/list users, optionally filtered by email or display name.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "search" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "search" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Search/list users, optionally filtered by email or display name. All Quiet: GET /v1/user/search/list.

    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 write2
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:31 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: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://all-quiet.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://all-quiet.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.

2 warn
  • The server marks "allquiet_who_is_on_call" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "allquiet_who_is_on_call" says "call": a word for a change.

    What this check looks for
  • The server marks "allquiet_on_call_report" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "allquiet_on_call_report" says "call": a word for a change.

    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: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://all-quiet.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://all-quiet.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 all-quiet https://all-quiet.usefulapi.io/mcp
claude mcp add --transport http all-quiet https://all-quiet.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__all-quiet__allquiet_list_incidents",
      "mcp__all-quiet__allquiet_get_incident",
      "mcp__all-quiet__allquiet_get_incident_markdown",
      "mcp__all-quiet__allquiet_list_teams",
      "mcp__all-quiet__allquiet_list_users",
      "mcp__all-quiet__allquiet_list_on_call_overrides"
    ],
    "ask": [
      "mcp__all-quiet__allquiet_who_is_on_call",
      "mcp__all-quiet__allquiet_on_call_report"
    ],
    "deny": [
      "mcp__all-quiet__allquiet_create_incident",
      "mcp__all-quiet__allquiet_update_incident",
      "mcp__all-quiet__allquiet_create_on_call_override"
    ]
  }
}

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

Capability tags behind 2 rules
  • mcp__all-quiet__allquiet_get_incident_markdown private-data, untrusted-input
  • mcp__all-quiet__allquiet_list_users 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/all-quiet/verify?hash=4c18907e8386c3170c6900d207efc3cf11071dcb86a1ea66565431b9572cd818" | jq -e '.changed == false'

Pinned hash 4c18907e8386, 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/all-quiet/changes.xml

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

Badge

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

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

All Quiet MCP by usefulapi: questions and answers

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

Is the All Quiet MCP by usefulapi safe?

No scan can promise that. What its definitions show: 11 tools, 5 of which can change, send or delete something, and 2 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 All Quiet MCP by usefulapi delete data?

Yes. 3 tools can delete, cancel or revoke something: allquiet_create_incident, allquiet_update_incident and allquiet_create_on_call_override.

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

11 tools: 3 destructive, 2 write, 6 read. allquiet_create_incident, allquiet_update_incident, allquiet_create_on_call_override, allquiet_who_is_on_call, allquiet_on_call_report, allquiet_list_incidents, allquiet_get_incident, allquiet_get_incident_markdown and 3 more.

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

Its remote endpoint did not answer the last anonymous look.

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

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