Skills/PyPI/iflow-mcp-mcp-cube-server

iflow-mcp-mcp-cube-server@0.0.2

VERIFIED

Publisher claims: "MCP server for interfacing with Cube.dev REST API" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher pypi · joined 9 days agoInstalls 13Last detonated 1 h ago
$claude mcp add iflow-mcp-mcp-cube-server -- uvx iflow-mcp_mcp_cube_server
WatchReport an issue

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-03 and scored it 81/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 · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.3sprocessdependency install exit 1
0.4sprocessexec /usr/bin/timeout
0.4sprocessexec .venv/bin/mcp_cube_server
0.4sprocessexited 127: timeout: failed to run command '.venv/bin/mcp_cube_server': No such file or directory
0.4sclaimedno tools/list reply (exit 127)
0.4sprocessscript backend runs setup only

Static findings

MEDIUM
Destructive file system command detectedDockerfile:9 · Destructive file system command detectedFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Pipe-to-shell pattern.github/workflows/python-publish.yml:31 · Pipe-to-shell pattern — downloads and immediately executes remote codeFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST06
MEDIUM
Remote installer piped to shell.github/workflows/python-publish.yml:31 · Remote installer piped to shellFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST07