mcp-name: io.github.CSOAI-ORG/agent-incident-reporter-mcp
Agent Incident Reporter MCP — the AI incident record a regulator can trust
[
Your agent failed in production. The evidence is scattered stdout logs anyone can edit. When the EU AI Act Article 73 serious-incident report is due, "trust us" is not an answer. This MCP records every incident as a hash-chained, Ed25519-signed, tamper-evident record — editing any past record breaks every later one, visibly.
🚀 Quick start
pip install agent-incident-reporter-mcp
# Claude/any MCP client → add stdio server: python -m agent_incident_reporter_mcp
Tools
| Tool | What it does |
|---|---|
report_incident |
Structured record (severity · system · users affected · corrective action), chained + signed |
list_incidents |
Filter by severity / system / time |
verify_chain |
Re-validate the whole chain + signatures — offline, no backend |
export_audit_pack |
Regulator-ready JSON bundle (Art 73 serious incidents flagged) |
Why now
EU AI Act Article 73 requires providers of high-risk systems to report serious incidents. Article 50 transparency hits new generative systems on 2 August 2026. The market has runtime guardrails and assessment PDFs — nobody offers verifiable incident evidence. This does.
Pricing (canonical CSOAI ladder)
Free: unlimited local records (unsigned-dev). Pro £199/mo — Ed25519 signing + public verify URLs + the full governance suite (subscribe). Enterprise £1,499/mo · 48h bespoke assessment £4,950.
Part of the CSOAI fabric
290+ servers in the official MCP Registry (verified 2026-06-10) · csoai.org/fabric · CSOAI certifies; MEOK AI Labs builds. Records prove identity & integrity, not legal accuracy. MIT © CSOAI LTD (UK 16939677) · contact: nicholas@csoai.org
Configuration
Add to your claude_desktop_config.json (Claude Desktop) or your MCP client config:
{
"mcpServers": {
"agent-incident-reporter-mcp": {
"command": "uvx",
"args": ["agent-incident-reporter-mcp"]
}
}
}
Or: pip install agent-incident-reporter-mcp then run the agent-incident-reporter-mcp command (stdio transport).
Examples
Once configured, ask your assistant, for example:
- "Use
the available toolsto …"
1 maintainer
Metadata
1 maintainer
Release files for agent-incident-reporter-mcp 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| agent_incident_reporter_mcp-1.0.3.tar.gz | 10.6 kB | Without provenance | Details for agent_incident_reporter_mcp-1.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agent_incident_reporter_mcp-1.0.3-py3-none-any.whl | Python 3 | none | any | Details for agent_incident_reporter_mcp-1.0.3-py3-none-any.whl |
Total release size: 13.5 kB
Release files / agent_incident_reporter_mcp-1.0.3.tar.gz
| Download URL | agent_incident_reporter_mcp-1.0.3.tar.gz |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d7a17411dee47c10e379348251c5d72be8b15da605e0a866f4c84f0f01ef90c9
|
|
BLAKE2b-256 checksum How to use checksums |
a189816fb1afbecc7e87878e78a087394afeb6fa0cd91f0c3df98e8833e8f550
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / agent_incident_reporter_mcp-1.0.3-py3-none-any.whl
| Download URL | agent_incident_reporter_mcp-1.0.3-py3-none-any.whl |
|---|---|
| Size | 2.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5ee2ac3b37817b31947612a5bf68ba592de123cfb183ccd2914a951859f05ae5
|
|
BLAKE2b-256 checksum How to use checksums |
bb0d38f1b89be89ce4b2dfd17c945e8de5ae3d3ed44de64fe5e190538cf60965
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for agent-incident-reporter-mcp 1.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
