mcpbeat Sign in

Agent Incident Classification Notification MCP Server

answering

Agent Incident Classification Notification is answering right now. Last checked 4 min ago. It exposes 3 tools.

Signed agent-incident classification vs PP-26-4396, with third-party notification receipts.

Uptime history 46 hours of history
46 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
335 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Agent Incident Classification Notification every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add agent-incident-classification-notification --transport http https://textforagents.com/products/agent-incident-classification-notification/mcp
Settings → Connectors → Add custom connector, then paste this address
https://textforagents.com/products/agent-incident-classification-notification/mcp
~/.codex/config.toml
[mcp_servers.agent-incident-classification-notification]
url = "https://textforagents.com/products/agent-incident-classification-notification/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agent-incident-classification-notification": {
      "url": "https://textforagents.com/products/agent-incident-classification-notification/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "agent-incident-classification-notification": {
      "type": "http",
      "url": "https://textforagents.com/products/agent-incident-classification-notification/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

classify
classify_incident
Classify an incident record (first verdict per operator free, then $0.49 via x402 on the HTTP surface)
flags
get_flags
Definition-diff flags for your verdicts
registry
get_registry
Public aggregate registry (counts and categories only)

Endpoints

URLTransportStateLatencyChecked
https://textforagents.com/products/agent-incident-classification-notification/mcp streamable-http answering 317 ms 4 min ago

Alternatives to Agent Incident Classification Notification

same job, measured the same way
AI Incident Reporting MCP
by csoai-org

AI Incident Reporting Compliance MCP. Unified classification + reporting-clock tracker across EU...

205 installs/wk local only
Emulo
by ohad6k

Mine your AI coding session logs into a you.md profile with dated receipts, for an agent to read.

237 installs/wk local only
Pagerduty
by mcparmory

Manage incidents, on-call schedules, escalation policies, and alert notifications

233 installs/wk local only
RealUptime
by realuptime

RealUptime monitors, incidents, status pages, Errors issues, and free third-party outage checks.

7 tools answering
three.ws Provenance
by nirholas

Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.

26 installs/wk local only
Asrs Reports
by pipeworx-io

NASA Aviation Safety Reporting System (ASRS) — de-identified aviation safety incident narratives.

44 tools answering
Threatcluster
by jam0k

Live threat intel for agents: incidents, actors, CVEs with KEV/EPSS, ransomware leak-site victims.

49 installs/wk answering
Agent Incident Reporter MCP
by csoai-org

Signed, hash-chained, tamper-evident AI incident records. EU AI Act Article 73 serious-incident repo

171 installs/wk local only

Agent Incident Classification Notification — questions

Answers built from our own checks of this server.

What can Agent Incident Classification Notification do?
It exposes 3 tools, read directly from the server on our last check. Among them: classify_incident, get_flags, get_registry. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Agent Incident Classification Notification working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 335 ms. The bar chart above shows every period we have measured.
How do I connect Agent Incident Classification Notification?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Agent Incident Classification Notification need an API key?
No. Agent Incident Classification Notification completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agent Incident Classification Notification?
It answers our handshake in 335 ms on average, which is faster than 48% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.