GDEX Trading
Related Servers
Alternatives to GDEX Trading
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceHosted MCP server that gives AI agents direct access to GMX DeFi protocol endpoints via deterministic, auto-generated tools.-
- FlicenseAqualityBmaintenanceMCP server providing AI agents with native access to Jupiter's full DeFi stack on Solana. It offers 17 tools covering swaps, tokens, lending, limit orders, DCA, prediction markets, perpetuals, and portfolio management.16-
- AlicenseNot gradedqualityDmaintenanceMCP (Model Context Protocol) server for the MAIN DEX on Base. Provides AI agents (Claude, Cursor, etc.) with tools to interact with the protocol: swap tokens, manage liquidity, enter/exit ALM strategies(10% APY), and more.MIT
- 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 gradedqualityDmaintenanceAI-to-AI marketplace MCP server with 46 tools — swap 65+ crypto tokens on 7 chains, rent GPUs, trade 25 tokenized stocks, on-chain escrow (Solana + Base), DeFi yields, sentiment analysis, wallet monitoring, and image generation. Supports USDC payments across 14 blockchains.MIT
- AlicenseAqualityCmaintenanceMCP server for ThryxProtocol on Base, enabling AI agents to launch ERC-20 tokens, trade on bonding curves or Uniswap V4 pools, claim fees, and discover tokens through 21 native tools with gasless transactions.2125 npm2MIT
TDQS
Scored across 117 tools
117 tools contain many overlapping trading and account tools (e.g., open_perp_position/place_perp_order/execute_cross_perp/execute_isolated_perp; get_account_state/get_hl_clearinghouse_state/get_perp_positions; multiple auth and docs tools). While descriptions differentiate some, the sheer number of similar-purpose tools creates frequent ambiguity for an agent.
Uses snake_case but inconsistently mixes prefixes and verb patterns: get_ vs no get_, hl_ vs get_hl_, managed_ vs execute_ vs direct_, build_ vs generate_. Some names are noun-first (trending_list, hl_outcomes) while most are verb_noun, making predictable tool discovery harder.
117 tools is an extreme mismatch for any single MCP server; many tools cover niche or duplicate workflows. This exceeds the 50+ threshold and forces agents to sift through a sprawling surface.
The surface is broad, covering spot/perp trading, copy trading, bridge, wallet, auth, docs, social, and outcome markets. Most CRUD/lifecycle paths (create, update, cancel, list) exist, though some operations are only reachable via deletion flags or warning-laden tools.