buda-mcp
Related Servers
Alternatives to buda-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceProvides live cryptocurrency market data including spot prices, OHLCV candles, order books, funding rates, and technical indicators via public exchange APIs.8MIT
- AlicenseAqualityCmaintenanceLive market data for AI agents. 8 tools: real-time crypto prices, OHLCV candles, order books, market cap rankings, trending coins, technical analysis (RSI/SMA/z-score), asset comparison, and Fear & Greed index. Zero API keys, zero dependencies.81MIT
- FlicenseNot gradedqualityNot gradedmaintenanceProvides real-time and historical cryptocurrency market data using ccxt, with tools for ticker, OHLCV, and streaming updates.-
- -licenseNot gradedqualityNot gradedmaintenanceReal-time financial market data MCP server. Stocks, crypto, technicals, sentiment, FDA calendar. No API keys required.-
- AlicenseAqualityCmaintenanceReal-time institutional crypto & equity orderflow intelligence. Detects BUY/SELL pressure from live Binance L2 orderbook and aggressive trade feeds for any USDT pair or US equity.102MIT
- FlicenseNot gradedqualityDmaintenanceProvides real-time and historical cryptocurrency market data from 100+ exchanges including prices, OHLCV data, market statistics, and order books through the CCXT library with intelligent caching.-
TDQS
Scored across 17 tools
Most tools have clearly distinct purposes (trades, volume, spread, summary, indicators, etc.), but specify_market functions like get_ticker, get_market_summary, and get_market_volume have overlapping market snapshot data. However, descriptions differentiate them well (summary is one-call, volume focuses on volume, ticker is a snapshot).
Tools follow a consistent verb_noun pattern with 'get_' prefix, e.g., get_trades, get_spread, get_markets. Minor deviations include calculate_position_size, simulate_order, and compare_markets, which use different verbs but are still readable and fit the domain.
17 tools is slightly above the ideal 3-15 but still well-scoped for a comprehensive market data server. Each tool serves a specific market data or analysis function, and there are no redundant tools (though simulate_order is deprecated, it is still useful for backward compatibility).
The tool surface covers a broad range of market data needs: market overview, order book, trades, history, technical indicators, sentiment, quotation, and stablecoin liquidity. Minor gaps include lack of direct order placement (but that is out of scope for a read-only server) and no explicit tool for order book depth beyond get_orderbook, but the main analytics are well covered.