Remote MCP · Endpoint

DETRAN PR: CNH MCP server

No. DETRAN PR: CNH answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://api.mcp.ai/p_detran_pr_cnh

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/detran_pr_cnh-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
47 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
DETRAN PR: CNH, official-source lookup. Platform-hosted, pay per query with prepaid credit.
Listing
From the official MCP registry (active).
Recent checks of DETRAN PR: CNH
CheckedResultHandshake
1 day agoHandshake completed47 ms
3 days agoHandshake completed281 ms
5 days agoHandshake completed34 ms
7 days agoHandshake completed69 ms
8 days agoHandshake completed85 ms
9 days agoHandshake completed30 ms
12 days agoHandshake completed53 ms
13 days agoHandshake completed60 ms
15 days agoHandshake completed2.73 s
16 days agoHandshake completed57 ms
18 days agoHandshake completed54 ms
19 days agoHandshake completed130 ms
20 days agoHandshake completed61 ms
20 days agoHandshake completed66 ms
21 days agoHandshake completed581 ms
22 days agoHandshake completed39 ms

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

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