Nis2 Compliance Mcp
io.github.CSOAI-ORGPublished by GitHub account CSOAI-ORGv1.3.11Updated Nov 5, 2026
NIS2 Directive (EU 2022/2555) compliance for AI agents. 10 Article 21 risk-management measures a...
Overview
Local MCP server that helps an assistant work through NIS2 Directive (EU 2022/2555) Article 21 and 23 compliance tasks such as entity classification and…
- What you can do
- Classify an entity against NIS2 scope
- List and audit the 10 Article 21 risk-management measures
- Support Article 23 incident-reporting work
- Return results that can be turned into signed attestations on a paid tier
- When to use it
- Useful when you need to check whether an organisation falls under NIS2, review its Article 21 measures, or prepare incident-reporting material with an assistant's help. Mostly relevant to EU compliance and audit preparation work.
- Requirements
- Runs locally over stdio, installed from PyPI (pip install nis2-compliance-mcp) or launched with uvx; Python runtime required. No authentication, environment variables or headers are declared. The README mentions an optional MEOK_PAYG_KEY for pay-per-call billing and a MEOK_X402_RECEIVER setting for stablecoin payment.
Installation
In SourceWeft
- Open Nis2 Compliance Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
🔏 Free tier: 50 calls/day. Need audit-ready proof?
Pro (£199/mo) turns every result into an HMAC-signed attestation with a public verify URL your auditor validates without an account — EU AI Act Art 11/12 ready. → Start: https://proofof.ai ·
pip install meok-attestation-verifyto verify any cert.
Nis2 Compliance MCP
[MEOK AI Labs] [PAYG enabled] [GSPC] [License] [PyPI]
NIS2 (Directive EU 2022/2555) Article 21+23 compliance MCP
NIS2 (Directive EU 2022/2555) Article 21+23 compliance MCP. Entity classification, 10 measures audit, incident reporting. MIT
🚀 Quick Start
⚡ Pay-per-call (PAYG) — no subscription
This MCP supports universal pay-per-call billing across the MEOK compliance fleet:
- No subscription — top up once, deduct per call.
- £0.05/call default (configurable via
MEOK_PAYG_RATE_GBP). - USDC on Base L2 accepted — set
MEOK_X402_RECEIVERand pay via stablecoin. - Backward-compatible — when
MEOK_PAYG_KEYis unset, behaviour is unchanged.
Get a token: councilof.ai/payg (£10 / £50 / £200 top-up tiers).
✨ Features
- MCP protocol compliant
- Easy installation
- Well-documented API
- Production-ready
- Active maintenance
📖 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 →
🏢 Enterprise
Need custom development, SLA guarantees, or white-label deployment?
- Pro: £79/mo — Full MCP suite + EU AI Act tracking
- Enterprise: £499/mo — Custom dev + SLA + Dedicated support
View Pricing → | Contact Sales →
🤝 Part of the MEOK Ecosystem
This server is part of the MEOK AI Labs ecosystem — 26 PyPI packages · ~16,300 monthly installs.
📜 License
MIT © CSOAI-ORG
Built with 💜 by MEOK AI Labs · UK Companies House 16939677
Configuration
Add to your claude_desktop_config.json (Claude Desktop) or your MCP client config:
Or: pip install nis2-compliance-mcp then run the nis2-compliance-mcp command (stdio transport).
Examples
Once configured, ask your assistant, for example:
- "Use
classify_entityto …" - "Use
list_article_21_measuresto …" - "Use
audit_article_21to …"
See also
MEOK compliance MCP fleet:
ai-incident-reporting-mcp, meok-eu-ai-act-art-26-fria-mcp
Source: README.md at commit bd5c491
Tools
0Version history
1- v1.3.11LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts