Futures MCP
Related Servers
Alternatives to Futures MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables Claude to control and read from the TradingView Desktop app, providing automated morning briefs, chart analysis, Pine Script development, and replay mode.-
- FlicenseNot gradedqualityBmaintenanceEnables Claude to pull multi-timeframe Binance kline data, compute Wyckoff/VSA/GANN context, manage trading rules and journals, and optionally reconcile real positions, fills, and PnL from read-only Binance, Bybit, or OKX accounts.1-
- FlicenseNot gradedqualityDmaintenanceExposes TradingView technical indicators and OHLCV data through MCP tools for Claude Desktop or any MCP-aware client.26-

AlgoLift MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI assistants to look up futures prop firm rules with each rule's verification status and cited source, run 217 tested technical indicators and candlestick patterns, and compute Setup Odds for intraday setups on the user's own bars, all through read-only tools that need no account or API key.101123 npmMIT- AlicenseBqualityBmaintenanceEnables Claude to read and annotate the chart open in a locally running TradingView Desktop, including quotes, candles, drawings, screenshots, and price alerts.21MIT
- AlicenseAqualityBmaintenanceEnables Claude to read Hyperliquid perpetual markets and account state, and to place bracketed orders that carry an exact stop and target, sized from a 3x/1% risk profile by default. It also serves oil and metals desk briefs, staying read-only until an API wallet key is supplied and asking for confirmation before every live-money call.283036MIT
TDQS
Scored across 4 tools
Each tool has a clear primary purpose: retrieving bar data, performing range analysis, and capturing chart images. The only potential confusion is between capture_chart and get_range_chart, but the descriptions make clear that one is a raw screenshot while the other includes the detected range and report.
All tool names follow a consistent verb_noun pattern: get_futures_bars, analyze_range, capture_chart, get_range_chart. The naming style is uniform and predictable, with no mixing of conventions.
Four tools is somewhat lean, but appropriate for a focused futures charting and range-analysis workflow. Each tool fills a distinct step in the process, and the small count keeps the server manageable.
The server covers the core workflow of retrieving bars, detecting a range, and viewing charts. Minor gaps exist, such as no obvious tool for listing available futures instruments or configuring window parameters, but these do not severely block the intended use case.