Skip to main content
Glama
usamahassan965

Futures MCP

by usamahassan965
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Futures MCP

No user-submitted related servers found.

    Related Servers

    • TradingView MCP Jackson

      BluePandaNYC
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to control and read from the TradingView Desktop app, providing automated morning briefs, chart analysis, Pine Script development, and replay mode.
      80 npm
      -

    • BAMCP

      tan-mai
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      -

    • TradingView MCP Jackson

      kylepk-boop
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to control TradingView Desktop for automated morning briefs, chart analysis, Pine Script development, and session management via MCP tools.
      80 npm
      -

    • tradingview-mcp

      Miha21222
      A
      license
      A
      quality
      A
      maintenance
      Provides AI agents with a TradingView-centric toolkit for screener queries, historical FX data, pattern scanning, chart rendering, backtesting, Pine tooling, and optional account/desktop integration.
      6
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources