Skip to main content
Glama
AI Incident Reporting MCP

AI Incident Reporting MCP

MCP Scorecard: 90/100

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 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

# Install via pip
pip install ai_incident_reporting_mcp

# Or install via Smithery
npx -y @smithery/cli@latest install ai-incident-reporting-mcp --client claude

Related MCP server: DORA Compliance MCP

✨ 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 →

How MEOK charges

MEOK has no subscriptions and no tiers. You pay per job, and only when the agreed artifact has been delivered to you. There is no public price list. See https://meok.ai/pricing.

This repository's source is MIT-licensed and free to self-host.

🤝 Part of the MEOK Ecosystem

This server is part of the MEOK AI Labs ecosystem — 300+ MCP servers for sovereign AI governance.

Domain

Purpose

councilof.ai

EU AI Act compliance marketplace

safetyof.ai

AI safety & monitoring

meok.ai

Sovereign AI platform

cobolbridge.ai

Legacy modernization

📜 License

MIT © CSOAI-ORG


Full catalogue + Anthropic Registry verify links: https://meok.ai

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:

Option

Price

Best for

Self-host (this MCP)

£0 — MIT

Devs

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.

Configuration

Add to your claude_desktop_config.json (Claude Desktop) or your MCP client config:

{
  "mcpServers": {
    "ai-incident-reporting-mcp": {
      "command": "uvx",
      "args": ["ai-incident-reporting-mcp"]
    }
  }
}

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

  • "Use list_regime_clocks to …"

  • "Use sign_incident_response_attestation to …"

See also

MEOK compliance MCP fleet: meok-eu-ai-act-art-26-fria-mcp, nis2-compliance-mcp

Available Tools

3 tools
classify_incidentB

Classify an incident against every regime in scope. Returns the multi-regime decision tree: which clocks start, who to notify, on what form, by when.

Inputs: entity_type (required), incident_description (required), affected_people_count, duration_hours, +9 more. Returns: result

list_regime_clocksB

List the reporting clocks + authorities for every regime this MCP covers.

Inputs: api_key. Returns: result

sign_incident_response_attestationC

Generate a cryptographically signed AI incident-response attestation (Pro+).

Captures: which regimes were notified, within which SLAs, what the response score was. Auditors consume the verify_url as evidence of post-incident compliance.

Inputs: entity_name (required), incident_id (required), response_score (required), regimes_notified_csv, +3 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct operation: classification, listing clocks, and signing attestations. No overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case, making them predictable and easy to distinguish.

    Tool Count4/5

    Three tools is slightly lean but appropriate for the narrow domain of AI incident reporting compliance. Each tool serves a clear purpose without redundancy.

    Completeness5/5

    The toolset covers the full workflow: classification against regimes, awareness of reporting clocks, and generation of signed attestations for auditors. No obvious gaps.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers