All servers / Web3 / Phantom MCP server
Phantom MCP server
MCP Server for Phantom Wallet
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-18 on package version 1.2.10. Package: @phantom/mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 16 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 16 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (29.1 seconds including download)
- Tools offered: 30
- Last published: 2026-11-17
- Weekly downloads (npm): 17,229
- License: none listed · Direct dependencies: 1
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
buy18 of 18 parameters describedPhantom Wallet — Fetches an optimized swap quote from Phantom's routing engine and can optionally execute it. Supports same-chain Solana swaps, same-chain EVM swaps (Ethereum, Base, Polygon, Monad), and cross-chain swaps between Solana and EVM chains. Arbitrum (eip155:42161) is not supported as a sell or buy chain. Cross-chain flows work in both directions, including EVM to Solana and Solana to EVM, and can also target Hypercore/Hyperliquid when supported. Both sellChainId and buyChainId must be a Solana chain (solana:*), EVM chain (eip155:*), or Hypercore/Hyperliquid (hypercore:*); other namespaces are not supported. Use this for ALL swap/exchange operations (e.g. 'swap USDC to SOL', 'buy ETH on Base', 'bridge SOL to ETH'). Use sellChainId to specify the source chain and buyChainId for the destination (omit both for Solana, same as before). For native tokens (SOL, ETH, MATIC) always use sellTokenIsNative/buyTokenIsNative — never use magic addresses like 0xeeee...eeee. EVM token contract addresses must be lowercase (e.g. "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"). Two modes: (1) execute: false (default) — returns quote only; (2) execute: true — signs and broadcasts immediately. For cross-chain swaps, execute: true sends the sell-side initiation transaction right away — the bridge completes the buy side automatically. IMPORTANT: The wallet must hold native tokens for fees on the source chain (SOL for Solana, ETH/native for EVM). Use get_token_balances to verify balances before executing. Success response (execute: false): {quoteRequest, quoteResponse}. Success response (execute: true): {quoteRequest, quoteResponse, execution: {signature, rawTransaction}}.
evm_allowance6 of 6 parameters describedReturns the ERC-20 token allowance granted by an owner address to a spender address on a supported EVM chain. Use this before a swap to check whether an approval transaction is needed. If ownerAddress is omitted, the authenticated wallet address for the chain is used.
evm_send14 of 14 parameters describedSigns and broadcasts an EVM transaction using the authenticated embedded wallet. Accepts the standard EVM transaction object format (the same fields used by eth_sendTransaction and returned by DeFi aggregators). Use the chainId field directly from the aggregator response (e.g. 1 for Ethereum mainnet, 8453 for Base, 137 for Polygon). Missing fields such as nonce and gas are automatically fetched from the network. SAFETY: By default (no confirmed flag), this tool runs a simulation and returns expected asset changes and warnings WITHOUT sending anything — use this to show the user what will happen and ask for approval. Pass confirmed: true only after the user explicitly approves the preview to actually sign and send. Arbitrum (chainId 42161) is not supported and is rejected. If the user wants to skip simulation and execute immediately, pass confirmed: true directly — but the two-step flow is recommended for safety. Response WITHOUT confirmed: {status: 'pending_confirmation', simulation: {expectedChanges, warnings, block?, advancedDetails?} | null}. Response WITH confirmed: true: {hash, networkId, from, to}.
evm_sign4 of 4 parameters describedSigns a UTF-8 message using EIP-191 personal_sign with the authenticated EVM embedded wallet. Use this for authentication challenges, proof-of-ownership flows, or any off-chain EVM signature request. Returns a hex-encoded signature. Use the chainId number directly (e.g. 1 for Ethereum, 8453 for Base, 137 for Polygon, 42161 for Arbitrum, 143 for Monad). For Solana message signing use sign_solana_message instead. Success response: {signature: string}.
evm_sign-typed4 of 4 parameters describedSigns EIP-712 typed structured data using the authenticated EVM embedded wallet. Returns a hex-encoded signature. Used for DeFi permit signatures, order signing (e.g. 0x, Seaport), and other structured off-chain approvals. The typedData parameter must follow the EIP-712 structure with types, primaryType, domain, and message fields. Use the chainId number directly (e.g. 1 for Ethereum, 8453 for Base, 137 for Polygon, 42161 for Arbitrum, 143 for Monad).
login1 of 1 parameter describedRe-authenticate with Phantom. Use this to log in for the first time, switch accounts, or refresh an expired session. Text mode (device-code auth flow) does not open a browser: it clears the current session and immediately returns { status: 'pending', prompt } with the approval URL and code. Show the prompt to the user. Approval is awaited in the background; call again with displayMode 'text' to check, which returns { status: 'authenticated', walletId, organizationId } once approved. A denied or expired attempt is reported once and the next call starts a new one. To switch accounts after a completed text login, log out first.
logoutno parametersPhantom Wallet — Log out by clearing the stored session and credentials from disk. Does not require an active session. The next tool call will require re-authentication.
pay3 of 3 parameters describedPhantom Wallet — Pays for daily API access by signing and broadcasting the CASH token transfer transaction included in an PaymentRequiredError error response. Call this when any tool returns error code PaymentRequiredError, passing the preparedTx from that response. On success, the payment signature is stored and API calls are unlocked until the purchased quota is consumed. After calling this, retry the original tool that triggered the payment requirement.
perps_account2 of 2 parameters describedReturns the perpetuals account balance including total account value, available balance, and withdrawable amount. The account is on Hyperliquid (funded with USDC).
perps_cancel4 of 4 parameters describedCancels an open perpetual order on Hyperliquid. Use get_perp_orders to retrieve the order ID before cancelling.
perps_close4 of 4 parameters describedCloses an open perpetual position on Hyperliquid. By default closes 100% of the position. Use sizePercent to partially close (e.g. 50 to close half). Uses a market IOC order with 10% slippage buffer.
perps_deposit8 of 8 parameters describedBridges tokens from an external chain (Solana, Base, Ethereum, Polygon) into Hyperliquid as USDC via a cross-chain swap. By default sells USDC on the source chain (or native SOL if sellTokenIsNative: true). The bridge delivers USDC directly to your Hyperliquid perps account. Arbitrum is not supported as a source chain. Use execute: false (default) to preview the quote first.
perps_history2 of 2 parameters describedReturns historical perpetual trades for the wallet. Each entry includes trade ID, coin, type (open/close/liquidation), timestamp, price, size, trade value, fee, and closed PnL.
perps_leverage5 of 5 parameters describedUpdates the leverage and margin type (cross or isolated) for a perpetual market. This takes effect for new orders on that market. Cross margin shares account balance across positions; isolated margin limits risk to the margin allocated to that position.
perps_markets1 of 1 parameter describedReturns all available perpetual markets on Hyperliquid with current prices, funding rates, open interest, 24h volume, max leverage, and asset IDs. Use this to discover tradeable markets and get current prices before opening positions.
perps_open10 of 10 parameters describedOpens a perpetual position on Hyperliquid. Supports market and limit orders in either long or short direction. The position size is specified in USD. For market orders, a 10% slippage buffer is applied automatically. Use get_perp_markets first to verify the market symbol and current price. Requires the wallet to have USDC deposited in the perps account (use deposit_to_perps if needed).
perps_orders2 of 2 parameters describedReturns all open perpetual orders (limit orders, take-profit, stop-loss) for the wallet. Each order includes ID, coin, side, type, limit/trigger price, size, and whether it is reduce-only.
perps_positions2 of 2 parameters describedReturns all open perpetual positions for the wallet. Each position includes coin, direction (long/short), size, margin, entry price, leverage, unrealized PnL, and liquidation price.
perps_transfer3 of 3 parameters describedMoves USDC from the Hyperliquid spot account into the perpetuals account. Both accounts live on Hypercore (Hyperliquid's own chain) — this is an internal transfer, not a cross-chain bridge. IMPORTANT: This only works if USDC is already in your Hyperliquid spot account. If your USDC is on Solana, Ethereum, Base, or Arbitrum you need to bridge it to Hyperliquid first (the Phantom app handles this via the dedicated Hyperliquid deposit flow). Use get_perp_account to verify the perp balance after transferring.
perps_withdraw5 of 5 parameters describedBridges USDC from the Hyperliquid perpetuals account to an external chain (Solana, Base, Ethereum, Arbitrum, Polygon) via the Relay bridge. By default receives USDC on the destination chain; pass buyToken to receive a different asset. Use get_perp_account to check the available balance before withdrawing.
perps_withdraw-hl-spot6 of 6 parameters describedBridges USDC from the Hyperliquid spot wallet to an external chain (Solana, Base, Ethereum, Arbitrum, Polygon) via the Relay bridge. Funds must be in the Hyperliquid spot account — use withdraw_from_perps first if they are in the perp account. By default receives USDC on the destination chain; pass buyToken to receive a different asset. Use execute: false (default) to preview the quote first.
price3 of 3 parameters describedPhantom Wallet — Fetches the current price of a specific token by its address and chain. Pass address='native' for the chain's native token (SOL, ETH, MATIC, etc.). For any other token, pass its mint address (Solana) or contract address (EVM). Returns price in USD (or the requested currency if supported) with 24h change and market cap. Response: {name, symbol, caip19, price, priceChange24h, currency, lastUpdatedAt?, marketCap}.
simulate9 of 9 parameters describedPhantom Wallet — Simulates a transaction and returns expected asset changes, security warnings, and blocking conditions — without submitting it on-chain. Use this to preview what a transaction will do before signing or sending. Supports Solana, EVM (Ethereum, Base, Polygon, Arbitrum, Monad), Sui, and Bitcoin. Built on top of Phantom's transaction simulation service. The `userAccount` wallet address is auto-derived from the authenticated session for Solana and EVM chains; supply it explicitly for Sui and Bitcoin. Chain-specific `params` shapes: Solana transaction — { transactions: ['<base58>'], method: '<signing method>', simulatorConfig?: { decodeAccounts?, decodeInstructions? } }; Solana method is required and must match the intended signing operation, for example signTransaction, signAllTransactions, signAndSendTransaction, or signAndSendAllTransactions. No signing method is inferred. EVM transaction — { transactions: [{ from, to, value, data, chainId, type }] }; Sui transaction — { rawTransaction: '<bytes>' }; Bitcoin transaction — { transaction: '<raw>', userAddresses: ['bc1q...'] }; EVM or Solana message signing — { message: '<message>' }. Response: { type, expectedChanges: [{ type, changeSign: PLUS|MINUS|EQUAL, changeText, asset: { type, amount, decimals, symbol, usdValue } }], warnings: [{ message, severity: 1-5 }], block?: { message, severity }, advancedDetails?: { chainId, totalFee, feePayers, gas, contractAddresses } }.
solana_send5 of 5 parameters describedSigns and broadcasts a Solana transaction using the authenticated embedded wallet. Accepts a standard base64-encoded serialized transaction (the format returned by Solana DeFi APIs such as Jupiter, Phantom swap, and others). SAFETY: By default (no confirmed flag), this tool runs a simulation and returns expected asset changes and warnings WITHOUT sending anything — use this to show the user what will happen and ask for approval. Pass confirmed: true only after the user explicitly approves the preview to actually sign and send. If the user wants to skip simulation and execute immediately, pass confirmed: true directly — but the two-step flow is recommended for safety. Response WITHOUT confirmed: {status: 'pending_confirmation', simulation: {expectedChanges, warnings, block?, advancedDetails?} | null}. Response WITH confirmed: true: {signature, networkId, account}.
solana_sign4 of 4 parameters describedSigns a UTF-8 message using the authenticated Solana embedded wallet. Returns a base58-encoded signature. Use this for off-chain signature proofs, authentication challenges, and message attestation on Solana.
transfer10 of 10 parameters describedTransfers native tokens or fungible tokens on Solana and EVM chains. Use this for direct token sends (e.g. 'send 1 SOL to X', 'send 0.01 ETH to Y', 'transfer 100 USDC on Base'). For swaps/exchanges (e.g. 'swap USDC for SOL'), use buy_token instead. Solana: supports SOL and SPL tokens. EVM: supports native tokens (ETH, MATIC, etc.) and ERC-20 tokens. Arbitrum is not supported: transfers on eip155:42161 are rejected. IMPORTANT: The sending wallet must hold enough native token for fees (SOL on Solana, ETH/native on EVM). For ERC-20 transfers, provide decimals when using amountUnit: 'ui'. TWO-STEP FLOW — always call this tool twice: (1) First call WITHOUT confirmed (or confirmed: false): builds the transaction, runs a simulation, and returns the preview showing expected asset changes, warnings, and any blocking conditions. Present these results to the user and ask 'Does this look correct? Shall I proceed with the transfer?' If the simulation is blocked (block field is set), inform the user and do NOT proceed. (2) Second call WITH confirmed: true (only after explicit user approval): builds and submits the transaction. Response WITHOUT confirmed: {simulation: {expectedChanges, warnings, block?, advancedDetails?}, status: 'pending_confirmation'}. Response WITH confirmed: true: {walletId, networkId, from, to, tokenMint: string|null, signature: string|null, rawTransaction: string}.
wallet_addresses1 of 1 parameter describedReturns all blockchain addresses (Solana, Ethereum, Bitcoin, Sui) for the authenticated Phantom embedded wallet. Call this first to confirm the user is connected and to get their wallet addresses before any transfer or swap. Response format: {walletId: string, organizationId: string, addresses: [{addressType: string, address: string}]} where addressType is one of 'solana', 'ethereum', 'bitcoin', 'sui'. Use the Solana address with send_solana_transaction, sign_solana_message, and transfer_tokens; use the Ethereum address with send_evm_transaction, sign_evm_personal_message, and sign_evm_typed_data. If this returns an auth error (session expired or revoked), call phantom_login to re-authenticate.
wallet_balances1 of 1 parameter describedPhantom Wallet — Returns fungible token balances across all supported chains (Solana, Ethereum, Base, Polygon, Arbitrum, Bitcoin, Sui) with live USD prices and 24h price change. Use the `networks` parameter to filter by chain — omit it to fetch all chains at once. Examples: pass ["base"] when user asks about Base tokens; ["solana"] for Solana only; omit for all. Use this to check if the user has enough funds before a transfer or swap. This does not include Hyperliquid perpetuals account balances; if the user asks for Hyperliquid/perps funds or total exposure, also call get_perp_account. Response: {items: [{name, symbol, decimals, caip19, totalQuantity, totalQuantityString, spamStatus, logoUri, price?: {price, priceChange24h}, queriedWalletBalances: [{address, quantity, quantityString}]}]}. Key fields: totalQuantity = human-readable balance (e.g. 1.5 for 1.5 SOL), totalQuantityString = raw base units (e.g. '1500000000' lamports), price.price = current USD price per token, caip19 = token identifier (parse after '/token:' to get the Solana mint address; SOL is 'slip44:501'). Non-spam tokens have spamStatus 'VERIFIED'. Filter out spamStatus 'SPAM' tokens for cleaner output.
wallet_rebalance7 of 7 parameters describedPhantom Wallet — Analyzes your portfolio allocation and rebalances it to target percentages via token swaps. Two-phase flow: (1) Call with phase 'analyze' to see current token balances, USD values, and allocation percentages. (2) After the user specifies desired target percentages, call with phase 'execute' and targetAllocations to compute and perform the swaps. Use dryRun: true in the execute phase to preview the swap plan without executing. Currently supports Solana network only. Percentages in targetAllocations must sum to 100. The tool uses direct token-to-token swaps via Phantom's routing engine for optimal execution.
wallet_statusno parametersReturns locally stored Phantom wallet session metadata without authentication or network requests. Connected means a local session exists, not that the server has validated it. Response when connected: {connected: true, walletId: string, organizationId: string, mcpServerVersion: string}. Response when not connected: {connected: false, reason: string, mcpServerVersion: string}. Use login to authenticate when no local session exists.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.