stlink-mcp@0.9.0
VERIFIED· not startedPublisher claims: "An MCP server that lets an AI coding agent program, run and inspect STM32 targets over ST-LINK, with every result marked verified, unverified or failed, and the evidence for it." 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: 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
- no credential variables read in the code
- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 0.8.5
vet-skills diff stlink-mcp 0.8.5 0.9.0In the sandbox, this version reached for nothing 0.8.5 did not. Compared from the two recorded runs, not from source.
0.8.5 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
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-19 and scored it 84/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 · 1 s · 2 scenarios · 0 deviationsStatic findings
on = subprocess.run(["uhubctl", "-l", hub, "-p", ports, "-a", "on"], capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.proc = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run([str(objcopy), "-O", "binary", str(elf), str(raw)], check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run([str(objcopy), "-O", "ihex", str(elf), str(hexfile)], check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.self._proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.saved = subprocess.run([programmer, "-c", "port=SWD", f"sn={serial}", "mode=HOTPLUG",Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run([str(signing_tool), "-bin", str(raw), "-nk", "-t", "fsbl", "-hv", "2.3",Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.listing = subprocess.run([str(objdump), "-d", str(elf)], capture_output=True, text=True, check=True).stdoutFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.restored = subprocess.run([programmer, *connect, "-w", str(trimmed), "0x08000000", "-v"],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.bench.console_text = "\ufffd\ufffd\u679e\ufffd\ufffd\ufffd\u6606\ufffd\ufffd\u6618\ufffd\ufffd\ufffd\ufffd\u679e\ufffd\ufffd"Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.self._proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.reason="root reads a file whatever its mode, and on Windows chmod only sets "Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.off = subprocess.run(["uhubctl", "-l", hub, "-p", ports, "-a", "off"], capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.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
No advisories in OSV for stlink-mcp@0.9.0 as of 4 h ago. This is the package itself, not its dependencies.