tesla-mcp@0.1.0
CAUTION· not startedPublisher claims: "Enables users to query a Tesla vehicle's battery, charging, climate, odometer, software, location, charging history, and local mileage or range reports through a local stdio MCP connector. Status can come from cached snapshots without waking the car, while wake-and-refresh is budget-gated and no vehicle commands are exposed." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
TESLA_AUTH_URLTESLA_CLIENT_SECRETTESLA_TOKEN_KEYTESLA_TOKEN_URLConfiguration, not credentials: TESLA_CLIENT_ID, TESLA_COMMAND_PROXY_CA, TESLA_COMMAND_PROXY_URL, TESLA_COMMANDS_ALLOWLIST, TESLA_COMMANDS_DRY_RUN, TESLA_ENABLE_CHARGING_HISTORY, TESLA_ENABLE_LOCATION, TESLA_FLEET_API_BASE, TESLA_LIVE_SMOKE, TESLA_MCP_CONFIG, TESLA_MCP_DATA_DIR, TESLA_POLL_INTERVAL_HOURS, TESLA_REDIRECT_URI, TESLA_REGION, TESLA_TIMEZONE, TESLA_WAKE_DAILY_CAP, TESLA_WAKE_MIN_INTERVAL_SECONDS, TESLA_WAKE_PER_MINUTE- Where it talks to
- no vendor host named in the codeAlso tesla.com, tesla.cn — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names tesla.com, tesla.cn as well as its own vendor. The guard injects TESLA_AUTH_URL, TESLA_CLIENT_SECRET, TESLA_TOKEN_KEY, TESLA_TOKEN_URL only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-15 and scored it 75/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.monkeypatch.setenv("TESLA_COMMAND_PROXY_URL", "https://user:[email protected]/hook")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.generated = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.monkeypatch.setenv("TESLA_COMMAND_PROXY_URL", "https://user:[email protected]:4443")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.description = "Placeholder strings from .env.example, not live credentials"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."https://user:[email protected]/oauth2/v3/token",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Load explicit config files. Never reads a `.env` from the working directory.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.No secrets have defaults. A `.env` file in the working directory is not read.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# planted .env cannot leak into later tests.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."https://8.8.8.8/oauth2/v3/token",Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.# a real secret in .env.example, the callback page, or the changelog must fail CI.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.(tmp_path / ".env").write_text(Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.chmod 644 "$dest/public-key.pem"Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.chmod 600 "$dest/private-key.pem"Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.inside = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.sudo install /tmp/gitleaks /usr/local/bin/gitleaksFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# can still supply the region. The cwd .env must not supply either.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."https://8.8.8.8/oauth2/v3/token",Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
5 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim naoiseirwin: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- URL with embedded credentials≈ +2 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- URL using a raw public IP address≈ +2 on the totalReplace encoded or assembled strings with plain literals and remove undeclared network calls.