@cachly-dev/mcp-server@0.10.207
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 source confirms that a configured API URL receives the resolved credential in authenticated requests, without a destination restriction. The default is package-aligned and the custom URL is operator-configurable, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The runtime defaults its API base to api.cachly.dev but allows CACHLY_API_URL to replace it.
- The API client sends requests to that base with the resolved credential in a Bearer header.
- The autopilot command accepts an explicit --api-url value and applies it to the API base.
- Credentials can be resolved from environment variables or saved Cachly configuration.
- Two runtime error paths send authenticated telemetry requests to the configured API base.
- The default API host is the package’s Cachly service, and the custom URL can be explicitly supplied by the operator.
- The postinstall script prints setup guidance; it does not itself send credentials.
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.207.
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.207 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.