stm32-gdb-mcp@0.15.1
VERIFIED· not startedPublisher claims: "MCP server for STM32 debugging with GDB" 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 codeAlso arm.com, segger.com, dummy.com — 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 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.
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 · 0 s · 2 scenarios · 0 deviationsStatic findings
result = subprocess.run(command, check=False)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.return subprocess.Popen(cmd, creationflags=base, **kwargs)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.(write-time SWO/ITM trace). In other IDEs the same guidance travels as a rules file (AGENTS.md). /Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.hard kill has been observed to wedge the ST-Link endpoint until the probeFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.mid-transaction -- a hard kill has been observed to wedge the ST-Link endpoint.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."probe. Close the owning debug session, stop its GDB server, or kill the "Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.return subprocess.Popen(cmd, start_new_session=True, **kwargs)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.parser.add_argument("--no-rules", action="store_true", help="do not write AGENTS.md / copilot-instructions")Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.text = text.lstrip("") # real ECAD exports (e.g. Altium) are UTF-8 with BOMFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.if requested == "auto" and importlib.util.find_spec("smartusbhub") is None:Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.- Never hard-kill OpenOCD; use `recover_session`. ST-Link SWD is exclusive.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.f"Close the debug session that owns this probe, or kill the zombie "Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.self.process = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.out = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.- Never hard-kill OpenOCD; use `recover_session`.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# On Linux the child asks the kernel to kill it if we die; on Windows theFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.return subprocess.Popen(cmd, creationflags=base | 0x01000000, **kwargs) # BREAKAWAY_FROM_JOBFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.head = text.lstrip("").lstrip()[:256].lower()Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.except Exception as exc: # noqa: BLE001 - never kill the daemon over one callFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.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 stm32-gdb-mcp@0.15.1 as of 5 h ago. This is the package itself, not its dependencies.