
Base Multi Wallet Mcp
io.github.lordbasilaiassistant-sudoPublished by GitHub account lordbasilaiassistant-sudov1.0.2Updated Oct 24, 2026
MCP server for AI agents to manage multiple wallets with coordinated trading and batch operations on
Overview
A local MCP server that lets an AI assistant manage multiple crypto wallets with coordinated trading and batch operations on Base.
- What you can do
- Manage multiple wallets together from one assistant session, per the registry description of coordinated wallet management on Base. Run coordinated trading actions across those wallets. Perform batch operations rather than acting on one wallet at a time. No individual tools are listed in the manifest, so the exact commands and their parameters are not documented here.
- When to use it
- Consider it when you want an assistant to operate several crypto wallets on Base at once, for example to run the same trading or batch action across accounts instead of repeating it wallet by wallet.
- Requirements
- Runs as a local process on the user's machine, installed from the npm package base-multi-wallet-mcp over stdio. Desktop only; not executable in a web context. No authentication, environment variables or headers are declared, but wallet credentials are presumably supplied some other way that the input does not describe.
Installation
In SourceWeft
- Open Base Multi Wallet Mcp 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.