mcp-agents-memory@0.9.15
Long-term memory for AI agents with provenance tracking
AI Security Review
scanned 1mo ago · by lpm-firewall-aiAutomatic collection of local agent-session content on normal server startup is a concrete, privacy-sensitive agent capability. The inspected code lacks a confirmed external exfiltration sink or install hook, so blocking as malware is not supported.
Decision evidence
public snapshot- The normal MCP-server startup automatically starts six session-capture routines.
- The Codex capture routine targets the user's Codex sessions directory.
- Captured user and assistant messages are passed to the memory insertion function.
- The package has no install lifecycle hook; its prepare script is a no-op.
- The required migration performs a scoped database schema change.
- No concrete external exfiltration endpoint was established from the inspected paths.
- No install-time execution or foreign agent-configuration write was found.
Source & flagged code
30 flaggedPackage contains a critical-looking secret pattern.
build/migrations/023_librarian_gate.jsView on unpkg · L9195RSA private key in build/migrations/023_librarian_gate.js
build/migrations/023_librarian_gate.jsView on unpkg · L9195Package source references child process execution.
build/migrations/023_librarian_gate.jsView on unpkg · L12898Findings
Affected versions and remediation
This report applies to mcp-agents-memory@0.9.15.
See all versions of mcp-agents-memory for other recorded verdicts.
- Review the evidence and your use of mcp-agents-memory@0.9.15 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.