vibops-mcp@0.61.1
VERIFIEDPublisher claims: "VibOps MCP server — control your GPU infrastructure from any MCP-compatible client" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-10-26 and scored it 89/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 1 s · 2 scenarios · 0 deviationst+CategoryObserved action
0.0sprocessno install scripts in bundle
1.1sprocessdependency install exit 1
1.2sprocessexec /usr/bin/timeout
1.2sprocessexec .venv/bin/vibops-mcp
1.2sprocessexited 127: timeout: failed to run command '.venv/bin/vibops-mcp': No such file or directory
1.2sclaimedno tools/list reply (exit 127)
1.2sprocessscript backend runs setup only
Static findings
HIGH
Access to sensitive file pathsvibops_mcp/tools/actions.py:460 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05No other findings across 5,701 lines in 30 files.