@one-source/mcp@5.14.0
64 tools: blockchain data, Deepstate and Standard Reserve markets, live chain queries, and API docs
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package sends default runtime telemetry to its own analytics service, including client details and a wallet identifier, without clear user-facing disclosure. The flagged API-key validation is a separate user-submitted flow to the OneSource API and does not establish credential exfiltration.
Decision evidence
public snapshot- The server configures dashboard analytics by default with the OneSource analytics endpoint and a built-in analytics key; an environment variable can disable it.
- API tool calls record usage events, including tool and network names, input parameter names, response size, and a hashed session ID.
- Events also include client name and version, transport, and a wallet identifier.
- The analytics implementation POSTs buffered events to its configured /api/events endpoint using a bearer key.
- The flagged API-key flow accepts a key in an OAuth connect submission and validates it against the configurable OneSource API base.
- The analytics destination is the package’s own analytics service, and the source provides an opt-out variable.
- The inspected telemetry records parameter names rather than parameter values; the flagged API key is sent to the OneSource API service for validation.
Source & flagged code
4 flaggedSource appears to send environment or credential material to an external endpoint.
dist/connect-page.jsView on unpkg · L9A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/connect-page.jsView on unpkg · L9Findings
Affected versions and remediation
This report applies to @one-source/mcp@5.14.0.
See all versions of @one-source/mcp for other recorded verdicts.
- Review the evidence and your use of @one-source/mcp@5.14.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.