jupiter-mcp
Related Servers
Alternatives to jupiter-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn MCP server that enables AI agents to interact with the Solana blockchain through 20 tools for wallet management, SPL token operations, blockchain exploration, and DeFi integration via Jupiter.21MIT
- FlicenseNot gradedqualityDmaintenanceAgent-ready MCP server providing access to Jupiter's DeFi API, with tools mapped 1:1 to real endpoints for crypto operations. Hosted free, no auth required.-
- AlicenseAqualityDmaintenanceMCP server giving AI agents access to Solana blockchain data. 7 tools: wallet balances, transaction history, token prices (Jupiter + CoinGecko), token metadata, DeFi yields (Raydium + Orca), and token safety checks (RugCheck scores, holder concentration, insider detection).81MIT
- FlicenseNot gradedqualityDmaintenanceA comprehensive MCP server providing unified access to over 144 tools for lending, trading, and staking across six major DeFi protocols on the Stacks Bitcoin Layer 2. It enables AI agents to perform complex blockchain operations and interact with the DeFi ecosystem using natural language commands.3-
- AlicenseNot gradedqualityFmaintenanceAn MCP server for the Sui blockchain that enables AI agents to manage accounts, execute token swaps, and perform smart contract development using the Sui CLI. It supports over 30 tools for DeFi operations, staking, and market data via Pyth price oracles.11 npm2MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents real-time access to DeFi across multiple chains, enabling non-custodial crypto trading, portfolio queries, and transaction execution.07MIT
TDQS
Scored across 16 tools
Each tool targets a distinct Jupiter subdomain/action: swap quote vs build, token search vs info vs price, and read/transaction tools are clearly separated. The only close pair is token_search and token_info, but exact-mint detail vs search-by-query is explicit enough to avoid misselection.
All tools share the jupiter_<domain>_<action|resource> pattern with consistent snake_case and plural lists for collection queries. Small structural differences like token_info vs limit_order_create follow the resource shape rather than being arbitrary.
16 tools is at the upper edge but each is justified by the breadth of Jupiter's products: swap, tokens, lending, limit orders, DCA, prediction markets, perps, and portfolio. No redundant tools exist; each domain has a focused read/action pair.
The swap, token, lending, and limit-order surfaces are fairly complete, but DCA has no cancel/close tool and perps only exposes markets/positions with no order creation or closing. Prediction events are also list-only, leaving a few lifecycle dead ends for agents.