QuantXData MCP Server
Related Servers
Alternatives to QuantXData MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for cryptocurrency trading across multiple exchanges (Bybit, Binance, KuCoin, etc.) with real-time price data, comparison, and natural language query support. Integrates with AI assistants via the Model Context Protocol.MIT
- AlicenseBqualityDmaintenanceMCP server that wraps the Theta Data API to provide AI assistants with real-time and historic stock, options, and index data, including OHLC, trades, quotes, Greeks, and more.591MIT

okx-trade-mcpofficial
AlicenseNot gradedqualityBmaintenanceMCP server connecting AI assistants to OKX exchange, enabling trading, market data, account management, and more via 150+ tools across 11 modules.423MIT- AlicenseAqualityCmaintenanceMCP server for accessing crypto market data (prices, portfolio analytics) from CoinGecko and performing RAG-based search over internal documents with responsible-AI guardrails.4MIT
- AlicenseAqualityDmaintenanceA comprehensive cryptocurrency market-data MCP server with 49 tools across six data sources, enabling LLMs to answer market questions via natural language.49MIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI clients to access live crypto market data and AI-driven quantitative analysis, with structured outputs and full observability.-
TDQS
Scored across 12 tools
Multiple tools overlap significantly: get_orderbooks, get_ob_l1_top, and get_ob_l2_snapshot all provide order book data, while get_ohlcv, get_histoday, get_histohour, and get_histominute all return OHLCV data at different intervals. get_trades and get_multi_trades also overlap, making it unclear which tool to select without reading detailed descriptions.
All tools use the get_ prefix, which is consistent, but the object naming is inconsistent: get_ohlcv versus get_histoday/hour/minute, get_orderbooks versus get_ob_l1_top, and get_trades versus get_multi_trades. The abbreviations (ob, l1, l2) and inconsistent use of 'multi_' create mixed conventions that are readable but not uniform.
With 12 tools, the count is within the typical well-scoped range for a market data server. However, several tools duplicate functionality (e.g., order book variants, OHLCV variants), which makes the count feel slightly inflated—a leaner set of 8-9 tools would be more appropriate.
The surface covers the major data types: instruments, trades, order books, OHLCV, options quotes, and real-time streaming. There are no obvious dead ends for historical or real-time market data, though the duplication of OHLCV and order book tools suggests the API is not optimally organized.