Loading...
Executes token swaps on Solana using Jupiter's Ultra API, combining DEX routing and RFQ for optimal pricing and execution, requiring private key access.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
Executes token swaps on Solana using Jupiter's Ultra API, combining DEX routing and RFQ for optimal pricing and execution, requiring private key access.
This server allows for automated token swaps on Solana, which is inherently risky due to the potential for financial loss. The need for a private key makes securing the server paramount. It is safe to use only with thorough understanding of the risks and careful management of the private key.
Performance depends on the Solana network and Jupiter's Ultra API. High network congestion can lead to slower execution times and increased slippage.
Cost includes Solana transaction fees, which vary depending on network congestion. Jupiter's Ultra API may have usage limits or fees in the future.
{
"mcpServers": {
"Jupiter-MCP": {
"command": "node",
"args": ["path/to/jupiter-mcp/server/index.js"],
"env": {
"SOLANA_RPC_URL": "solana rpc url you can access",
"PRIVATE_KEY": "your private key"
}
}
}
}get-ultra-orderFetches a swap order from Jupiter's Ultra API, finding the best price via DEX and RFQ.
Read-only operation that retrieves swap order details without executing any transactions.
execute-ultra-orderExecutes a pre-approved swap transaction on the Solana blockchain via Jupiter's Ultra API.
Signs and submits transactions, potentially leading to financial loss if used improperly or maliciously.
Environment Variable
This server allows for automated token swaps on Solana, which is inherently risky due to the potential for financial loss. The need for a private key makes securing the server paramount. It is safe to use only with thorough understanding of the risks and careful management of the private key.
Full autonomy allows the agent to execute trades without human intervention, increasing risk. No sandboxing or rollback mechanisms are present, requiring careful configuration and monitoring.
Production Tip
Implement robust monitoring and alerting to detect unexpected trades or errors.
Node.js version 18 or higher is required due to the use of native `fetch`.
Store your private key securely, ideally using a hardware wallet or a secrets management solution. Avoid storing it directly in code or configuration files.
Slippage is the difference between the expected price and the actual price of a trade. Setting a higher slippage tolerance increases the chance of a successful trade but may result in a less favorable price.
The `execute-ultra-order` tool returns a status indicating success or failure. Check the Solana explorer using the transaction ID for more details.
Monitor the server's logs and track transaction execution times using the Solana explorer. Implement alerting for failed transactions or unexpected behavior.
Refer to Jupiter's official documentation for information on rate limits and usage policies.
The current configuration only supports a single wallet defined by the `PRIVATE_KEY` environment variable. You would need to modify the code to support multiple wallets.