bitbank-lab-mcp
OfficialRelated Servers
Alternatives to bitbank-lab-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceAn MCP server that enables AI clients to analyze cryptocurrency market data from bitbank API, providing technical indicators, order book analysis, and chart visualization.486 npmMIT

bitbank MCP Serverofficial
AlicenseAqualityBmaintenanceMCP server for bitbank cryptocurrency exchange enabling ticker, candlestick, order book, and transaction data retrieval.5244 npmMIT- AlicenseDqualityDmaintenanceA powerful cryptocurrency analysis MCP server that adds advanced technical analysis capabilities to the original Binance MCP implementation.151Apache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that delivers cryptocurrency sentiment analysis to AI agents.547MIT
- AlicenseAqualityBmaintenanceAn MCP server providing real-time market data, technical analysis, prediction market odds, and strategy backtesting for crypto, equities, and prediction markets.20MIT
- AlicenseAqualityDmaintenanceMCP server for crypto market analysis providing compact market-state briefs, patterns, support/resistance, trend, and indicators via tools like patternfetch_brief, patternfetch_delta, and patternfetch_analogs.412 npmMIT
TDQS
Scored across 33 tools
There is meaningful overlap among tools: prepare_chart_data vs get_candles, prepare_depth_data vs render_depth_svg, analyze_indicators vs the specialized snapshot tools, and detect_patterns vs analyze_candle_patterns. Descriptions usually clarify the intended use, but with 33 tools an agent still faces several plausible choices for the same task.
Names consistently follow a snake_case verb_noun pattern: get_*, analyze_*, detect_*, prepare_*, render_*, run_backtest, validate_candle_data. Minor deviations such as get_ticker vs get_tickers_jpy and analyze_mtf_sma vs analyze_sma_snapshot add slight inconsistency, but the overall convention is predictable and readable.
33 tools exceeds the 25+ threshold and creates a heavy tool menu for agents. The count is inflated by redundant pairs like prepare_chart_data/render_chart_svg and prepare_depth_data/render_depth_svg, plus many single-indicator snapshot tools that could be consolidated.
The domain is clearly read-only crypto market analysis, and the surface covers data retrieval, indicators, patterns, order book analysis, volume/flow analysis, visualization, and backtesting. Minor gaps exist such as no direct pairs/market-info fetch and no multi-pair candle batch endpoint, but they do not fatally block the server's apparent purpose.