DSGVO.pro — German Digital-Law Compliance
REMOTE · DSGVO.PRO
Search 26 German/EU statutes free — then scan any website against 33 compliance modules.
Available components
Last scanned (22 hours ago)
Scores higher than 97% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 3146 tokens (~95/item across 33 items; 6 tools + 27 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 0
- Schema quality: 68 → 95 ▼ functional
- Schema quality: good → excellent functional
- 15 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check-compliance” rewrote its description, which is the text the model reads security
- Tool “get-scan-status” rewrote its description, which is the text the model reads security
- Tool “search-law” rewrote its description, which is the text the model reads security
- Resource “KosmetikVO Paragraph” was removed ▼ functional
- Schema quality: excellent → good functional
- New resource “KosmetikV Paragraph” functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Probed https://dsgvo.pro/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dsgvo.pro | CN=YR1,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | RSA 2048 | SHA256-RSA | 6d734d992a0611c04f07a755e5cc0b7b540 |
| SANs: dsgvo.pro | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dsgvo.pro. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| pro. | present | 33289, 42154 | 8, 8 | Verified |
| dsgvo.pro. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://stats.ai-firma.de; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://*.supabase.co; font-src 'self'; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.trigger.dev wss://api.trigger.dev https://stats.ai-firma.de; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dsgvo.pro/api/mcp | Verified | 200 | |
| http (plaintext) | http://dsgvo.pro/api/mcp | HTTPS enforced | 308 | https://dsgvo.pro/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check-compliance Start Website Compliance Scan ~455
🔑 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 hosting-location verification with SCC declaration audit, §312k BGB Kündigungsbutton, BFSG accessibility (active 28.06.2025). Pro/Agency tier (13 exclusive modules): §356a BGB Widerrufsbutton (active 19.06.2026 — currently the only EU compliance-scanner with this check), KI-VO transparency and data-processing requirements (Article 13/14 + Article 50 AI Act), advanced security audit (Art. 32 DSGVO — TLS protocol, mixed content, CMS-version CVE detection), tech-stack staleness (CMS/framework versions vs NVD CVE database), plus 8 industry-specific compliance modules — lawyer (BORA/BRAO), real-estate broker (§34c GewO + MaBV + §87 GEG energy-pass disclosure in listings), physician (BOÄ + HWG + Art. 9 GDPR sensitive-data), financial intermediary (§34d/f/h/i GewO + FinVermV), gastronomy (LMIV allergen labeling + PAngV + IfSG hygiene), cosmetics studio (KosmetikV + HWG before/after imagery), construction (§34c GewO Bauträger-Erlaubnis + HwO + MiLoG/SOKA), hotel (BMG registration + PAngV tourist-tax inclusive pricing + GEG). Industry detection runs from page content — only triggers relevant checks. ⚠️ IMPORTANT: This tool returns only a scanId — NOT the results. The scan takes 60–120 seconds. After calling this, wait 60–90 seconds, then call get-scan-result with the scanId. Use get-scan-status to check progress without waiting for completion.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The website URL to scan (e.g. https://example.com) |
| Name | Type | Req | Description |
|---|---|---|---|
| details | string | – | – |
| error | string | – | Set instead of scanId when the scan could not be started |
| hint | string | – | – |
| message | string | – | – |
| nextStep | string | – | – |
| scanId | string | – | Pass this to get-scan-status / get-scan-result |
| status | string | – | "pending" right after the scan is queued |
| url | string | – | Normalized URL that is being scanned |
No examples provided.
get-article Get Law Article ~86
Get the full German text of a specific article or paragraph from a law. Returns full text and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| article | string|number | yes | The article or paragraph number. Letter suffixes are supported and required for norms like "356a" (§356a BGB Widerrufsbutton), "312k", "312j". |
| law | string | yes | The law identifier |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Set instead of the fields above when the norm was not found |
| law | string | – | – |
| lawName | string | – | Full German name of the statute |
| metadata | object | – | – |
| num | string | – | Article/paragraph incl. suffix, e.g. "356a" |
| text | string | – | Full German text of the norm |
| title | string | – | – |
| unit | string | – | "Artikel" (EU regulations) or "Paragraf" (German statutes) |
No examples provided.
get-scan-result Get Scan Report ~102
Get 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 is still running, returns current progress instead of an error.
| Name | Type | Req | Description |
|---|---|---|---|
| scanId | string | yes | The scan ID returned by check-compliance |
| Name | Type | Req | Description |
|---|---|---|---|
| completedAt | string | – | ISO timestamp |
| error | string | – | – |
| message | string | – | – |
| modules | array | – | – |
| modulesCompleted | number | – | – |
| modulesTotal | number | – | – |
| riskLevel | string | – | – |
| scanId | string | – | – |
| scanReportUrl | string | – | Human-readable report on dsgvo.pro |
| score | number | – | Compliance score 0–100 (completed scans only) |
| startedAt | string | – | ISO timestamp |
| status | string | – | initializing | pending | crawling | scanning | completed | failed |
| url | string | – | – |
| violations | array | – | – |
No examples provided.
get-scan-status Check Scan Progress ~302
Lightweight 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 BGB), KI-Transparenz (Art. 50 KI-VO), Tech-Stack-Aktualität (Art. 32 DSGVO), Anwaltsspezifische Prüfung (BORA / BRAO), Maklerspezifische Prüfung (§34c GewO + MaBV + GEG), Arztspezifische Prüfung (BOÄ + HWG + Art. 9 DSGVO), Finanzvermittler-Prüfung (§34d/f/h/i GewO + FinVermV), Gastronomie-Prüfung (LMIV + PAngV + IfSG), Kosmetik-Prüfung (KosmetikV + HWG + UWG), Bau-/Sanierung-Prüfung (§34c GewO + HwO + MiLoG), Hotel-/Beherbergung-Prüfung (BMG + PAngV + GEG + DSGVO)). Use this to poll progress. When status is 'completed', call get-scan-result for the full report.
| Name | Type | Req | Description |
|---|---|---|---|
| scanId | string | yes | The scan ID returned by check-compliance |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| message | string | – | – |
| modulesCompleted | number | – | – |
| modulesRunning | number | – | – |
| modulesTotal | number | – | – |
| ready | boolean | – | true once the scan is completed or failed |
| scanId | string | – | – |
| startedAt | string | – | ISO timestamp |
| status | string | – | initializing | pending | crawling | scanning | completed | failed |
| url | string | – | – |
No examples provided.
list-laws List Available Laws ~23
List all available German/EU digital-law statutes with article/paragraph counts.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| laws | array | – | – |
No examples provided.
search-law Search German Law ~211
Search 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 AND free-text keywords ("Cookie", "Widerrufsbutton", "Einwilligung"). Returns matching articles/paragraphs with excerpts. Covers data protection, telecom & digital-services law, AI regulation, accessibility, unfair-competition (UWG), consumer and sector-specific law.
| Name | Type | Req | Description |
|---|---|---|---|
| law | string | – | Optional: limit search to a specific law |
| query | string | yes | Search query text |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | – | Matching articles/paragraphs, max 20 |
| totalMatches | number | – | Total hits before the 20-item cap |
No examples provided.
How do I install the DSGVO.pro — German Digital-Law Compliance MCP server?
DSGVO.pro — German Digital-Law Compliance is a hosted endpoint at https://dsgvo.pro/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · dsgvo.pro
claude mcp add --transport http pro-dsgvo-dsgvo-pro 'https://dsgvo.pro/api/mcp'
What is the DSGVO.pro — German Digital-Law Compliance MCP server?
DSGVO.pro — German Digital-Law Compliance is an MCP server listed in the public MCP registry as pro.dsgvo/dsgvo-pro. Search 26 German/EU statutes free, then scan any website against 33 compliance modules. This page covers its hosted endpoint (https://dsgvo.pro/api/mcp).
Is the DSGVO.pro — German Digital-Law Compliance MCP server safe to use?
DSGVO.pro — German Digital-Law Compliance scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DSGVO.pro — German Digital-Law Compliance MCP server expose?
DSGVO.pro — German Digital-Law Compliance exposes 6 tools: search-law, get-article, list-laws, check-compliance, get-scan-status, get-scan-result. Their descriptions and schemas cost roughly 1,179 tokens of context every time the server is loaded.
Does the DSGVO.pro — German Digital-Law Compliance MCP server require authentication?
No. We connected to DSGVO.pro — German Digital-Law Compliance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DSGVO.pro — German Digital-Law Compliance MCP server still maintained?
DSGVO.pro — German Digital-Law Compliance is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.