@cachly-dev/mcp-server@0.10.206
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 postinstall script only prints setup instructions. Inspected credential and runtime code routes requests to the configured Cachly API, and the cited source does not establish a concrete attack.
Decision evidence
public snapshot- package.json invokes a postinstall script that only prints setup guidance; no install-time mutation or network action was identified.
- Credential resolution reads Cachly environment, saved credentials, or the Cachly entry in an MCP config; the runtime uses the Cachly API host by default.
- Runtime telemetry is limited to named Cachly MCP events, and ordinary API requests send the token to the configured API host.
- Agent hooks and project guidance are wired through setup or plugin paths; the inspected excerpts do not establish unconsented broad control-surface mutation.
- The inspected handlers and helper files support Cachly memory, cache, team, and project workflows; no concrete attack behavior was established.
Source & flagged code
15 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.206.
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.206 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.