AI Incident Reporting Compliance MCP. Unified classification + reporting-clock tracker across EU AI Act Article 73, DORA Article 19, NIS2 Article 23, GDPR Article 33, ISO/IEC 42001 clause 9, and UK AISI voluntary frontier-model reporting. One incident → all regime clocks in parallel. HMAC-signed post-incident attestation. By MEOK AI Labs.
Project description
AI Incident Reporting Compliance MCP
Buy Starter — £29/mo
Signed attestations + unlimited audits + email support. 👉 Subscribe at meok.ai — instant HMAC signing key + Stripe-managed billing.
Free tier remains MIT-licensed and zero-config. Upgrade only when you need signed compliance artefacts for audit.
One AI incident → many mandatory notifications. Classifies once, emits every regime's clock + authority + form in parallel.
By MEOK AI Labs.
Regimes covered
- EU AI Act Article 73 — serious-incident reporting (high-risk AI + GPAI with systemic risk). 15-day initial notification to market-surveillance authority.
- DORA Article 19 — major ICT incident reporting (financial entities + CTPPs). 4h / 72h / 1 month clocks.
- NIS2 Article 23 — significant incident (essential/important entities). 24h early warning / 72h notification / 1 month final.
- GDPR Article 33 — personal-data breach (controllers). 72h.
- ISO/IEC 42001 clause 9 — AIMS monitoring + internal incident for AI management systems.
- UK AI Safety Institute (AISI) — voluntary frontier-model incident reporting.
Why this MCP
A single incident — say, a bias-driven lending decision that materially harms a protected group — can simultaneously trigger:
- EU AI Act Art 73 (high-risk AI fundamental-rights incident — 15 days)
- DORA Art 19 (if financial entity, €100k impact — 4 hours)
- NIS2 Art 23 (if essential entity, significant disruption — 24 hours)
- GDPR Art 33 (personal data involved — 72 hours)
If you don't know that, you miss the tightest SLA. This MCP classifies the incident against every regime in scope for your entity and tells you the master deadline.
Tools
classify_incident— multi-regime decision treelist_regime_clocks— all regime clocks + authoritiessign_incident_response_attestation— Pro/Enterprise: signed post-incident evidence
Install
pip install ai-incident-reporting-mcp
Tiers
- Free — 10 classifications/day
- Pro £199/mo — unlimited + signed attestations + notification templates
- Enterprise £1,499/mo — multi-entity + Trust Center webhook pushes
- £5,000 assessment — 48h incident-response audit + playbook hardening
Full Compliance Platform
Need the complete multi-regime stack? councilof.ai — EU AI Act, DORA, NIS2, CRA, CSRD compliance from £29/mo. 100x cheaper than traditional consulting.
Related MEOK MCPs
eu-ai-act-compliance-mcpdora-compliance-mcpnis2-compliance-mcpdora-nis2-crosswalk-mcpmeok-attestation-verify
If this tool helps your compliance workflow, please star this repo — it helps other teams find it.
License
MIT — MEOK AI Labs, 2026.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "Is this MCP server free to use?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. The free tier gives you 10 calls per day with no API key required. Pro tier is £79/mo for unlimited calls plus cryptographically signed attestations your auditor can verify independently." } }, { "@type": "Question", "name": "How does the signed attestation work?", "acceptedAnswer": { "@type": "Answer", "text": "Every Pro tier audit produces a HMAC-SHA256 signed certificate with a unique ID and a public verify URL. Your auditor pastes the cert into https://meok-attestation-api.vercel.app/verify and gets an independent valid/invalid response. No contact with MEOK required." } }, { "@type": "Question", "name": "Which MCP clients does this work with?", "acceptedAnswer": { "@type": "Answer", "text": "All standard MCP clients: Claude Desktop, Claude Code, Cursor, VS Code with MCP extension, Windsurf, Cline, and any custom MCP-compatible agent. Install via npx meok-setup or pip install for the underlying Python package." } }, { "@type": "Question", "name": "Can I install all MEOK governance MCPs at once?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Run npx meok-setup --pack governance to install all 10 governance MCPs and write the configs for Claude Desktop, Cursor, or Windsurf in one command." } }, { "@type": "Question", "name": "Is the regulation text authoritative?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. MEOK syncs daily from the EUR-Lex Cellar SPARQL endpoint, the canonical EU regulation publication system. The text is verbatim with no LLM summarization. Every quote is auditor-defensible and includes the exact article number plus relevance score." } } ] } </script>Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file ai_incident_reporting_mcp-1.0.3.tar.gz.
File metadata
- Download URL: ai_incident_reporting_mcp-1.0.3.tar.gz
- Upload date:
- Size: 25.7 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.11.15
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
36ae714b0b70091ea1855a81fb6160689a19a3a765d7685adfd6dad174ff224d
|
|
| MD5 |
1c0016de55c0173b3003ebe702860956
|
|
| BLAKE2b-256 |
07d0e49d9b28a00c4bf97dd51b275e4666804c12005d94bfdb3069d11efc193c
|
File details
Details for the file ai_incident_reporting_mcp-1.0.3-py3-none-any.whl.
File metadata
- Download URL: ai_incident_reporting_mcp-1.0.3-py3-none-any.whl
- Upload date:
- Size: 11.2 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.11.15
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
c50b7b6185deb2d1a6f92b67995f39f184480c1a1ac95ed73edac04fb0481e92
|
|
| MD5 |
041afcef3369ebf33dc7de53f1116fa1
|
|
| BLAKE2b-256 |
34d996791314442e7d96a2eb5a7f84a77782d026363052fdc7fdd99e4b8af2e4
|