Connects Claude, Cursor, ChatGPT and any MCP-compatible client directly to German data-protection and digital law — plus a live website compliance scanner. ## Free, no API key - **search-law** — full-text search across **26 German/EU statutes** with ~990 articles and paragraphs. Accepts paragraph numbers (`§356a`, `§312k`, `Art. 42`) or free-text keywords. - **get-article** — the exact German text of any article or paragraph, with metadata. - **list-laws** — every supported statute with its article count. Covered: DSGVO, KI-VO (AI Act), BDSG, TDDDG, DDG, BFSG, UWG, BGB, PAngV, VSBG, UrhG, VerpackDG, ElektroG, JuSchG, GewO, MaBV, GEG, BRAO, FinVermV and more. ## With an API key (free tier: 3 scans/month) - **check-compliance** — Playwright-driven scan of any URL against **33 compliance modules**. - **get-scan-status** / **get-scan-result** — score 0–100, financial risk in EUR, each violation with its legal basis (DSGVO Art. X, TDDDG §Y, BGB §356a) and concrete fix steps. ## Twelve modules no other EU scanner offers today - **§356a BGB Widerrufsbutton** — the e-commerce withdrawal button, in force since 19.06.2026. - **Schrems II hosting-location verification** — geographic provenance of every third-party connection. - **KI-VO Art. 50 AI-transparency** — surfaces undisclosed AI use on the scanned site. - **Triple-Trust evidence chain** — HMAC-signed HAR captures plus an append-only transparency log, so a result stays verifiable years later. Plus 8 industry-specific Pro modules: lawyer, real-estate broker, physician, financial intermediary, gastronomy, cosmetics studio, construction, hotel. ## Why it matters German businesses face real legal exposure — a single Abmahnung (formal warning) commonly costs €500–5000. This server lets an AI assistant answer compliance questions from authoritative statute text instead of guessing, and then actually scan and fix a website in the same workflow. Pricing: Free 3 scans/month · Eins €9 · Pro €19 · Agency €89 — [dsgvo.pro/mcp](https://dsgvo.pro/mcp)

MCP readiness

B · 87/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	24/25	Endpoint answers the MCP initialize handshake (3078 ms); slow response -1.
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 7 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Slow (3078 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 88% of peers; This listing 87 · peer median 81
Latency: Faster than 25% of peers; This listing 562 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Protocol revision −2 — Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-08-20 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/cloncopy/dsgvo-pro/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/cloncopy/dsgvo-pro/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://dsgvo.pro/mcp

Listed at (smithery)

https://dsgvo.pro/mcp