Remote MCP · Endpoint

CarGene MCP server

No. CarGene answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.car-gene.com/mcp

The last check completed an MCP handshake.

Registry name
com.car-gene/genealogy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.03 s
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Japanese car genealogy with sources: generations, developers, and sales figures. Read-only.
Listing
From the official MCP registry (active).
Recent checks of CarGene
CheckedResultHandshake
1 hour agoHandshake completed1.03 s
2 days agoHandshake completed679 ms
4 days agoHandshake completed649 ms
6 days agoHandshake completed620 ms
7 days agoHandshake completed553 ms
9 days agoHandshake completed614 ms
10 days agoHandshake completed587 ms
11 days agoHandshake completed627 ms
14 days agoHandshake completed589 ms
15 days agoHandshake completed571 ms
17 days agoHandshake completed640 ms
18 days agoHandshake completed646 ms
19 days agoHandshake completed578 ms
20 days agoHandshake completed654 ms
21 days agoHandshake completed612 ms
21 days agoHandshake completed679 ms
23 days agoHandshake completed2.41 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 CarGene and makes no claim about it beyond what these checks measured.