
Multi Wallet
io.github.lordbasilaiassistant-sudoPublished by GitHub account lordbasilaiassistant-sudov1.0.2Updated Oct 24, 2026
Multi-wallet management for AI agents — generate, distribute, consolidate on EVM
Overview
Lets an assistant manage multiple EVM crypto wallets: generate wallets, distribute ETH to them, and consolidate funds back.
- What you can do
- Multi Wallet is a local MCP server for managing many EVM wallets from an AI assistant. According to its description, it can generate wallets, distribute ETH across them, and consolidate balances back into one address. It runs as a local process over stdio and is intended for desktop use.
- When to use it
- Worth considering when an assistant needs to operate a set of EVM wallets, for example spreading funds across many addresses or sweeping them back together. It is not aimed at general blockchain data lookups or read-only queries.
- Requirements
- Runs locally as an npm package over stdio, so Node.js is needed. It uses the environment variables DEPLOYER_PRIVATE_KEY for write operations such as distributing ETH, RPC_URL for the chain endpoint (defaults to Base mainnet), THRYX_API_KEY for premium access, and WALLET_PASSWORD for encrypted wallet storage. Network access to an RPC endpoint is required.
Installation
In SourceWeft
- Open Multi Wallet in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.2LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.