asrai-mcp-apikey@1.7.4
Asrai crypto analysis MCP server — API key auth for ADVANCED plan users.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package's documented API-key flows and explicit skill installer appear consistent with its purpose. Server mode also records failed tool-call arguments in its database without a user-facing opt-out, which presents a runtime telemetry risk.
Decision evidence
public snapshot- In server mode, each tool call is logged to the mcp_tool_calls database table, including failed-call details and arguments.
- Logging runs after a tool call and only when ASRAI_INTERNAL_KEY is set; failed-call arguments are truncated and secret-looking fields are masked.
- The install-skill command copies the bundled skill files only when explicitly run, and API keys are sent to the package's Asrai service.
- The package declares no preinstall, install, or postinstall hook; its only lifecycle script is prepublishOnly.
- The stdio bridge sends its API key to the documented Asrai MCP endpoint as part of the stated API-key service.
- Exchange credentials are sent to the configured Asrai API endpoint for the positions tool.
Source & flagged code
5 flaggedManifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
bin/install-skill.jsView on unpkgFindings
Affected versions and remediation
This report applies to asrai-mcp-apikey@1.7.4.
See all versions of asrai-mcp-apikey for other recorded verdicts.
- Review the evidence and your use of asrai-mcp-apikey@1.7.4 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.