Remote MCP · Endpoint

Wrench.Pro Vehicle Check MCP server

No. Wrench.Pro Vehicle Check answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://mcp.wrench.pro/mcp

The last check completed an MCP handshake.

Registry name
pro.wrench/vehicle-check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
129 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Recalls, known issues, and honest maintenance costs for any US-market vehicle since 1990.
Listing
From the official MCP registry (active).
Recent checks of Wrench.Pro Vehicle Check
CheckedResultHandshake
7 hours agoHandshake completed129 ms
2 days agoHandshake completed188 ms
5 days agoHandshake completed77 ms
7 days agoHandshake completed115 ms
9 days agoHandshake completed96 ms
11 days agoHandshake completed105 ms
13 days agoHandshake completed67 ms
15 days agoHandshake completed76 ms
17 days agoHandshake completed67 ms
19 days agoHandshake completed85 ms
20 days agoHandshake completed70 ms
21 days agoHandshake completed159 ms
23 days agoHandshake completed145 ms

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

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 Wrench.Pro Vehicle Check and makes no claim about it beyond what these checks measured.