mcp-ltspice-qucs@0.6.2
CAUTION· static onlyPublisher claims: "RF engineering MCP servers for LTspice/ngspice, Qucs-S, and simulator-agnostic RF analysis, in one package" Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Before you give it your token
Code inventory arrives with this version's next honeypot run.- It will ask for
- unknown until the next run
- Where it talks to
- unknown until the next run
- What the honeypot saw
- nothing has run yet
- What we could not test
- everything: the server has not run yet
Run it before you trust it. Nothing has run yet: the code was read, the server was not. `vet-skills try` runs this exact version in the honeypot in about a minute.
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 analysed it statically (a sandbox run is pending) on 2026-11-08 and scored it 59/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: Latin word with Cyrillic or Greek look-alike letters (homoglyph); Latin word with Cyrillic or Greek look-alike letters (homoglyph); Latin word with Cyrillic or Greek look-alike letters (homoglyph). Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
cosθFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.ΓoptFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.process = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.ΓoptFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.ΓoptFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.ΓoptFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.ΓoptFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.return subprocess.check_output(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.ΓoptFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for mcp-ltspice-qucs@0.6.2 as of 6d ago. This is the package itself, not its dependencies.
What would make this Verified
21 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim rfingadam: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
- 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.