MAX Exchange MCP Server
Related Servers
Alternatives to MAX Exchange MCP Server
No user-submitted related servers found.
Related Servers
- 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.21MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact directly with the Binance cryptocurrency exchange for trading, portfolio management, market analysis, and strategy automation via natural language.62 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to trade on MetaTrader 5 using natural language, supporting account management, order placement, and real-time market data.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI tools to execute trades and fetch market data across six crypto exchanges via natural language or API, with dual Telegram and MCP interfaces.2-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to perform cryptocurrency trading analysis and execution with 38+ tools including real-time market data, technical indicators, risk management, and support for both paper trading and live execution on Hyperliquid.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural language trading operations through AI assistants, supporting stocks, options, crypto, portfolio management, and real-time market data.MIT
TDQS
Scored across 45 tools
Tools are generally well-distinguished by resource type and action (e.g., singular vs. plural, spot vs. M-wallet prefixes). Minor potential confusion exists between get_order and get_open_orders/get_closed_orders, but parameter differences (ID lookup vs. state filtering) clarify intent.
Excellent snake_case consistency with clear verb_noun patterns (get_*, submit_*, cancel_*). All margin wallet tools use the m_ prefix predictably. Minor deduction for get_k being cryptic (should be get_klines or get_candles) and get_m_ad_ratio using unexplained abbreviation.
With 45 tools, the surface far exceeds the rubric's 25+ threshold for 'too many.' The count is inflated by numerous singular/plural pairs (get_order/get_orders, get_deposit/get_deposits) that could have been consolidated with optional parameters, creating unnecessary bloat for an agent to navigate.
Extremely comprehensive coverage of exchange operations including spot trading, margin (M-wallet) lifecycle, deposits/withdrawals, and market data. Minor gaps exist (e.g., no submit_internal_transfer to match get_internal_transfers, no cancel_withdrawal), but core workflows are fully supported.