@one-source/mcp@5.23.2
Blockchain data, Deepstate and Standard Reserve markets, live chain queries, and API docs
AI Security Review
scanned 4d ago · by lpm-firewall-aiNo malicious credential flow was found: the flagged key path validates a user-submitted key against the configured OneSource API. Runtime usage analytics are enabled by default, but the setup tool discloses them as optional and provides an opt-out; the recorded events contain metadata and input field names rather than values.
Decision evidence
public snapshot- The setup tool describes anonymous usage analytics as optional, says it is on by default, and explains how to disable it with ONESOURCE_ANALYTICS=false.
- Tool-call analytics record tool and network metadata, response size, and input field names; the recorded input_params are Object.keys(input), not the input values.
- Analytics events are POSTed to the configured analytics endpoint. The flagged API key is separately validated against the configured OneSource API during the connect-submit flow.
- Analytics is enabled by default, so events may be sent before the user chooses to disable it.
- The connect flow transmits a user-submitted API key to the configured OneSource API 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.23.2.
See all versions of @one-source/mcp for other recorded verdicts.
- Review the evidence and your use of @one-source/mcp@5.23.2 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.