Remote MCP · Endpoint

AUTO411 Vehicle Intelligence MCP server

No. AUTO411 Vehicle Intelligence answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.411specs.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.simonizer69/auto411-vehicle-intelligence
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
308 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Identity-first automotive intelligence for vehicle resolution, specs, safety and efficiency.
Listing
From the official MCP registry (active).
Recent checks of AUTO411 Vehicle Intelligence
CheckedResultHandshake
1 hour agoHandshake completed308 ms
9 days agoHandshake completed188 ms
10 days agoHandshake completed197 ms
11 days agoHandshake completed141 ms
12 days agoHandshake completed121 ms
14 days agoHandshake completed170 ms
14 days agoHandshake completed142 ms
15 days agoHandshake completed129 ms
17 days agoHandshake completed256 ms
19 days agoHandshake completed279 ms
21 days agoHandshake completed145 ms
24 days agoHandshake completed156 ms
26 days agoHandshake completed133 ms
28 days agoHandshake completed189 ms

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

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