Gdpr Compliance Ai Mcp
io.github.CSOAI-ORGPublished by GitHub account CSOAI-ORGv1.1.14Updated Oct 30, 2026
Gdpr Compliance Ai MCP Server by MEOK AI Labs
Overview
Local MCP server for GDPR compliance work: DPIA generation, Article 30 records, Article 22 audits and data subject request workflows.
- What you can do
- Classify processing activities and assess lawful basis for data processing
- Generate DPIA (data protection impact assessment) documents
- Produce and manage Article 30 processing records
- Audit automated decision-making under Article 22
- Handle data subject request workflows
- Check cross-border transfers, data localization and breach detection
- When to use it
- Useful when an assistant should help draft or check GDPR documentation — impact assessments, processing records, lawful-basis reasoning, transfer checks or data subject requests — rather than doing that work by hand.
- Requirements
- Runs locally over stdio, installed from PyPI (pip install gdpr_compliance_ai_mcp) or launched with uvx; Python runtime needed. Optional pay-per-call billing uses the MEOK_PAYG_KEY environment variable, with MEOK_PAYG_RATE_GBP and MEOK_X402_RECEIVER for rate and stablecoin payment settings.
Installation
In SourceWeft
- Open Gdpr Compliance Ai 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
Verification is free and public: signed measurement cards and live verification at https://councilof.ai — measurement, not certification.
Gdpr Compliance Ai MCP
[Council of AI] [PAYG enabled] [GSPC] [License] [PyPI]
GDPR compliance MCP — DPIA automation, Article 30 records, Article 22 automated decision-making a...
GDPR compliance MCP — DPIA automation, Article 30 records, Article 22 automated decision-making audit, data subject request workflow.
🚀 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
- GDPR Chapter V compliance
- Cross-region data guard
- Data localization
- Transfer mechanism validation
- Breach detection
📖 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?
View Pricing → | Contact Sales →
🤝 Part of the MEOK Ecosystem
This server is part of the Council of AI ecosystem — 26 PyPI packages · ~public measurement tools.
📜 License
MIT © CSOAI-ORG
Built with 💜 by Council of AI · UK Companies House 16939677
Configuration
Add to your claude_desktop_config.json (Claude Desktop) or your MCP client config:
Or: pip install gdpr-compliance-ai-mcp then run the gdpr-compliance-ai-mcp command (stdio transport).
Examples
Once configured, ask your assistant, for example:
- "Use
classify_processingto …" - "Use
lawful_basis_assessmentto …" - "Use
dpia_generatorto …"
Source: README.md at commit 55c55f1
Tools
0Version history
1- v1.1.14LatestSep 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