Remote MCP · Endpoint
GDPR PII Shield & EU AI Act Anonymization Gate MCP server
No. GDPR PII Shield & EU AI Act Anonymization Gate answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://agent-gateway-i3gust564q-ey.a.run.app/mcp/privacy-pii-shield
The last check completed an MCP handshake.
- Registry name
- eu.iotpay/privacy-pii-shield
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 613 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- Zero-retention GDPR PII redaction gate (IBAN, Tax-ID, HRB, Names) with signed Ed25519 VC.
- Website
- https://iotpay.eu/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 613 ms |
| 1 day ago | Failed - the server returned an HTTP error | — |
| 1 day ago | Failed - the server returned an HTTP error | — |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 1 responding of 3.
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 GDPR PII Shield & EU AI Act Anonymization Gate and makes no claim about it beyond what these checks measured.