Remote MCP · Endpoint

Tn Dmv MCP server

No. Tn Dmv answered an MCP handshake 25 minutes ago.

UpLast checked 25 minutes ago

Server URL

https://gateway.pipeworx.io/tn-dmv/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/tn-dmv
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
838 ms
Tools exposed
38 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Tennessee DMV MCP — Department of Safety and Homeland Security: the 186 driver service
Listing
From the official MCP registry (active).
Recent checks of Tn Dmv
CheckedResultHandshake
25 minutes agoHandshake completed838 ms
2 days agoHandshake completed63 ms
4 days agoHandshake completed61 ms
5 days agoHandshake completed56 ms
7 days agoHandshake completed77 ms
8 days agoHandshake completed76 ms
9 days agoHandshake completed79 ms
12 days agoHandshake completed40 ms
13 days agoHandshake completed46 ms
15 days agoHandshake completed54 ms
17 days agoHandshake completed39 ms
18 days agoHandshake completed52 ms
19 days agoHandshake completed40 ms
20 days agoHandshake completed79 ms
21 days agoHandshake completed41 ms
21 days agoHandshake completed57 ms
23 days agoHandshake completed44 ms

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

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