If you search for a Solana wallet MCP, you will not find one thing. You will find a stack: a signer, a data layer, a swap route, a policy layer and a risk check. Eight tracked listings on Sato Hub list Solana among their chains and cover those jobs. Some ship an MCP server, some are SDKs or standards you wrap yourself. The honest summary: the pieces exist, the glue is yours to build, and "Solana" on a listing means the chain is named, not that the tool is Solana-first.
A note on how to read this: every description below is what the project says about itself, as tracked on its Sato Hub page. The Sato Score is a transparency and liveness signal. It is not a safety, quality or returns grade, and nothing here is a claim that any of these tools performs well.
The signer: who holds the key
An agent that moves funds needs a key it can use and a human can bound. Three listings cover this layer.
- ▸Vultisig describes a seedless MPC wallet whose vaults are programmable through a TypeScript SDK, a CLI and an MCP server. Solana is among its listed chains. Sato Score 76 (High tier). No deploy spec on file.
- ▸Trust Wallet Agent Kit (TWAK) is described as a non-custodial toolkit (MCP server, CLI and SDK) that lets agents read and transact within user-defined rules. Sato Score 72. It has a deploy spec.
- ▸Open Wallet Standard (OWS) is a local-first standard with a CLI and SDK: an encrypted keystore, policy checks before signing, scoped tokens instead of raw keys. Sato Score 70. No deploy spec, and the listing describes a CLI/SDK rather than an MCP server.
The pattern worth noticing: two of the three lead with rules around signing, not just signing. If your agent can move funds, "trust me" is not a spending policy. Whichever you pick, read the policy model before the feature list.
The data layer: what the wallet holds
Zerion is a wallet and DeFi data provider with an agent-accessible API: portfolio, positions, transactions, PnL and prices across many chains, Solana included. Sato Score 85, the highest of the eight, and it has a deploy spec. The listing describes an API, so check whether you need to wrap it in an MCP tool yourself.
The swap route
1inch is a multichain DEX aggregator with a developer API suite and an official MCP server for agent swap execution. Solana is on its chain list. Sato Score 77, with a deploy spec. This is the one listing here whose description names an official MCP for execution.
The glue
- ▸Universal Crypto MCP is a plugin-based monorepo MCP covering EVM and Solana wallets, DEX aggregation, x402 payments, CEX trading, market data and bridges. One server, many surfaces. Breadth cuts both ways: more plugins means more code to read before you hand it a key. Sato Score 71, deploy spec on file.
- ▸Lucid Agents is a commerce SDK for agents that pay, sell and transact onchain, on Base, Ethereum and Solana. It is a framework, not a wallet. Sato Score 71.
The risk check
MistTrack MCP comes from SlowMist and exposes MistTrack address risk scoring and fund-flow tracing to agents over MCP. Solana is among its chains. Sato Score 70, deploy spec on file. For a wallet agent, a counterparty check before sending is the cheapest guardrail on this list.
What is still missing
Reading only these eight listings, a few gaps are visible. These are gaps in what the listings describe, not claims about what the projects can't do:
1. No Solana-specific story. Every descriptor leans multichain. Nothing here says what it does for Solana programs, token accounts or priority fees. Test that yourself. 2. One MCP, many owners. Vultisig, TWAK, 1inch, Universal Crypto MCP and MistTrack each ship their own MCP surface. Composing them into one agent means managing several servers and several permission models. 3. Policy lives in different places. OWS puts policy at the keystore, TWAK says user-defined rules, Vultisig leans on MPC. There is no shared way to express "spend at most X per day" across them. 4. Deploy specs are uneven. Vultisig and OWS, the two signer-focused listings with the strongest key-handling language, have no deploy spec on file.
How to build with it
A reasonable starting stack from this list: a signer with a policy layer (Vultisig, TWAK or OWS), a data source (Zerion), a swap route (1inch) and a counterparty check (MistTrack). Start with read-only calls, then add signing behind limits. The prompt is the cute part. The stack is where the work lives.
What to watch
Whether any of these listings adds Solana-specific tooling rather than a chain name on a list. Whether signer projects converge on a shared policy format. And whether the deploy-spec gaps close. We keep tracking all of it, and the scores move when the evidence does.
Want to wire this together? Describe the agent at satohub.ai/build and Sato maps the stack from the library of 458 tracked listings.