# GDPR and ToS Compliance MCP – scan your codebase for GDPR violations

> Source: <https://github.com/enrique-martin-182/gdpr-compliance-mcp>
> Published: 2026-11-18 14:52:45+00:00

**Key takeaway:** The gdpr-compliance-mcp server plugs into Claude Code via an npx command with a GDPR_MCP_KEY environment variable and returns findings with severity, file location, GDPR article and fix, though v0.1 PII detection and v0.2 ToS scanning for 25 APIs are not due until Q1 2025.

Scan your codebase for GDPR violations and API ToS risks — directly inside Claude Code.

You're building with AI. You're calling third-party APIs. You're storing user data.

And somewhere in your codebase, right now, there's probably a GDPR violation you don't know about.

- Personal data passed in a URL parameter (logged by every server, forever)
- API keys stored in a way that violates the provider's ToS
- User emails sent to a third-party service without a DPA
- Consent flow that doesn't meet GDPR Article 7 requirements
- Logs that capture PII you legally can't retain

Finding these problems costs €500+/hour with a lawyer. Missing them costs €20M or 4% of annual turnover.

**There is no MCP server that solves this. Until now.**

Connect this MCP to Claude Code. Then ask:

```
Scan this project for GDPR compliance issues
Does this API call violate Stripe's Terms of Service?
What personal data are we collecting and where is it stored?
```

The MCP analyzes your code and returns structured findings:

```
{
  "severity": "HIGH",
  "issue": "PII in URL parameters",
  "location": "src/api/users.ts:47",
  "gdpr_article": "Article 5(1)(f) - Integrity and confidentiality",
  "fix": "Move email to request body. Never pass PII in GET parameters.",
  "legal_exposure": "Logged by CDN, load balancers, and analytics. Counts as unauthorized disclosure."
}
```

**GDPR Scanner**

- Personal data flow mapping (where does PII go?)
- Consent mechanism audit (does your consent flow meet Article 7?)
- Data retention checker (are you storing data longer than declared?)
- Cross-border transfer detection (sending EU data outside EU?)
- DPA requirements (which third-party services need a Data Processing Agreement?)

**ToS Compliance**

- API usage audit against provider ToS (OpenAI, Stripe, Twilio, SendGrid, and 20+ more)
- Automated flagging when code patterns violate rate limits, usage restrictions, or data policies
- Competitive intelligence clauses detection

**Privacy Policy Gap Analysis**

- Compare what your code *actually* does vs. what your privacy policy*says* you do
- Auto-generate missing sections

| Plan | Price | For | 
|---|---|---|
| **Free** | €0 | 3 scans/month, basic GDPR checks | 
| **Solo** | €29/month | Unlimited scans, full ruleset, weekly digest | 
| **Teams** | €79/month | Everything + team reports, Slack alerts, priority support | 

**Early access**: First 50 users get Solo plan at €19/month, locked forever.

```
{
  "mcpServers": {
    "gdpr-compliance": {
      "command": "npx",
      "args": ["-y", "gdpr-compliance-mcp"],
      "env": {
        "GDPR_MCP_KEY": "your-api-key"
      }
    }
  }
}
```

GDPR enforcement is accelerating. In 2023: €1.6B in fines. In 2024: €1.2B in H1 alone.

The tools that exist today:

- **Free GDPR checklists** : Static PDFs. Can't read your code.
- **Termly / iubenda** (€10-100/month): Generate privacy policies. Don't scan code.
- **Legal consultants** (€200-500/hour): Deep expertise. Can't review every commit.
- **Enterprise platforms** (€4,200+/year): Overkill for indie devs and small teams.

There is nothing in the middle. This is the middle.

**⭐ Star this repo** to follow progress.

**Comment below** if you'd use this. Specifically helpful to know:

- What stack you're on (Node, Python, Go...)
- Biggest compliance pain right now
- Whether you'd pay for this

Building in public. First 50 signups get early access + locked-in pricing.

📧 [Join waitlist → open an issue](https://github.com/enrique-martin-182/gdpr-compliance-mcp/issues/new?title=Waitlist+signup&body=Stack%3A+%0AGDPR+pain+point%3A+%0AWould+pay%3A+yes%2Fno)

- v0.1 — PII detection in code (Q1 2025)
- v0.2 — ToS scanner for top 25 APIs (Q1 2025)
- v0.3 — Privacy policy gap analysis (Q2 2025)
- v0.4 — CI/CD integration (GitHub Actions) (Q2 2025)
- v1.0 — Full GDPR article coverage (Q3 2025)

Open an issue. Or email directly. Response within 24h.

*Built for developers who ship fast and need compliance that keeps up.*
