@cachly-dev/mcp-server@0.10.205
Solve it once. From then on, your AI knows. Experience for coding agents, EU-hosted: an MCP server for Claude Code, Cursor, Copilot & Windsurf. Learns from every bug fix, commit and CI run.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe lifecycle hook only prints a suggested command; it does not install hooks or modify editor configuration. Inspected runtime requests and project indexing align with the enabled Cachly MCP service, with no concrete malicious behavior established.
Decision evidence
public snapshot- The npm postinstall runs a script that prints a suggested setup command; it does not perform setup itself.
- Editor configuration and ambient-hook setup occur through the separately invoked CLI setup flow.
- Credentials are read from Cachly environment variables or Cachly configuration, and the default API is api.cachly.dev.
- Telemetry is sent to the configured Cachly API; its sender supports a telemetry opt-out.
- The inspected runtime and handler files implement MCP features, including session-based project indexing that can be disabled.
Source & flagged code
16 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 unpkgFindings
Affected versions and remediation
This report applies to @cachly-dev/mcp-server@0.10.205.
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.205 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.