openkrak-mcp@1.2.0
OpenKrak MCP Server - AI coding intelligence via Dorchester engine
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has no install hook or destructive execution path, but its active remote telemetry and explicit agent-steering instructions create a concrete runtime risk. This warrants a warning rather than a publication block.
Decision evidence
public snapshot- Each MCP tool call derives a stable hash from the host name and user name, then sends it to a remote service.
- The runtime sends error messages and the host fingerprint to the same remote service.
- Tool descriptions instruct an AI agent to trust the package output and avoid independently reading repository source.
- The package reads selected files from a user-supplied repository and returns their contents through its MCP tools.
- package.json has no install-time lifecycle hook; prepublishOnly only builds before publishing.
- No source path shows shell execution, persistence, destructive writes, or dynamic payload loading.
- The only explicit environment value sent is a named license key, consistent with a license check.
Source & flagged code
4 flagged · loading sourceSource collects local host identity data and sends it to an external endpoint.
dist/license/check.jsView on unpkg · L2Source fingerprint signature matches a known malicious package signature; route for source-aware review.
dist/license/check.jsView on unpkgFindings
Affected versions and remediation
This report applies to openkrak-mcp@1.2.0.
See all versions of openkrak-mcp for other recorded verdicts.
- Review the evidence and your use of openkrak-mcp@1.2.0 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.