Remote MCP · Endpoint
Laudos Veiculares DEKRA: LCD (Classificação de Danos) MCP server
No. Laudos Veiculares DEKRA: LCD (Classificação de Danos) answered an MCP handshake 16 hours ago.
UpLast checked 16 hours ago
Server URL
https://api.mcp.ai/p_laudos_veiculares_dekra_lcd
The last check completed an MCP handshake.
- Registry name
- io.github.mcp-dir/laudos_veiculares_dekra_lcd-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 647 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- Laudos Veiculares DEKRA: LCD (Classificação de Danos), official-source lookup. Platform-hosted, pay
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 16 hours ago | Handshake completed | 647 ms |
| 1 day ago | Handshake completed | 52 ms |
| 2 days ago | Handshake completed | 1.50 s |
| 3 days ago | Handshake completed | 520 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 Laudos Veiculares DEKRA: LCD (Classificação de Danos) and makes no claim about it beyond what these checks measured.