Remote MCP · Endpoint

Car Check MCP server

No. Car Check answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://cars.openkrill.app/mcp

The last check completed an MCP handshake.

Registry name
app.openkrill/cars
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
4.40 s
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Check a US car: decode a VIN, see recalls, crash ratings, owner complaints and fuel economy.
Listing
From the official MCP registry (active).
Recent checks of Car Check
CheckedResultHandshake
7 hours agoHandshake completed4.40 s
2 days agoHandshake completed367 ms
5 days agoHandshake completed645 ms
7 days agoHandshake completed392 ms
9 days agoHandshake completed349 ms
11 days agoHandshake completed439 ms
13 days agoHandshake completed849 ms
15 days agoHandshake completed1.03 s
17 days agoHandshake completed305 ms
19 days agoHandshake completed80 ms
20 days agoHandshake completed723 ms
21 days agoHandshake completed493 ms
23 days agoHandshake completed315 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 Car Check and makes no claim about it beyond what these checks measured.