@echomem/mcp@1.4.56
EchoMem MCP bridge for cross-agent memory, local history import, and recall
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo malicious npm lifecycle behavior or covert install-time control-surface mutation was found. The persistent hooks, automatic runtime updates, and conversation-ingestion capability warrant a warning for agent-extension lifecycle risk.
Decision evidence
public snapshot- The running MCP checks for updates and automatically stages a newer release in the background.
- Explicit setup installs commands into Codex and Claude lifecycle-hook configuration.
- A memory-save operation sends supplied conversation data to the EchoMem API.
- package.json has no preinstall, install, or postinstall script.
- The nested runtime installer uses npm with --ignore-scripts.
- Configuration changes are reached through explicit init, setup, or update commands, not package installation.
- The HUD binds its HTTP server to loopback.
Source & flagged code
9 flaggedPackage source references child process execution.
dist/durable-entry.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @echomem/mcp@1.4.56.
See all versions of @echomem/mcp for other recorded verdicts.
- Review the evidence and your use of @echomem/mcp@1.4.56 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.