mcp-server-kicad@0.21.1
VERIFIED· not startedPublisher claims: "Byte-preserving MCP servers for KiCad: schematic capture, PCB layout, ERC, DRC, and manufacturing exports" 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.
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-09 and scored it 85/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
When working on ANY electronics or KiCad task, you MUST follow thisFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.# the file this call created. In this order: chown clearsFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.python3 .github/tools/docs_only.py "$RUNNER_TEMP/skip.txt" < "$RUNNER_TEMP/changed.txt" | tee -a "$GITHUB_OUTPUT"Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.self.proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.…in a Claude Code session here do not see local changes. ## Architecture Five `MCPServer` servers, one module each: `schematic.py`, `pcb.py`, `project.py`, `symbol.py`, `footprint.py`. Each defines its own `mcp` instance and `main()` consol…Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.uv run python mcp_server_kicad/_cst.py # CST self-check (demo() asserts)Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.- No `subprocess.run(..., shell=True)` or f-string command building.Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.return subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.run = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.npx -y @modelcontextprotocol/inspector --cli uv run mcp-server-kicad --method tools/list # this checkout's tools, as a client sees themFix: Pin versions and sources; vendor anything fetched at install time.wire_pins_to_net it never refused, it only swapped a stub for a label on the pin.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…er by hand: `uv run mcp-server-kicad` (stdio), or under the MCP Inspector with `npx -y @modelcontextprotocol/inspector uv run mcp-server-kicad`. README.md's Inspector…Fix: Pin versions and sources; vendor anything fetched at install time.proc = subprocess.run(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.stopped. Three of the nineteen boards KiCad 10 ships kill pcbnew's bindingsFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# above, and 0xC0000409 is what pcbnew exits with on the boards that kill itsFix: 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 mcp-server-kicad@0.21.1 as of 5d ago. This is the package itself, not its dependencies.