DSGVO.pro — German Digital-Law Compliance

pro.dsgvo/dsgvo-pro · v1.0.0 · security

DSGVO.pro — German Digital-Law Compliance is healthy: it completed an MCP handshake in 2007 ms and exposes 6 tools.

Search 26 German/EU statutes free — then scan any website against 33 compliance modules.

Endpoint: https://dsgvo.pro/api/mcp (streamable-http)

No repository listed · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count6
Latency2007 ms
Last checked (UTC)2026-10-15T13:15:14.187Z

Health history

Checked (UTC)StatusLatencyError
2026-10-15T13:15:14.187ZHealthy2007

Tools (6)

search-lawSearch across all 26 German/EU statutes (DSGVO, KI-VO, BDSG, TDDDG, DDG, BFSG, UWG, BGB, PAngV, VSBG, UrhG, VerpackG, VerpackDG, ElektroG, JuSchG, GewO, MaBV, GEG, BRAO, FinVermV, HwO, IfSG, KosmetikV, HWG, HOAI, MiLoG). Accepts paragraph references ("356a", "§ 312k", "Art. 42") for direct lookup AN
get-articleGet the full German text of a specific article or paragraph from a law. Returns full text and metadata.
list-lawsList all available German/EU digital-law statutes with article/paragraph counts.
check-compliance🔑 Requires API key (Bearer header in MCP client config). Free tier: 3 scans/month — get a key at https://dsgvo.pro/api-keys. Start a compliance scan against up to 33 German digital law modules. Standard tier covers 20 modules across DSGVO, TDDDG, DDG, BFSG, UWG, BGB, PAngV including Schrems II host
get-scan-statusLightweight progress check for an in-progress compliance scan. Returns current status (pending/crawling/scanning/completed/failed) and how many modules have finished (20 Standard or up to 33 with Pro/Agency tier including Hosting-Standort (Schrems II) (Art. 13 lit. f DSGVO), Widerrufsbutton (§356a B
get-scan-resultGet the full compliance report for a completed scan. Returns score (0–100), financial risk in EUR, per-module results, and all violations with law references, fine estimates, and fix instructions. ⚠️ Only call after the scan is complete — check status first with get-scan-status. If called while scan