Back to MCP Directory
Jupiter
Model Context Protocol high risk

Jupiter

Executes token swaps on Solana using Jupiter's Ultra API, combining DEX routing and RFQ for optimal pricing and execution, requiring private key access.

Connections & Capabilities

Connects To

GitHub

Capabilities

readwriteexec

Quickstart

Config

{
  "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"
      }
    }
  }
}

Exposed MCP Tools (2)

safe
get-ultra-order

Fetches 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.

critical
execute-ultra-order

Executes 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.

Safety Assessment

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.

  • Slippage control helps limit unexpected losses.
  • Ultra API aims for optimal pricing.
  • Clear separation of order fetching and execution.
  • Requires access to a Solana wallet's private key.
  • Executes transactions on the Solana blockchain, which carries financial risk.
  • Relies on external APIs (Jupiter Ultra) which could have vulnerabilities.
  • Potential for slippage if market conditions change rapidly.
  • No explicit input validation mentioned, increasing risk of unexpected behavior.