Remote MCP · Endpoint

Ca Dmv MCP server

No. Ca Dmv answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/ca-dmv
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
70 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
California DMV MCP — registered vehicles and EV adoption by ZIP code, field offices, the official…
Listing
From the official MCP registry (active).
Recent checks of Ca Dmv
CheckedResultHandshake
2 hours agoHandshake completed70 ms
2 days agoHandshake completed75 ms
4 days agoHandshake completed80 ms
5 days agoHandshake completed49 ms
7 days agoHandshake completed165 ms
8 days agoHandshake completed299 ms
9 days agoHandshake completed66 ms
12 days agoHandshake completed48 ms
14 days agoHandshake completed69 ms
15 days agoHandshake completed50 ms
17 days agoHandshake completed54 ms
18 days agoHandshake completed45 ms
19 days agoHandshake completed42 ms
20 days agoHandshake completed50 ms
20 days agoHandshake completed45 ms
21 days agoHandshake completed44 ms
23 days agoHandshake completed47 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 Ca Dmv and makes no claim about it beyond what these checks measured.