Remote MCP · Endpoint

CarHunt MCP server

No. CarHunt answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.carhunt.fr/mcp

The last check completed an MCP handshake.

Registry name
fr.carhunt/carhunt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
404 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
French used-car search across LeBonCoin, LaCentrale, L'Argus and more, with price estimates.
Listing
From the official MCP registry (active).
Recent checks of CarHunt
CheckedResultHandshake
1 hour agoHandshake completed404 ms
2 days agoHandshake completed394 ms
4 days agoHandshake completed420 ms
5 days agoHandshake completed496 ms
7 days agoHandshake completed377 ms
8 days agoHandshake completed561 ms
9 days agoHandshake completed372 ms
12 days agoHandshake completed396 ms
13 days agoHandshake completed376 ms
15 days agoHandshake completed436 ms
16 days agoHandshake completed624 ms
18 days agoHandshake completed359 ms
19 days agoHandshake completed331 ms
20 days agoHandshake completed489 ms
20 days agoHandshake completed339 ms
21 days agoHandshake completed393 ms
22 days agoHandshake completed1.09 s

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