Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.

Is dsgvo-pro free to use?

Yes — the hub reached it with no key and no payment.

What tools does dsgvo-pro have?

7 tools: get-article, get-scan-result, search-law, get-scan-status, check-compliance, cancel-scan, list-laws.

Is dsgvo-pro safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp streamable-http · checked 2h ago

dsgvo-pro

https://dsgvo.pro

Registry code: 6f42e4e9df0133f4

api record

DSGVO.pro MCP — German digital-law compliance platform.

FREE TOOLS (no API key; anonymous callers are capped at 30 requests/minute per IP):

endpoint: https://dsgvo.pro/api/mcp
protocol: streamable-http ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is dsgvo-pro live?: Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is dsgvo-pro free to use?: Yes — the hub reached it with no key and no payment.
What tools does dsgvo-pro have?: 7 tools: get-article, get-scan-result, search-law, get-scan-status, check-compliance, cancel-scan, list-laws.
Is dsgvo-pro safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

99.1%

90 days 99.5%· all time 99.5%

latency

146ms

last good check

priced tools

of 7 tools

_ answered our checks, 90 days 370 checks · signed record

2026-11-13 22:29 degraded → live
2026-11-12 13:02 live → degraded· timeout after 20000ms
2026-10-12 09:50 degraded → live
2026-09-27 16:34 unknown → live

_ what it is for

topic: security & compliance compliance & regulation
used for: search german and eu digital laws
get the text of a law article
scan a website for gdpr compliance
takes → gives: text, web pages → data, text
tools: 5 reads1 changes data

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 7 tools

1 open 6 never probed 1 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

list-laws reads open 24h ago
List all available German/EU digital-law statutes with article/paragraph counts.

mcp-tool
{ "type": "object", "properties": {} }
arguments 4 lines

get-article reads unknown 8h ago

Get the full German text of a specific article or paragraph from a law. Returns full text and metadata.

mcp-tool

{
  "type": "object",
  "required": [
    "law",
    "article"
  ],
  "properties": {
    "law": {
      "enum": [
        "dsgvo",
        "ki-vo",
        "bdsg",
        "tdddg",
        "ddg",
        "bfsg",
        "uwg",
        "bgb",
        "pangv",
        "vsbg",
        "urhg",
        "verpackg",
        "verpackdg",
        "elektrog",
        "juschg",
        "gewo",
        "mabv",
        "geg",
        "brao",
        "finvermv",
        "hwo",
        "ifsg",
        "kosmkv",
        "hwg",
        "hoai",
        "milog"
      ],
      "type": "string",
      "description": "The law identifier"
    },
    "article": {
      "type": [
        "string",
        "number"
      ],
      "description": "The article or paragraph number. Letter suffixes are supported and required for norms like \"356a\" (§356a BGB Widerrufsbutton), \"312k\", \"312j\"."
    }
  }
}

arguments 48 lines

get-scan-result reads unknown 8h ago
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.

mcp-tool
{ "type": "object", "required": [ "scanId" ], "properties": { "scanId": { "type": "string", "description": "The scan ID returned by check-compliance" } } }
arguments 12 lines

search-law reads unknown 24h ago

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.

mcp-tool

{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "law": {
      "enum": [
        "dsgvo",
        "ki-vo",
        "bdsg",
        "tdddg",
        "ddg",
        "bfsg",
        "uwg",
        "bgb",
        "pangv",
        "vsbg",
        "urhg",
        "verpackg",
        "verpackdg",
        "elektrog",
        "juschg",
        "gewo",
        "mabv",
        "geg",
        "brao",
        "finvermv",
        "hwo",
        "ifsg",
        "kosmkv",
        "hwg",
        "hoai",
        "milog"
      ],
      "type": "string",
      "description": "Optional: limit search to a specific law"
    },
    "query": {
      "type": "string",
      "description": "Search query text"
    }
  }
}

arguments 44 lines

get-scan-status reads unknown 24h ago
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.

mcp-tool
{ "type": "object", "required": [ "scanId" ], "properties": { "scanId": { "type": "string", "description": "The scan ID returned by check-compliance" } } }
arguments 12 lines
check-compliance changes data unknown never probed
🔑 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.

mcp-tool
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "The website URL to scan (e.g. https://example.com)" } } }
arguments 12 lines
cancel-scan unknown never probed
🔑 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.

mcp-tool
{ "type": "object", "required": [ "scanId" ], "properties": { "scanId": { "type": "string", "description": "The scan ID returned by check-compliance" } } }
arguments 12 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6f42e4e9df0133f4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6f42e4e9df0133f4/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/6f42e4e9df0133f4/badge.svg)](https://brick.blue/agent/6f42e4e9df0133f4?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.