Skip to main content

Signed, hash-chained, tamper-evident AI incident records (MCP server). EU AI Act Art 73 ready. By MEOK AI Labs / CSOAI.

Project description

mcp-name: io.github.CSOAI-ORG/agent-incident-reporter-mcp

Agent Incident Reporter MCP — the AI incident record a regulator can trust

[CSOAI][![MCP Scorecard](https://img.shields.io/badge/MCP Scorecard: 74/100-7c3aed)]![MCP Scorecard](https://img.shields.io/badge/MCP Scorecard: 74/100-7c3aed) (https://proofof.ai/scoreboard) (https://csoai.org) License

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 tools to …"

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

agent_incident_reporter_mcp-1.0.3.tar.gz (10.6 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

agent_incident_reporter_mcp-1.0.3-py3-none-any.whl (2.8 kB view details)

Uploaded Python 3

File details

Details for the file agent_incident_reporter_mcp-1.0.3.tar.gz.

File metadata

File hashes

Hashes for agent_incident_reporter_mcp-1.0.3.tar.gz
Algorithm Hash digest
SHA256 d7a17411dee47c10e379348251c5d72be8b15da605e0a866f4c84f0f01ef90c9
MD5 8cfb50b9cfebf722cfb075878da373a3
BLAKE2b-256 a189816fb1afbecc7e87878e78a087394afeb6fa0cd91f0c3df98e8833e8f550

See more details on using hashes here.

File details

Details for the file agent_incident_reporter_mcp-1.0.3-py3-none-any.whl.

File metadata

File hashes

Hashes for agent_incident_reporter_mcp-1.0.3-py3-none-any.whl
Algorithm Hash digest
SHA256 5ee2ac3b37817b31947612a5bf68ba592de123cfb183ccd2914a951859f05ae5
MD5 b1e1e2caffce6943dc36138b939a4c88
BLAKE2b-256 bb0d38f1b89be89ce4b2dfd17c945e8de5ae3d3ed44de64fe5e190538cf60965

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page