@cachly-dev/mcp-server@0.10.124
Your AI forgets everything between sessions. cachly fixes that permanently. Persistent memory + causal root-cause analysis for Claude Code, Cursor, Copilot & Windsurf. Learns from every bug fix, git commit, and CI run automatically. Arrives pre-briefed. P
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource confirms a user-invoked, first-party AI-agent extension setup with persistent hooks and configured network use, not concrete malicious install-time behavior or stealthy exfiltration. Per policy, this warrants a warning rather than a block.
Decision evidence
public snapshot- Explicit setup/autopilot writes MCP and AI-instruction files, then installs Git and Claude hooks.
- Generated Claude instructions mandate Cachly calls at conversation start and before every task.
- The installed post-commit hook silently launches Cachly ingestion with commit metadata.
- Runtime authentication persists a Cachly credential/configuration entry in the user's Claude config.
- The npm postinstall script only prints setup instructions; it performs no filesystem, network, or config mutation.
- AI-agent and hook mutations are reached through explicit init/setup/autopilot commands, not installation.
- Observed Cachly network destinations are package-aligned first-party endpoints.
Source & flagged code
14 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references child process execution.
dist/src/bench/cachly-bench.jsView on unpkg · L40Findings
Affected versions and remediation
This report applies to @cachly-dev/mcp-server@0.10.124.
See all versions of @cachly-dev/mcp-server for other recorded verdicts.
- Review the evidence and your use of @cachly-dev/mcp-server@0.10.124 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.