iflow-mcp-gongrzhe-acp-mcp-server@0.0.5
VERIFIEDPublisher claims: "Bridge server connecting Agent Communication Protocol (ACP) agents with Model Context Protocol (MCP) clients" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
$claude mcp add iflow-mcp-gongrzhe-acp-mcp-server -- uvx iflow-mcp_gongrzhe_acp-mcp-server
WatchReport an issueIs [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-03 and scored it 87/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.4sprocessdependency install exit 1
0.4sprocessexec /usr/bin/timeout
0.4sprocessexec .venv/bin/iflow-mcp-gongrzhe-acp-mcp-server
0.4sprocessexited 127: timeout: failed to run command '.venv/bin/iflow-mcp-gongrzhe-acp-mcp-server': No such file or directory
0.4sclaimedno tools/list reply (exit 127)
0.4sprocessscript backend runs setup only
Static findings
MEDIUM
MCP server using network transport (SSE/HTTP)acp_mcp_server/server.py:150 · 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.
AST04MEDIUM
MCP server using network transport (SSE/HTTP)acp_mcp_server/server.py:153 · 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.
AST04MEDIUM
MCP server using network transport (SSE/HTTP)acp_mcp_server/server.py:147 · 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