io.github.CSOAI-ORG/ai-incident-reporting-mcp

Name: io.github.CSOAI-ORG/ai-incident-reporting-mcp
Rating: 60 (1 reviews)
Author: io.github.CSOAI-ORG

MCPcommunity

v1.1.7io.github.CSOAI-ORGUnknownUpdated 20d agoGitHub

AI Incident Reporting Compliance MCP. Unified classification + reporting-clock tracker across EU...

mcp-name: io.github.CSOAI-ORG/ai-incident-reporting-mcp ⚖️ Built by MEOK AI Labs / CSOAI. Need this applied to your system fast? Book a 30-min Founder Office Hour (£29) → · Full governance platform → 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…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

20d agoLast update

Package

Authorio.github.CSOAI-ORG

LicenseUnknown

Version1.1.7

Sourcemcp-registry

GitHubCSOAI-ORG/ai-incident-reporting-mcp

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

DependenciesNot audited

Tool surface—

Security scan✓ Cleanv1.1.8 · 19d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp