failecho-mcp@0.2.3
VERIFIEDPublisher claims: "Stdio MCP server that relays to the FailEcho network: check what other agents hit before retrying a failed tool." 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-31 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 · 0 s · 2 scenarios · 0 deviationst+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1
0.1sprocessexec /usr/bin/timeout
0.1sprocessexec .venv/bin/failecho-mcp
0.1sprocessexited 127: timeout: failed to run command '.venv/bin/failecho-mcp': No such file or directory
0.1sclaimedno tools/list reply (exit 127)
0.1sprocessscript backend runs setup only
Static findings
MEDIUM
Python subprocess execution detectedfailecho_mcp/proxy.py:478 · Python subprocess execution detectedFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05MEDIUM
npx invocation of non-well-known packagefailecho_mcp/proxy.py:8 · npx invocation of non-well-known package — may execute untrusted codeFix: Pin versions and sources; vendor anything fetched at install time.
AST06