Metadata-Version: 2.4
Name: agent-incident-relay-mcp
Version: 1.0.1
Summary: Agent Incident Relay MCP — Article 73 5-clock broadcaster. One incident → simultaneous signed reports to EU AI Act Art 73, DORA Art 19, NIS2 Art 23, GDPR Art 33, ISO 42001 cl 10.1. By MEOK AI Labs.
Author-email: Nicholas Templeman <nicholas@meok.ai>
License: MIT
Project-URL: Homepage, https://meok.ai/a2a
Project-URL: Repository, https://github.com/CSOAI-ORG/agent-incident-relay-mcp
Keywords: mcp,compliance,incident-reporting,eu-ai-act,dora,nis2,gdpr,iso-42001,meok
Classifier: Development Status :: 4 - Beta
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3
Classifier: Topic :: Office/Business :: Financial
Requires-Python: >=3.10
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: mcp[cli]>=1.3.0
Dynamic: license-file

# Agent Incident Relay MCP

> ## 🧱 Part of the MEOK A2A Substrate (£999/mo) + Governance Substrate (£499/mo)
> See [meok.ai/a2a](https://meok.ai/a2a).

# Article 73 5-clock broadcaster — one incident, five signed regulatory reports

<!-- mcp-name: io.github.CSOAI-ORG/agent-incident-relay-mcp -->

[![PyPI](https://img.shields.io/pypi/v/agent-incident-relay-mcp)](https://pypi.org/project/agent-incident-relay-mcp/)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE)

## What this does

EU regulated AI systems live under **five concurrent regulatory regimes**. When an incident happens, missing one clock = enforcement action.

This MCP takes ONE incident description, classifies which regimes apply, and starts ALL the clocks simultaneously. It emits per-regime signed payloads ready for submission to each national authority.

| # | Regime | Earliest clock | Authority |
|---|---|---|---|
| 1 | **EU AI Act Article 73** | 15 days to deployer | National AI competent authority + AI Office |
| 2 | **DORA Article 19** | 4 hours initial | National financial supervisor + ESAs |
| 3 | **NIS2 Article 23** | 24 hours early warning | National CSIRT + competent authority |
| 4 | **GDPR Article 33** | 72 hours | National DPA |
| 5 | **ISO/IEC 42001 cl 10.1** | 24h internal | Internal AIMS + external auditor |

## Tools

| Tool | Purpose |
|---|---|
| `classify_incident(description, severity?)` | Which regimes apply? Auto-detect severity. |
| `relay_incident(description, regimes?, severity, entity_id)` | Start all clocks from one detection timestamp |
| `check_clock_status(incident_id)` | How many hours remain on each clock? |
| `generate_authority_payload(incident_id, regime, extra_fields?)` | Regime-formatted submission payload |
| `sign_relay(incident_id)` | HMAC-seal the full 5-regime relay for audit |
| `list_regimes()` | Full regime spec — clocks, authorities, schemas |

## Why this matters

Today GRC teams maintain five separate spreadsheets and miss deadlines because the clocks all start at different events. This MCP gives you one incident_id that drives all five regimes from the same detection timestamp, with cryptographic non-repudiation.

Companion to:
- `ai-incident-reporting-mcp` (classifier-only, no broadcast)
- `dora-nis2-crosswalk-mcp` (regulation-to-regulation map)
- `agent-audit-logger-mcp` (the chain-of-custody log for the submitted payloads)

## Sister MCPs

Part of the MEOK **A2A** + **Governance** packs:

- `bft-progress-council-mcp` — anti-loop for the response team
- `agent-audit-logger-mcp` — HMAC-chained log of every submission
- `agent-policy-enforcement-mcp` — gate on incident-response approval
- `eu-ai-act-compliance-mcp` — Article 73 text + thresholds

Full catalogue: [meok.ai/anthropic-registry](https://meok.ai/anthropic-registry)

## Pricing

| Option | Price |
|---|---|
| Self-host MIT | £0 |
| Universal PAYG | £29/mo + £0.0002/call |
| Governance Substrate | £499/mo |
| A2A Substrate | £999/mo |
| Defence | £4,990/mo |

Buy: https://meok.ai/a2a

## Licence

MIT. By [MEOK AI Labs](https://meok.ai) (CSOAI LTD, UK Companies House 16939677).
