io.github.lordbasilaiassistant-sudo/base-wallet-toolkit
NPM · BASE-WALLET-TOOLKIT-MCP
MCP server for Base wallet interactions: balances, gas, tokens, allowances, ENS.
Available components
Last scanned (20 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
- 32 of 102 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. 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 68 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 410 tokens (~58/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 −1
- Stability: pass → 0.93 functional
- 14 Nov 26 +1
- Stability: 0.97 → pass security
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −5
- Stability: pass → 0.67 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed npm/base-wallet-toolkit-mcp@1.0.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 102 packages
| Packages resolved | 102 |
|---|---|
| Stale | 32 |
| 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_allowance ~71
Check ERC-20 token allowance — how many tokens an owner has approved a spender to use. Useful before executing swaps or transfers that require approval.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | Token owner address |
| spender | string | yes | Approved spender address |
| token | string | yes | ERC-20 token contract address |
No output schema declared.
No examples provided.
check_balances ~69
Get ETH balance and ERC-20 token balances for any wallet address on Base. Provide token addresses to check specific token balances alongside ETH.
| Name | Type | Req | Description |
|---|---|---|---|
| tokens | array | – | Optional array of ERC-20 token addresses to check balances for |
| wallet | string | yes | Wallet address to check (0x...) |
No output schema declared.
No examples provided.
get_base_gas_price ~33
Get current Base chain gas price, priority fee, and block info. Use to determine optimal timing for transactions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_gas_estimate ~80
Estimate gas cost for a transaction on Base. Provide a to address and optional data/value to get precise gas estimates in ETH and USD-equivalent.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | – | Transaction calldata (hex string) |
| to | string | yes | Destination address |
| value | string | – | ETH value to send (e.g. '0.001') |
No output schema declared.
No examples provided.
get_token_info ~48
Get detailed ERC-20 token information on Base — name, symbol, decimals, total supply. Works with any ERC-20 token contract address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token contract address |
No output schema declared.
No examples provided.
get_tx_status ~50
Check the status of a transaction on Base by its hash. Returns confirmation status, block, gas used, and whether it succeeded or reverted.
| Name | Type | Req | Description |
|---|---|---|---|
| tx_hash | string | yes | Transaction hash (0x...) |
No output schema declared.
No examples provided.
resolve_address ~59
Resolve an ENS name to an Ethereum address, or look up the ENS name for an address. Uses Ethereum mainnet ENS registry.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | ENS name (e.g. 'vitalik.eth') or Ethereum address (0x...) |
No output schema declared.
No examples provided.
How do I install the io.github.lordbasilaiassistant-sudo/base-wallet-toolkit MCP server?
io.github.lordbasilaiassistant-sudo/base-wallet-toolkit runs locally as an npm package, launched with npx -y base-wallet-toolkit-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 · base-wallet-toolkit-mcp
claude mcp add lordbasilaiassistant-sudo-base-wallet-toolkit -- npx -y base-wallet-toolkit-mcp
What is the io.github.lordbasilaiassistant-sudo/base-wallet-toolkit MCP server?
io.github.lordbasilaiassistant-sudo/base-wallet-toolkit is an MCP server listed in the public MCP registry as io.github.lordbasilaiassistant-sudo/base-wallet-toolkit. MCP server for Base wallet interactions: balances, gas, tokens, allowances, ENS. This page covers its npm package (base-wallet-toolkit-mcp).
Is the io.github.lordbasilaiassistant-sudo/base-wallet-toolkit MCP server safe to use?
io.github.lordbasilaiassistant-sudo/base-wallet-toolkit scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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 io.github.lordbasilaiassistant-sudo/base-wallet-toolkit MCP server expose?
io.github.lordbasilaiassistant-sudo/base-wallet-toolkit exposes 7 tools: check_balances, get_gas_estimate, get_token_info, check_allowance, get_base_gas_price, and 2 more. Their descriptions and schemas cost roughly 410 tokens of context every time the server is loaded.
Is the io.github.lordbasilaiassistant-sudo/base-wallet-toolkit MCP server still maintained?
io.github.lordbasilaiassistant-sudo/base-wallet-toolkit is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.lordbasilaiassistant-sudo/base-wallet-toolkit MCP server under?
io.github.lordbasilaiassistant-sudo/base-wallet-toolkit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.lordbasilaiassistant-sudo/base-wallet-toolkit MCP server?
VerifyMCP ran 15 checks on io.github.lordbasilaiassistant-sudo/base-wallet-toolkit, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.lordbasilaiassistant-sudo/base-wallet-toolkit: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.