agent-incident-classification-notification
Signed agent-incident classification vs PP-26-4396, with third-party notification receipts.
Should I use this
Quality & Safety
B
Findings (1)
- LOWTool 'get_flags' description lacks action verbin get_flags
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
~130Tokens (tool definitions)
~147 BTypical response size
Minimal attention impact (0.10% of 128k context)
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"agent-incident-classification-notification": {
"url": "https://textforagents.com/products/agent-incident-classification-notification/mcp"
}
}
}Remote endpoints
https://textforagents.com/products/agent-incident-classification-notification/mcpstreamable-httpWhat it can do
Tool inventory
Tools (3)
🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
⚪classify_incident(record)
Classify an incident record (first verdict per operator free, then $0.49 via x402 on the HTTP surface)
Input Schema
{
"type": "object",
"properties": {
"record": {
"type": "object"
}
},
"required": [
"record"
]
}🟢get_registry
Public aggregate registry (counts and categories only)
Input Schema
{
"type": "object",
"properties": {}
}🟢get_flags
Definition-diff flags for your verdicts
Input Schema
{
"type": "object",
"properties": {}
}Community
Evidence
Recent observations
verifiedversion not recorded3 tools