multichain-mcp
NPM · @WKALIDEV/MULTICHAIN-MCP
MCP server for AI agents — Stacks, Celo, and Base in one npm package.
Available components
Last scanned (2 hours ago)
Scores higher than 40% 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
- 33 of 127 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 125 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 387 tokens (~77/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "prepare_transfer" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −6
- Stability: pass → 0.60 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +42
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
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/@wkalidev/multichain-mcp@1.2.1
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 127 packages
| Packages resolved | 127 |
|---|---|
| Stale | 33 |
| 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 →
deploy_token ~115
Prepare an unsigned ERC-20 token deployment transaction on Celo or Base (requires Team — you're on Free)
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | EVM chain to deploy on |
| decimals | integer | – | – |
| name | string | yes | Token name (e.g. 'My Token') |
| ownerAddress | string | yes | Address that will receive the initial supply |
| symbol | string | yes | Token symbol (e.g. 'MTK') |
| totalSupply | string | yes | Total supply (e.g. '1000000') |
No output schema declared.
No examples provided.
get_balance ~56
Get native and token balances for a wallet on Celo, Base, or Stacks
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address (EVM 0x... or Stacks SP/ST...) |
| chain | string | yes | Target blockchain |
No output schema declared.
No examples provided.
get_portfolio ~44
Aggregate wallet balances across Celo, Base, and Stacks in one call (requires Pro — you're on Free)
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | object | yes | Your wallet addresses per chain |
No output schema declared.
No examples provided.
get_prices ~68
Get real-time token prices and 24h change for STX, CELO, ETH, and more
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Quote currency (default: usd) |
| symbols | array | yes | Token symbols to fetch (e.g. ['STX', 'CELO', 'ETH']) |
No output schema declared.
No examples provided.
prepare_transfer ~104
Build an unsigned transaction to transfer native tokens or ERC-20/SIP-010 tokens on any supported chain (requires Pro — you're on Free)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount as a string (e.g. '1.5') |
| chain | string | yes | – |
| from | string | yes | Sender address |
| to | string | yes | Recipient address |
| tokenAddress | string | – | ERC-20/SIP-010 contract address. Omit for native transfer. |
No output schema declared.
No examples provided.
How do I install the multichain-mcp server?
multichain-mcp runs locally as an npm package, launched with npx -y @wkalidev/multichain-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @wkalidev/multichain-mcp
claude mcp add wkalidev-multichain-mcp -- npx -y @wkalidev/multichain-mcp
What is the multichain-mcp server?
multichain-mcp is listed in the public MCP registry as io.github.wkalidev/multichain-mcp. MCP server for AI agents, Stacks, Celo, and Base in one npm package. This page covers its npm package (@wkalidev/multichain-mcp).
Is the multichain-mcp server safe to use?
multichain-mcp scores 71 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 multichain-mcp server expose?
multichain-mcp exposes 5 tools: get_balance, get_prices, get_portfolio, prepare_transfer, deploy_token. Their descriptions and schemas cost roughly 387 tokens of context every time the server is loaded.
Is the multichain-mcp server still maintained?
multichain-mcp 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 multichain-mcp server under?
multichain-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.