Remote MCP · Endpoint

Car Check MCP server

No. Car Check answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes 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
365 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 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
44 minutes agoHandshake completed365 ms
3 days agoHandshake completed144 ms
13 days agoHandshake completed406 ms
13 days agoHandshake completed328 ms
15 days agoHandshake completed227 ms
15 days agoHandshake completed210 ms
17 days agoHandshake completed588 ms
18 days agoHandshake completed333 ms
18 days agoHandshake completed171 ms
20 days agoHandshake completed451 ms
22 days agoHandshake completed4.40 s
25 days agoHandshake completed367 ms
27 days agoHandshake completed645 ms
29 days agoHandshake completed392 ms

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

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.