Skip to main content
Glama
Aloysiusjs

tradingview-mcp

by Aloysiusjs

Related Servers

Alternatives to tradingview-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to retrieve TradingView market data, including historical OHLCV candles, quotes, technical indicators, and screener results over stdio or SSE.
      4
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides unified TradingView capabilities through one MCP server, including market data, screening, technical analysis, backtesting, sentiment, chart control via browser automation, Pine script transpilation and compilation, and alert webhooks.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Exposes TradingView data including quotes, technical ratings, historical OHLCV, and market screening through an MCP server using unofficial libraries.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to control a local TradingView Desktop instance, providing tools to read chart state, change symbols and timeframes, and fetch OHLCV data.
      117 npm
      133
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      An MCP server providing Model-usable tools to fetch real-time quotes, historical price charts, fundamental datasets, SEC filings, economic/earnings calendars, option chains, and corporate bond data from TradingView.
      21
      -
    • A
      license
      B
      quality
      C
      maintenance
      TradingView MCP server — real-time market data, technical indicators, screeners, and backtesting for Claude, ChatGPT, Cursor, Copilot, and any MCP client. Stocks, crypto, forex & futures across global exchanges.
      44
      1
      MIT

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool covers a clearly separate part of the market-data workflow: symbol resolution, live quotes, historical candles, technical indicators, and backend health. There is no meaningful overlap or ambiguity between them.

    Naming Consistency4/5

    All tools share the consistent 'tv_' prefix and lowercase snake_case style, making the naming predictable. tv_search_symbol is the only verb-led name while the rest are noun-resource names, a minor deviation.

    Tool Count5/5

    Five tools is well-scoped for a TradingView market-data server: each tool serves a distinct data need without redundancy. The count is neither too thin nor bloated.

    Completeness5/5

    The tool surface covers the full market-data lifecycle: find a symbol, fetch a live quote, retrieve historical candles, compute indicators, and verify backend health. There are no obvious dead ends or missing core operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues