@cachly-dev/mcp-server@0.10.203
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 runtime places an existing service JWT in telemetry bodies, with only an opt-out guard and a configurable destination. Because the default recipient is the package's intended service, this supports a warning for conditional credential exposure rather than a block.
Decision evidence
public snapshot- The runtime obtains a Cachly JWT from environment variables, saved credentials, or the Cachly entry in .mcp.json.
- The telemetry helper sends the JWT and user fingerprint in the request body; telemetry is disabled only when CACHLY_NO_TELEMETRY is set to 1.
- Telemetry uses CACHLY_API_URL when configured and otherwise sends to api.cachly.dev.
- The postinstall hook only prints setup instructions and performs no file or network operation.
- The default telemetry recipient, api.cachly.dev, is also the package's intended API service.
- The telemetry request is guarded by an explicit no-telemetry environment setting.
Source & flagged code
17 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.203.
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.203 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.