AI Incident Reporting MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| classify_incidentB | Classify an incident against every regime in scope. Returns the multi-regime decision tree: which clocks start, who to notify, on what form, by when. |
| list_regime_clocksB | List the reporting clocks + authorities for every regime this MCP covers. |
| sign_incident_response_attestationC | Generate a cryptographically signed AI incident-response attestation (Pro+). Captures: which regimes were notified, within which SLAs, what the response score was. Auditors consume the verify_url as evidence of post-incident compliance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct operation: classification, listing clocks, and signing attestations. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern in snake_case, making them predictable and easy to distinguish.
Three tools is slightly lean but appropriate for the narrow domain of AI incident reporting compliance. Each tool serves a clear purpose without redundancy.
The toolset covers the full workflow: classification against regimes, awareness of reporting clocks, and generation of signed attestations for auditors. No obvious gaps.