safe-solana-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALLOWLIST | No | Comma-separated list of recipient addresses allowed to receive transfers. If set, only these addresses may receive. | |
| ALLOW_MAINNET | No | Must be set to 'true' to allow running on mainnet-beta. | false |
| SOLANA_CLUSTER | No | The Solana cluster to connect to: devnet, testnet, or mainnet-beta. | devnet |
| SOLANA_RPC_URL | No | Custom RPC endpoint URL. If not set, uses the cluster default. | |
| MAX_SOL_PER_TRANSFER | No | Hard per-transfer cap, in SOL. | 1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_policyA | Returns the cluster and guardrails this server enforces: the per-transfer cap, the recipient allowlist, and whether mainnet is permitted. |
| get_balanceB | Read the SOL balance of an address. |
| get_accountA | Read an account's owner, lamports, executable flag, and data size. |
| recent_transactionsC | Return the most recent transaction signatures that touched an address. |
| prepare_transferA | Check a transfer against the safety policy, simulate it against the cluster, and (only if both pass) stage an unsigned transaction. Returns an actionId for execute_action. Nothing is signed or sent. |
| execute_actionA | Re-check policy for a previously prepared action, then return the unsigned transaction (base64) for you to sign and submit with your own wallet. This server never holds keys and never broadcasts. |
| icp_token_balanceA | Chain Fusion read: fetch an ICRC-1 token's symbol, decimals, and a principal's balance from an ICP ledger canister (for example ckBTC, ckETH, or ICP). Read-only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct operation: policy reading, balance checks, account details, transaction preparation/execution, and cross-chain token balance. No two tools overlap in purpose.
Most tools follow a verb_noun pattern (e.g., get_balance, prepare_transfer), but icp_token_balance slightly deviates by leading with a noun prefix. Overall naming is clear and predictable.
With 7 tools, the server is well-scoped for safe Solana operations. The count is neither too few to be useful nor too many to be confusing.
The server covers core functionalities: account queries, balance checks, policy verification, and a secure two-step transfer process. Missing direct send SOL tool, but that's intentionally handled via prepare_transfer/execute_action.