@cachly-dev/mcp-server@0.10.129
Your AI forgets everything between sessions. cachly fixes that permanently: 122 MCP tools for Claude Code, Cursor, Copilot & Windsurf. Learns from every bug fix, commit and CI run. Arrives pre-briefed. Free tier forever, EU servers, GDPR.
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection found an output-only postinstall hook and no confirmed attack behavior. The scanner’s credential and agent-configuration signals map to service-aligned search and explicit setup behavior.
Decision evidence
public snapshot- The postinstall hook only prints setup guidance; it does not perform the advertised configuration changes.
- Credential persistence updates Cachly’s own MCP entry, while ambient hooks read the key from the environment or local credentials file.
- Semantic search uses the Cachly vector token in its default URL; a configured vector URL replaces that URL, and the request sends the search payload.
- The agent-related code inspected builds hooks and setup guidance; the inspected setup and git-hook paths are explicit CLI features.
- The benchmark, git hook, and author helper findings are scoped to benchmarking, post-commit setup, and reading Git configuration.
Source & flagged code
12 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.js#virtual:normalized:round1Findings
Affected versions and remediation
This report applies to @cachly-dev/mcp-server@0.10.129.
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.129 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.