Remote MCP · Endpoint

EasyLPD: Swiss data protection (FADP) and GDPR MCP server

No. EasyLPD: Swiss data protection (FADP) and GDPR answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://easylpd.ch/api/mcp

The last check completed an MCP handshake.

Registry name
ch.easylpd/fadp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
291 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Swiss FADP (nLPD/revDSG) and GDPR: which laws apply, action plan, templates, transfers abroad.
Listing
From the official MCP registry (active).
Recent checks of EasyLPD: Swiss data protection (FADP) and GDPR
CheckedResultHandshake
37 minutes agoHandshake completed291 ms
4 days agoHandshake completed292 ms
7 days agoHandshake completed220 ms
16 days agoHandshake completed203 ms
16 days agoHandshake completed177 ms
18 days agoHandshake completed246 ms
19 days agoHandshake completed208 ms
20 days agoHandshake completed222 ms
21 days agoHandshake completed291 ms
22 days agoHandshake completed277 ms
23 days agoHandshake completed159 ms
26 days agoHandshake completed342 ms

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

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 EasyLPD: Swiss data protection (FADP) and GDPR and makes no claim about it beyond what these checks measured.