Remote MCP · Endpoint

DSGVO.pro — German Digital-Law Compliance MCP server

No. DSGVO.pro — German Digital-Law Compliance answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://dsgvo.pro/api/mcp

The last check completed an MCP handshake.

Registry name
pro.dsgvo/dsgvo-pro
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
172 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Search 26 German/EU statutes free — then scan any website against 33 compliance modules.
Listing
From the official MCP registry (active).
Recent checks of DSGVO.pro — German Digital-Law Compliance
CheckedResultHandshake
1 hour agoHandshake completed172 ms
12 hours agoHandshake completed189 ms
1 day agoHandshake completed176 ms
2 days agoHandshake completed186 ms
4 days agoHandshake completed240 ms
4 days agoHandshake completed151 ms
5 days agoHandshake completed170 ms
7 days agoHandshake completed213 ms
9 days agoHandshake completed203 ms
11 days agoHandshake completed169 ms
14 days agoHandshake completed175 ms
16 days agoHandshake completed162 ms
18 days agoHandshake completed169 ms
20 days agoHandshake completed165 ms
22 days agoHandshake completed151 ms
24 days agoHandshake completed171 ms
26 days agoHandshake completed163 ms
28 days agoHandshake completed176 ms
29 days agoHandshake completed205 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with DSGVO.pro — German Digital-Law Compliance and makes no claim about it beyond what these checks measured.