Paradex MCP Server
Related Servers
Alternatives to Paradex MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityNot gradedmaintenanceA bridge between AI assistants and the Paradex perpetual futures trading platform that enables retrieving market data, managing trading accounts, placing orders, and monitoring positions.26MIT
- AlicenseAqualityFmaintenanceA Model Context Protocol server implementation that enables AI assistants to interact with the Paradex perpetual futures trading platform, allowing for retrieving market data, managing trading accounts, placing orders, and monitoring positions.169MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access real-time cryptocurrency market data, manage accounts, execute trades, track portfolios, and perform wallet and risk-management operations through the Model Context Protocol.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to discover and analyze prediction markets, execute trades, and manage positions on Polymarket via the Model Context Protocol.786 npm22MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to securely trade on Hyperliquid perpetual exchange, including order placement, position management, market data retrieval, and vault operations via natural language.29 PyPI24MIT
- AlicenseBqualityCmaintenanceProvides Binance futures market data, trading capabilities, and technical indicators to AI assistants through the Model Context Protocol.5766 npm1MIT
TDQS
Scored across 33 tools
All 33 tools have clearly distinct purposes. Account, market, order, system, and vault tools each target specific resources and actions without overlap. For example, account_balance vs account_fills vs account_positions are well-separated, and market tools like bbo, orderbook, klines, and market_summaries each provide different granularity of data.
Tools follow a consistent pattern: 'paradex_' prefix followed by snake_case area and action (e.g., paradex_account_balance, paradex_cancel_orders). Abbreviations like 'bbo' and 'klines' are standard in trading and do not break the pattern. The naming is predictable and clear.
With 33 tools, the count is above the typical well-scoped range of 3–15 and falls into the borderline/heavy category (16–25 is borderline; above 25 is considered too many per calibration). However, each tool serves a distinct purpose for a comprehensive trading platform, so while high, it is not excessive for the domain.
The tool surface covers core trading operations (account, orders, market data), vault management, and system status. Minor gaps exist: no dedicated deposit/withdrawal tool, no order amendment, and no API token management beyond listing. These are non-critical but prevent a perfect score.