Tesla MCP Server (Sara3/Tesla-MCP) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. It declares 9 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
56/100

Tesla MCP Server

An MCP server that connects to the Tesla Fleet API, allowing users to control vehicles and retrieve real-time status updates through Claude and other AI assistants. It supports functions such as waking up vehicles, viewing detailed vehicle information, and debugging via both stdio and HTTP/SSE transports.

→ Sara3/Tesla-MCP· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Sara3

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 13 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: TESLA_CLIENT_SECRET, TESLA_PUBLIC_KEY, TESLA_REFRESH_TOKEN, TWILIO_AUTH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes9 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

list_vehicles

List your Tesla vehicles and get their IDs (id, vehicle_id, vin).

wake_up

Wake up your Tesla vehicle from sleep mode.

refresh_vehicles

Refresh the list of Tesla vehicles from the API.

debug_vehicles

Show debug information about available vehicles.

get_vehicle_location

Get your Tesla's current location (latitude, longitude, map link).

get_battery_status

Get your Tesla's battery level, range, charging state, charge limit, and time to full charge.

get_climate_status

Get your Tesla's climate info: inside/outside temperature, climate on/off, seat heaters, and temperature settings.

get_vehicle_status

Get your Tesla's status: locked/unlocked, doors, windows, trunk/frunk, sentry mode, odometer, software update info.

nearby_charging

Find nearby Superchargers and destination chargers for your Tesla.

// known CVEs in dependencies13 high12 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highaxios@1.8.2GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.8.2GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.8.2GHSA-43fc-jf86-j433

Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig

highaxios@1.8.2GHSA-4hjh-wcwx-xvwj

Axios is vulnerable to DoS attack through lack of data size check

highaxios@1.8.2GHSA-6chq-wfr3-2hj9

Axios: Header Injection via Prototype Pollution

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configBASE_URLIn your MCP client, use Server URL: http://localhost:3000/sse (for production use HTTPS and set ).
configHOSTNo Bind address (default 0.0.0.0)
configNGROK_URL
configTESLA_CLIENT_IDOptional If set with TESLA_CLIENT_SECRET, users go straight to the Tesla login page (no setup page)
🔐 secretTESLA_CLIENT_SECRETTESLA_CLIENT_ID Optional If set with , users go straight to the Tesla login page (no setup page)
🔐 secretTESLA_PUBLIC_KEY
🔐 secretTESLA_REFRESH_TOKENYes From npm run get-token
configTWILIO_ACCOUNT_SIDOptional Twilio account SID (enables get_recent_texts / send_text)
🔐 secretTWILIO_AUTH_TOKENOptional Twilio auth token
configTWILIO_PHONE_NUMBEROptional Your Twilio phone number (E.164, e.g. +15551234567)
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

9/9 tools missing one or more hints — list_vehicles (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); wake_up (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); refresh_vehicles (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets not logged

2 secret values sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 13 high severity in production deps — axios@1.8.2 (high), axios@1.8.2 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/sara3/tesla-mcp?variant=verified)](https://m8ven.ai/mcp/sara3/tesla-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: e6e2b3a7451ad2488e14733b5dd15dc4123f314b
code hash: 4fbd4ff3b9124aeedfd233ea4f769d49a569cdbd227116eab5e7439e1a39926a
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client