
Ai Incident Reporting Mcp
io.github.CSOAI-ORGPublished by GitHub account CSOAI-ORGv1.1.9Updated Oct 30, 2026
AI Incident Reporting Compliance MCP. Unified classification + reporting-clock tracker across EU...
Overview
Local MCP server that helps an assistant classify AI incidents across EU AI Act, DORA, NIS2 and GDPR regimes and track reporting deadlines.
- What you can do
- Classify AI incidents against multiple regulatory regimes (EU AI Act Article 73, DORA, NIS2, GDPR breach)
- Track reporting clocks and list the deadlines that apply per regime
- Run escalation workflows and keep an audit trail of incident handling
- Sign incident-response attestations and prepare regulatory submissions
- When to use it
- Useful for teams that must report AI incidents to regulators and want an assistant to classify an incident, identify which reporting clocks apply and keep a record of the response. Mostly relevant to EU-regulated AI deployments.
- Requirements
- Runs locally over stdio as a Python package (ai-incident-reporting-mcp), installed with pip or launched via uvx. No authentication, environment variables or headers are declared. The README also mentions an optional Smithery install route.
Installation
In SourceWeft
- Open Ai Incident Reporting Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Ai Incident Reporting MCP
mcp-name: io.github.CSOAI-ORG/ai-incident-reporting-mcp
AI Incident Reporting Compliance MCP
⚖️ Built by MEOK AI Labs / CSOAI. Need this applied to your system fast? Book a 30-min Founder Office Hour (£29) → https://meok.ai/work · Full governance platform → https://meok.ai
[MEOK AI Labs] [EU AI Act] [License] [PyPI]
Multi-regime AI incident classification + reporting MCP (EU AI Act Art 73, DORA, NIS2, GDPR breach)
Multi-regime AI incident classification + reporting MCP (EU AI Act Art 73, DORA, NIS2, GDPR breach). MIT
🚀 Quick Start
✨ Features
- Article 73 incident reporting
- 5-clock broadcast
- Escalation workflows
- Audit trail
- Regulatory submission
📖 Documentation
🛡️ Compliance
This MCP server is built with EU AI Act compliance built-in:
- ✅ Article 9 — Risk Management System
- ✅ Article 13 — Transparency & Instructions for Use
- ✅ Article 15 — Bias Detection & Testing
- ✅ Article 26 — FRIA Support (where applicable)
- ✅ Article 50 — AI Content Watermarking (where applicable)
Need help getting compliant? Book a free 15-min diagnostic →
🏢 Enterprise
Need custom development, SLA guarantees, or white-label deployment?
- Pro: $99/mo — Full MCP suite + EU AI Act tracking
- Enterprise: $499/mo — Custom dev + SLA + Dedicated support
View Pricing → | Contact Sales →
🤝 Part of the MEOK Ecosystem
This server is part of the MEOK AI Labs ecosystem — 300+ MCP servers for sovereign AI governance.
📜 License
MIT © CSOAI-ORG
Built with 💜 by MEOK AI Labs · UK Companies House 16939677
- **EU AI Act** → `uvx eu-ai-act-compliance-mcp` · [PyPI](https://pypi.org/project/eu-ai-act-compliance-mcp/) · [GitHub](https://github.com/CSOAI-ORG/eu-ai-act-compliance-mcp) - **DORA** → `uvx dora-compliance-mcp` · [PyPI](https://pypi.org/project/dora-compliance-mcp/) · [GitHub](https://github.com/CSOAI-ORG/dora-compliance-mcp) - **NIS2** → `uvx nis2-compliance-mcp` · [PyPI](https://pypi.org/project/nis2-compliance-mcp/) · [GitHub](https://github.com/CSOAI-ORG/nis2-compliance-mcp) - **Cyber Resilience Act** → `uvx cra-compliance-mcp` · [PyPI](https://pypi.org/project/cra-compliance-mcp/) · [GitHub](https://github.com/CSOAI-ORG/cra-compliance-mcp) - **AI Bill of Materials** → `uvx ai-bom-mcp` · [PyPI](https://pypi.org/project/ai-bom-mcp/) · [GitHub](https://github.com/CSOAI-ORG/ai-bom-mcp) - **DORA × NIS2 Crosswalk** → `uvx dora-nis2-crosswalk-mcp` · [PyPI](https://pypi.org/project/dora-nis2-crosswalk-mcp/) · [GitHub](https://github.com/CSOAI-ORG/dora-nis2-crosswalk-mcp)Full catalogue + Anthropic Registry verify links: meok.ai/anthropic-registry
Protocol coverage + Universal PAYG
This MCP is part of MEOK's 47-MCP fleet that bridges every active agent-interop protocol and 30+ regulatory frameworks. See the full coverage matrix at meok.ai/protocols.
Agent interop protocols supported (8 live):
- ✅ MCP (Anthropic) — native
- ✅ A2A (Google + Linux Foundation, absorbed IBM ACP Sept 2025)
- ✅ IBM ACP — covered via A2A merge
- ◐ Stripe ACP (Agentic Commerce Protocol) — Q3 bridge via agent-commerce-protocol-mcp
- ◐ AP2 (Google Agent Payments) — partial via agent-commerce-payments-mcp
- ◐ x402 (Coinbase HTTP 402) — partial via api.meok.ai gateway
- → OASF / AGNTCY (Cisco Outshift + Linux Foundation) — Q3 bridge
- 👁 ANP (Cisco Agent Network) — watch-list
Pricing options:
Each tier above the free self-host adds HMAC-signed attestations verifiable at
verify.meok.ai. Linux Foundation governance on the A2A spine means EU regulated
buyers can deploy without vendor-lock-in objections.
💸 Try MEOK in 30 seconds — instant buy ladder
Refundable. UK Stripe — VAT-clean. Builds on the 81-MCP MEOK fleet. Verify any signed report at https://meok.ai/verify.
Configuration
Add to your claude_desktop_config.json (Claude Desktop) or your MCP client config:
Or: pip install ai-incident-reporting-mcp then run the ai-incident-reporting-mcp command (stdio transport).
Examples
Once configured, ask your assistant, for example:
- "Use
classify_incidentto …" - "Use
list_regime_clocksto …" - "Use
sign_incident_response_attestationto …"
See also
MEOK compliance MCP fleet:
meok-eu-ai-act-art-26-fria-mcp, nis2-compliance-mcp
Source: README.md at commit 60694b7
Tools
0Version history
1- v1.1.9LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts