@cachly-dev/mcp-server@0.10.183
Solve it once. From then on, your AI knows. Experience for coding agents, EU-hosted: 124 MCP tools for Claude Code, Cursor, Copilot & Windsurf. Learns from every bug fix, commit and CI run.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe runtime permits an environment-selected API destination while attaching an existing Cachly credential, and the inspected request path shows no destination restriction. This supports a warning for conditional credential exposure, not a publish block.
Decision evidence
public snapshot- The install hook runs a script that prints setup guidance; the displayed setup is a separate user command.
- The MCP entrypoint accepts CACHLY_API_URL from the environment and defaults to the Cachly API.
- When a Cachly credential is present, runtime requests send it as a bearer token to the configured API URL.
- The cited request provisions an instance through that URL; the source does not show an endpoint allowlist in this request path.
- The postinstall script only prints instructions and does not itself perform the advertised setup.
- The package's default API endpoint is its own api.cachly.dev service.
Source & flagged code
14 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.183.
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.183 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.