optivibe-mcp@0.2.3
VERIFIED· not startedPublisher claims: "OptiVibe harness: ZOS-API automation, typed tools, and the single OptiVibe MCP" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Registry PyPI (MCP server)Publisher chuang44-tiff · publishing for 22 daysInstalls 474Last detonated 16 h ago
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.
$vet-skills run --net declared -- uvx optivibe-mcp
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-13 and scored it 80/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 deviationst+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.2sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run
Static findings
MEDIUM
Process kill commandsrc/optivibe_doctor/_runner.py:48 · Process kill command — agent can terminate processes
AST05#: The sixth worker mode. Spawned ONLY after an --engine overall-deadline kill that saw anFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Python subprocess execution detectedsrc/optivibe_doctor/_runner.py:1546 · Python subprocess execution detected
AST05completed = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.MEDIUM
Process kill commandsrc/optivibe_harness/process_reaper.py:9 · Process kill command — agent can terminate processes
AST05evidence key ONLY — it is NEVER a kill key. A user's interactive OpticStudio isFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_doctor/_runner.py:237 · Process kill command — agent can terminate processes
AST05"""The ``zemax`` child's kill deadline, from production's own connect-timeout knob.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_harness/engine_ledger.py:10 · Process kill command — agent can terminate processes
AST05orphan. Policy 2 (stale LIVE-session reclaim) is DEFERRED (it would killFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_doctor/_worker.py:1140 · Process kill command — agent can terminate processes
AST05to kill on either value. A real process's create_time is an epoch float, so ``0.0`` isFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_doctor/_worker.py:1081 · Process kill command — agent can terminate processes
AST05#: Left below the parent's own 30 s kill so the grandchild's timeout is reportable.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_harness/engine_ledger.py:14 · Process kill command — agent can terminate processes
AST05Reuses (L30 — the ONLY kill path / the ONLY atomic writer):Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_doctor/_runner.py:301 · Process kill command — agent can terminate processes
AST05# thread exists to keep the parent alive, so it cannot become a way to kill it.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Python subprocess execution detectedsrc/optivibe_doctor/_runner.py:331 · Python subprocess execution detected
AST05child = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.MEDIUM
Process kill commandsrc/optivibe_harness/engine_ledger.py:3 · Process kill command — agent can terminate processes
AST05Probe-grounded (BINDING). Claude Code's restart killFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_doctor/_worker.py:1144 · Process kill command — agent can terminate processes
AST05sprint has been closing. One predicate, so doctor's proof gate and production's killFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_doctor/_worker.py:1185 · Process kill command — agent can terminate processes
AST05``terminate_tracked`` REFUSES to kill on it), so a one-sided AccessDenied — realisticFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_harness/errors.py:100 · Process kill command — agent can terminate processes
AST05block or kill the engine, so a save or load is refused rather than hung.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_harness/_io.py:420 · Process kill command — agent can terminate processes
AST05full, a kill between the write and the newline) can still leave a torn FINAL line --Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Python subprocess execution detectedsrc/optivibe_doctor/_worker.py:1105 · Python subprocess execution detected
AST05completed = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.MEDIUM
Process kill commandsrc/optivibe_doctor/_worker.py:1193 · Process kill command — agent can terminate processes
AST05declared fail-safe. One predicate, so doctor's proof gate and production's kill gateFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_harness/engine_ledger.py:15 · Process kill command — agent can terminate processes
AST05- ``process_reaper.terminate_tracked`` — every kill routes through it (its own baselineFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_doctor/_runner.py:53 · Process kill command — agent can terminate processes
AST05#: Doctor's own band for the ``zemax`` child's kill deadline. The operator'sFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_harness/engine_ledger.py:9 · Process kill command — agent can terminate processes
AST05POLICY 1 ONLY (this cycle): a persistent, dead-parent-gated boot reap of a hard-killFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_doctor/_runner.py:63 · Process kill command — agent can terminate processes
AST05#: deadline is a kill rather than a suggestion.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.HIGH
Hidden zero-width characters detectedsrc/optivibe_harness/catalog/plot.py:136 · Hidden zero-width characters detected — may conceal content
AST07# first header cell becomes "design_name" and every design is mislabeled.Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.MEDIUM
Process kill commandsrc/optivibe_harness/process_reaper.py:121 · Process kill command — agent can terminate processes
AST05user's engine is not. "Never kill on doubt."Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_harness/session.py:293 · Process kill command — agent can terminate processes
AST05which callers must treat as NOT ours (never kill an engine we cannot prove is ours).Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_harness/process_reaper.py:188 · Process kill command — agent can terminate processes
AST05# and we might kill an unrelated recycled PID. Never kill on unverifiableFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_harness/process_reaper.py:167 · Process kill command — agent can terminate processes
AST05PID-reuse guard cannot prove identity, so we "never kill on doubt" ->Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_harness/session.py:363 · Process kill command — agent can terminate processes
AST05self._unresolved = {} # {pid: create_time} — parent unreadable; NO kill authorityFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_harness/process_reaper.py:27 · Process kill command — agent can terminate processes
AST05# filter the process snapshot to engine candidates — never as a kill key. AFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_harness/session.py:230 · Process kill command — agent can terminate processes
AST05"engine or kill it.")Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_harness/session.py:160 · Process kill command — agent can terminate processes
AST05# engine SaveAs / LoadFile / New BLOCK (>100 s) or kill the engine; reads, an LDEFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.MEDIUM
Process kill commandsrc/optivibe_harness/session.py:219 · Process kill command — agent can terminate processes
AST05"engine or kill it.")Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
Instructions loaded
≈56 tok
1 file · 81 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0
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 optivibe-mcp@0.2.3 as of 15 h ago. This is the package itself, not its dependencies.