bawbel-mcp@1.1.0
VERIFIEDPublisher claims: "MCP server exposing Bawbel Scanner as agent-callable security tools" 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-28 and scored it 90/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
0.6sprocessdependency install exit 1
0.7sprocessexec /usr/bin/timeout
0.7sprocessexec .venv/bin/bawbel-mcp
0.7sprocessexited 127: timeout: failed to run command '.venv/bin/bawbel-mcp': No such file or directory
0.7sclaimedno tools/list reply (exit 127)
0.7sprocessscript backend runs setup only
Static findings
MEDIUM
Python subprocess execution detectedbawbel_mcp/server.py:69 · Python subprocess execution detectedFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05MEDIUM
Python subprocess execution detectedbawbel_mcp/server.py:736 · Python subprocess execution detectedFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05MEDIUM
Python subprocess execution detectedbawbel_mcp/server.py:482 · Python subprocess execution detectedFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05