Skip to main content

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

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 tree
  • list_regime_clocks — all regime clocks + authorities
  • sign_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

Related MEOK MCPs

License

MIT — MEOK AI Labs, 2026.

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

ai_incident_reporting_mcp-1.0.0.tar.gz (8.3 kB view details)

Uploaded Source

Built Distribution

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

ai_incident_reporting_mcp-1.0.0-py3-none-any.whl (9.9 kB view details)

Uploaded Python 3

File details

Details for the file ai_incident_reporting_mcp-1.0.0.tar.gz.

File metadata

File hashes

Hashes for ai_incident_reporting_mcp-1.0.0.tar.gz
Algorithm Hash digest
SHA256 05237781daa47ce79c540b81799b7b03b9b82316b3773410794bd99ae99234d0
MD5 3b504e6ef4a1bfd77f32c676942bd224
BLAKE2b-256 49d2ba10f81af2f0c0b92e3b9bc8d231b38757596748ae1251349287c4014da7

See more details on using hashes here.

File details

Details for the file ai_incident_reporting_mcp-1.0.0-py3-none-any.whl.

File metadata

File hashes

Hashes for ai_incident_reporting_mcp-1.0.0-py3-none-any.whl
Algorithm Hash digest
SHA256 8a18acd54a871e3cac8cb8776fcce89ced9c319670f36f570ae84e11e8ab23e7
MD5 1a66cab2a3f41a6149a101018a199535
BLAKE2b-256 6ac20437cff02b27fb281da1dd27efe967109340a054aa69dbe1239c7e76d672

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