iflow-mcp-cam10001110101-mcp-server-jsoncanvas@0.1.0
VERIFIEDPublisher claims: "MCP server for working with JSON Canvas files" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Registry PyPI (MCP server)Publisher yourusername · joined 8 days agoInstalls 14Last detonated 30 h ago
$claude mcp add iflow-mcp-cam10001110101-mcp-server-jsoncanvas -- uvx iflow-mcp_Cam10001110101-mcp-server-jsoncanvas
WatchReport an issueIs [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-02 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 deviationst+CategoryObserved action
0.0sprocessno install scripts in bundle
0.2sprocessdependency install exit 1
0.3sprocessexec /usr/bin/timeout
0.3sprocessexec .venv/bin/mcp-server-jsoncanvas
0.3sprocessexited 127: timeout: failed to run command '.venv/bin/mcp-server-jsoncanvas': No such file or directory
0.3sclaimedno tools/list reply (exit 127)
0.3sprocessscript backend runs setup only
Static findings
MEDIUM
Pipe-to-shell patternDockerfile:13 · 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.
AST06MEDIUM
Remote installer piped to shellDockerfile:13 · Remote installer piped to shellFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST07MEDIUM
Destructive file system command detectedDockerfile:10 · Destructive file system command detectedFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05