Basis Protocol
NPM · @BASIS-PROTOCOL/MCP-SERVER
Stablecoin risk scores, wallet risk profiles, and transaction risk assessment.
Available components
Last scanned (4 hours ago)
Scores higher than 49% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 212 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 552 tokens (~69/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@basis-protocol/mcp-server@1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_transaction_risk ~100
Composite risk assessment for a proposed stablecoin transaction — evaluates the asset, sender wallet, and receiver wallet. The core agent decision gate before executing any stablecoin transfer, swap, or deposit.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_symbol | string | yes | Symbol of the stablecoin being transferred (e.g. 'usdc', 'dai') |
| from_address | string | yes | Sender's Ethereum wallet address |
| to_address | string | yes | Receiver's Ethereum wallet address |
No output schema declared.
No examples provided.
get_methodology ~42
Returns the current SII formula, category weights, structural subweights, grade scale, data sources, and version information. Use for explaining scoring decisions and audit transparency.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_riskiest_wallets ~65
Wallets with the most capital at risk — lowest risk scores weighted by total value. Use for systemic risk monitoring and identifying wallets most impacted by a stablecoin failure.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of wallets to return (1–100, default 20) |
No output schema declared.
No examples provided.
get_scoring_backlog ~59
Unscored stablecoin assets ranked by total capital exposure across all indexed wallets. Shows which unscored assets represent the most risk.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of backlog items to return (1–100, default 20) |
No output schema declared.
No examples provided.
get_stablecoin_detail ~71
Full score breakdown for a specific stablecoin including category scores, structural subscores, and methodology version. Use to deep-dive into why an asset scored the way it did.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Stablecoin identifier (e.g. 'usdc', 'usdt', 'dai') |
No output schema declared.
No examples provided.
get_stablecoin_scores ~76
Get current SII scores for all scored stablecoins. Use before any decision involving stablecoins — portfolio assessment, swap routing, or collateral evaluation.
| Name | Type | Req | Description |
|---|---|---|---|
| min_grade | string | – | Optional minimum grade filter (e.g. 'B+' returns B+ and above) |
| sort_by | string | – | Sort order for results |
No output schema declared.
No examples provided.
get_wallet_holdings ~55
Detailed holdings breakdown for an Ethereum wallet with per-asset SII scores. Use to understand exactly what a wallet holds and identify unscored exposure.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum wallet address (0x-prefixed) |
No output schema declared.
No examples provided.
get_wallet_risk ~61
Get risk profile for a specific Ethereum wallet — composite risk score, concentration risk, coverage quality, dominant holdings. Use for counterparty due diligence before a transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum wallet address (0x-prefixed, 42 characters) |
No output schema declared.
No examples provided.
How do I install the Basis Protocol MCP server?
Basis Protocol runs locally as an npm package, launched with npx -y @basis-protocol/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @basis-protocol/mcp-server
claude mcp add shlok-lgtm-basis-mcp -- npx -y @basis-protocol/mcp-server
What is the Basis Protocol MCP server?
Basis Protocol is an MCP server listed in the public MCP registry as io.github.shlok-lgtm/basis-mcp. Stablecoin risk scores, wallet risk profiles, and transaction risk assessment. This page covers its npm package (@basis-protocol/mcp-server).
Is the Basis Protocol MCP server safe to use?
Basis Protocol scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Basis Protocol MCP server expose?
Basis Protocol exposes 8 tools: get_stablecoin_scores, get_stablecoin_detail, get_wallet_risk, get_wallet_holdings, get_riskiest_wallets, and 3 more. Their descriptions and schemas cost roughly 529 tokens of context every time the server is loaded.
Is the Basis Protocol MCP server still maintained?
Basis Protocol is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Basis Protocol MCP server under?
Basis Protocol declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.