Remote MCP · Endpoint

DPOLens MCP server

No. DPOLens answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://mcp.dpolens.com/

The last check completed an MCP handshake.

Registry name
com.dpolens/dpolens
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
356 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Privacy law your AI assistant can cite: the exact clause and its version. GDPR and UAE PDPL today.
Listing
From the official MCP registry (active).
Recent checks of DPOLens
CheckedResultHandshake
33 minutes agoHandshake completed356 ms
3 days agoHandshake completed835 ms
13 days agoHandshake completed184 ms
13 days agoHandshake completed396 ms
15 days agoHandshake completed326 ms
16 days agoHandshake completed330 ms
17 days agoHandshake completed401 ms
18 days agoHandshake completed351 ms
18 days agoHandshake completed357 ms
20 days agoHandshake completed392 ms
22 days agoHandshake completed409 ms
25 days agoHandshake completed353 ms
27 days agoHandshake completed348 ms

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

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 DPOLens and makes no claim about it beyond what these checks measured.