Skills/PyPI/iflow-mcp-clickhouse-mcp-clickhouse

iflow-mcp-clickhouse-mcp-clickhouse@0.1.13

VERIFIED

Publisher claims: "An MCP server for ClickHouse." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher clickhouse · joined 9 days agoInstalls 17Last detonated 18 h ago
$claude mcp add iflow-mcp-clickhouse-mcp-clickhouse -- uvx iflow-mcp_clickhouse-mcp-clickhouse
WatchReport an issue

Is [email protected] safe to install?

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

Static findings

MEDIUM
Destructive file system command detected.github/workflows/ci.yaml:74 · Destructive file system command detectedFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
MCP server using network transport (SSE/HTTP)mcp_clickhouse/mcp_env.py:269 · MCP server using network transport (SSE/HTTP) — data sent over networkFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04