@echomem/mcp@1.4.36
EchoMem MCP bridge: cloud-first memory tools and the Agent Doctor workspace forensics report (cost ledger + 3D repo city)
AI Security Review
scanned 3mo ago · by lpm-firewall-aiNo concrete malicious or unconsented install-time behavior was found. Warn because explicit setup persistently modifies agent configuration and behavior-bearing guidance across user AI clients.
Decision evidence
public snapshot- dist/setup.js: init/setup writes MCP entries, global agent guidance, bundled skills, and optional hooks.
- The injected global guidance directs agents to proactively search and save through EchoMem.
- dist/hud/hooks.js installs command hooks into Codex and Claude Code configuration.
- dist/hud/autostart.js can create a macOS LaunchAgent via an explicit CLI command.
- package.json has no preinstall, install, postinstall, or prepare lifecycle hook.
- All agent-control and persistence writes are reached through explicit init/setup or HUD CLI commands.
- No stealth, remote payload execution, credential harvesting, or destructive filesystem chain was found.
- dist/index.js network use is the package's authenticated EchoMem memory API.
Source & flagged code
6 flaggedSource writes installer persistence such as shell profile or service configuration.
dist/hud/autostart.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to @echomem/mcp@1.4.36.
See all versions of @echomem/mcp for other recorded verdicts.
- Review the evidence and your use of @echomem/mcp@1.4.36 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.