Remote MCP · Endpoint
TracePass DPP Compliance Assistant MCP server
No. TracePass DPP Compliance Assistant answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://ai.tracepass.eu/compliance/mcp
The last check completed an MCP handshake.
- Registry name
- eu.tracepass/compliance
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 321 ms
- Tools exposed
- 9 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- Answers EU Digital Product Passport questions: scope, required fields, registry and law changes.
- Website
- https://www.tracepass.eu/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 321 ms |
| 2 days ago | Handshake completed | 293 ms |
| 4 days ago | Handshake completed | 311 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 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 TracePass DPP Compliance Assistant and makes no claim about it beyond what these checks measured.