Skip to content

DSGVO.pro — German Digital-Law Compliance MCP server

pro.dsgvo/dsgvo-prodsgvo.prostreamable-httpv1.0.0Scanned

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

7 tools: 1 can delete or cancel things, 1 change things and 5 only read.

Tools: 1 delete, 0 irreversible, 1 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the DSGVO.pro — German Digital-Law Compliance MCP server can do

The DSGVO.pro — German Digital-Law Compliance MCP server is published by dsgvo.pro, a domain the MCP Registry verified. It has 7 tools. It can delete or cancel things (1 tool: cancel-scan) and create or change data (1 tool: check-compliance). 5 tools only read.

1 tool brings in text other people can write (check-compliance); 1 tool can send data out of your system (check-compliance).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Deletes or cancels 1Claude Code: deny
  • cancel-scan🔑 Requires the same API key that started the scan.No findings

    Why it is in this group

    • The name "cancel-scan" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    🔑 Requires the same API key that started the scan. Stops a scan that is still running (pending/crawling/scanning) and returns the quota unit it cost, if the scan was started within the last hour. Use it when check-compliance was called by mistake or the wrong URL was scanned. A scan that already completed or failed cannot be cancelled and nothing is refunded. Scans started with a different API key are reported as not found. Free — does not use quota itself.

    Annotations the server declares

    • title: Cancel Running Scan
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 1Claude Code: ask
  • check-compliance🔑 Requires API key (Bearer header in MCP client config).Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote itContains invisible characters, shown as [U+…]
    🔑 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. ⚠[U+FE0F] 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.

    Annotations the server declares

    • title: Start Website Compliance Scan
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 5Show 5 read-only tools
  • get-articleGet the full German text of a specific article or paragraph from a law.No findings

    Why it is in this group

    • The name "get-article" says "get": a word for reading.
    Description, as the server wrote it
    Get the full German text of a specific article or paragraph from a law. Returns full text and metadata.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Get Law Article
  • get-scan-resultGet the full compliance report for a completed scan.No findings

    Why it is in this group

    • The name "get-scan-result" says "get": a word for reading.
    Description, as the server wrote itContains invisible characters, shown as [U+…]
    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. ⚠[U+FE0F] 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Get Scan Report
  • get-scan-statusLightweight progress check for an in-progress compliance scan.No findings

    Why it is in this group

    • The name "get-scan-status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Check Scan Progress
  • list-lawsList all available German/EU digital-law statutes with article/paragraph counts.No findings

    Why it is in this group

    • The name "list-laws" says "list": a word for reading.
    Description, as the server wrote it
    List all available German/EU digital-law statutes with article/paragraph counts.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: List Available Laws
  • 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, …No findings

    Why it is in this group

    • The name "search-law" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Search German Law

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:17 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://dsgvo.pro/api/mcp: tools/list returned 7 tools to an anonymous client, including cancel-scan (destructive), check-compliance (write)

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 1 to 2

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added.+1 addedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 2.View diff
    • Tools that change things, listed without credentials: 1 to 2

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http dsgvo-pro https://dsgvo.pro/api/mcp
claude mcp add --transport http dsgvo-pro https://dsgvo.pro/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__dsgvo-pro__search-law",
      "mcp__dsgvo-pro__get-article",
      "mcp__dsgvo-pro__list-laws",
      "mcp__dsgvo-pro__get-scan-status",
      "mcp__dsgvo-pro__get-scan-result"
    ],
    "ask": [
      "mcp__dsgvo-pro__check-compliance"
    ],
    "deny": [
      "mcp__dsgvo-pro__cancel-scan"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dsgvo-pro. Review it before you use it.

Capability tags behind 1 rule
  • mcp__dsgvo-pro__check-compliance untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/pro.dsgvo/dsgvo-pro/verify?hash=a02518eae7d0045f9b72583be58a328f4a8f7b896067d1d6ee5c035194f30f98" | jq -e '.changed == false'

Pinned hash a02518eae7d0, from Nov 19, 2026, 02:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/pro.dsgvo/dsgvo-pro/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for pro.dsgvo/dsgvo-pro
[![Anlyon Radar](https://radar.anlyon.com/badge/pro.dsgvo/dsgvo-pro.svg)](https://radar.anlyon.com/servers/pro.dsgvo/dsgvo-pro)

Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.

DSGVO.pro — German Digital-Law Compliance MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the DSGVO.pro — German Digital-Law Compliance MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the DSGVO.pro — German Digital-Law Compliance MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: cancel-scan.

Can the DSGVO.pro — German Digital-Law Compliance MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the DSGVO.pro — German Digital-Law Compliance MCP server have?

7 tools: 1 destructive, 1 write, 5 read. cancel-scan, check-compliance, search-law, get-article, list-laws, get-scan-status and get-scan-result.

Does the DSGVO.pro — German Digital-Law Compliance MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the DSGVO.pro — German Digital-Law Compliance MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check-compliance.

Has the DSGVO.pro — German Digital-Law Compliance MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 5, 2026. Every change is on this page and in its Atom feed.