Signed agent-incident classification vs PP-26-4396, with third-party notification receipts.
Scored across 3 tools
classify_incident is a clear write action, while get_flags and get_registry are both reads but target different resources (private per-operator flags vs. public aggregates). The two 'get' tools could momentarily be confused since both return derived metadata, but the descriptions draw a workable line between them.
All three tools follow a clean verb_noun pattern (classify_incident, get_flags, get_registry) with consistent snake_case and verbs that match their action type.
Three tools is at the thin edge for a service whose name implies classification plus notification. Each tool is justified, but the surface feels under-built for the stated scope.
The server name promises notification, yet there is no notification or subscribe tool at all. There is also no way to read back an individual incident or verdict, list incidents, or correct a misclassification, leaving agents with dead ends after classifying.
Classify an incident record (first verdict per operator free, then $0.49 via x402 on the HTTP surface)
Inputs: record (required).
Public aggregate registry (counts and categories only)
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Agent Incident Relay MCP — Article 73 5-clock broadcaster. One incident → simultaneous signed
Signed verdict receipts recovering a fleet's gatekeeper category, plus appeal packets.
Signed receipts + horizon statements proving whether an event-triggered agent actually woke.
Agent completion verification with defects, corrections, and evidence receipts.
Add one secure layer between your agents and this server.