Skills/Glama/betterkey-mcp

betterkey-mcp@0.1.4

VERIFIED· install only

Publisher claims: "Enables AI agents to inspect connected vehicles and issue lock/unlock commands through a scoped, authenticated vehicle API, with telemetry, capability, location access, and explicit confirmation for destructive actions." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher cmlabsllc · publishing for 20 daysInstalls 0Last detonated 8 h ago
$npx skills add betterkey-mcp
WatchReport an issue

Coverage

Nothing executable in the bundle ran; the trace covers the install step only.
Tested
every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

What this means for the label: Verified 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
BETTERKEY_API_KEYConfiguration, not credentials: BETTERKEY_API_BASE
Where it talks to
betterkey.xyz (its own)
What the honeypot saw
no credential files read · no network
What we could not test
use of the skill by an agent

Connect it with a scoped credential, under the guard. It asks for BETTERKEY_API_KEY and talks to betterkey.xyz. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets BETTERKEY_API_KEY=betterkey.xyz -- <the server's command>

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 (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-14 and scored it 91/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 1 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessscript backend runs setup only
0.0sprocessscript backend runs setup only
0.0sprocessno install scripts to re-run

Static findings

LOW
Unpinned dependency.github/workflows/publish.yml:21 · Unpinned dependency- run: npm install -g npm@latestFix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
AST06

No other findings across 3,772 lines in 25 files.

Cost to the agent

Instructions loaded
≈37 tok
1 file · 25 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.