@echomem/mcp@1.4.50
EchoMem MCP bridge for cross-agent memory, local history import, and recall
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe flagged agent integration behavior is tied to explicit EchoMem setup and local session processing, while the manifest has no install-time trigger. The inspected authentication code directs authenticated requests to the configured EchoMem API base URL.
Decision evidence
public snapshot- The manifest identifies the package entrypoint and has no npm install lifecycle hook; its packaging hook is prepack.
- Two bundled scorer utilities locate local Codex session files, while the monitor reads session metadata and migration code recognizes Claude project paths.
- The setup flow installs EchoMem session hooks for detected clients when its CLI setup flow runs; the hooks invoke this package’s own local commands.
- The default API host is EchoMem’s configured service, and authenticated requests use that same API base URL.
Source & flagged code
7 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.50.
See all versions of @echomem/mcp for other recorded verdicts.
- Review the evidence and your use of @echomem/mcp@1.4.50 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.