Home / MCP registry index / io.usefulapi/all-quiet
All Quiet MCP by usefulapi
io.usefulapi/all-quiet in the official MCP registry.
Endpoint https://all-quiet.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides.
We read its 11 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
allquiet_list_incidents allquiet_get_incident allquiet_get_incident_markdown allquiet_who_is_on_call allquiet_on_call_report allquiet_list_teams allquiet_list_users allquiet_list_on_call_overrides allquiet_create_incident allquiet_update_incident allquiet_create_on_call_override
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-all-quiet)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.