@echomem/mcp@1.4.69
EchoMem MCP bridge for cross-agent memory, local history import, and recall
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the inspected agent configuration changes are reached through setup. Credential requests use the EchoMem API default; the reviewed source does not establish an unrelated recipient or unconsented control-surface mutation.
Decision evidence
public snapshot- package.json defines build, development, and prepack scripts, with no install lifecycle hook.
- The canonical scorer tools search local Codex session files using a supplied session identifier.
- The HUD monitor reads local Codex session index metadata to display thread titles.
- Migration code identifies local Claude project paths while discovering sessions.
- Setup can add EchoMem source-session and private-save hooks for detected clients through its setup flow.
- Login sends device credentials to the configured EchoMem API, which defaults to echo-mem-chrome.vercel.app.
Source & flagged code
8 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.69.
See all versions of @echomem/mcp for other recorded verdicts.
- Review the evidence and your use of @echomem/mcp@1.4.69 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.