Remote MCP · Endpoint

Tesla MCP server

No. Tesla answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_tesla

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/tesla-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.48 s
Tools exposed
17 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Tesla Fleet API for AI: send navigation destinations, read battery and location, run car commands.
Listing
From the official MCP registry (active).
Recent checks of Tesla
CheckedResultHandshake
1 hour agoHandshake completed1.48 s
1 day agoHandshake completed71 ms
2 days agoHandshake completed55 ms
3 days agoHandshake completed87 ms
4 days agoHandshake completed111 ms
5 days agoHandshake completed1.43 s
7 days agoHandshake completed742 ms
10 days agoHandshake completed69 ms
12 days agoHandshake completed136 ms
14 days agoHandshake completed60 ms
17 days agoHandshake completed168 ms
19 days agoHandshake completed64 ms
21 days agoHandshake completed312 ms
23 days agoHandshake completed111 ms
25 days agoHandshake completed67 ms

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

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