Skip to main content
Glama
Aether-Grid

@sentimentracker/signals-mcp

by Aether-Grid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @sentimentracker/signals-mcp

No user-submitted related servers found.

    Related Servers

    • MetaTrader MCP Server

      felix-murcia
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to trade on MetaTrader 5 via REST API or MCP tools, supporting market/pending orders, position management, and account info retrieval.
      -

    • Enterprise Crypto MCP Gateway

      Jinzo03
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible AI clients to access live crypto market data and AI-driven quantitative analysis, with structured outputs and full observability.
      -

    • vanoe-intelligence-mcp

      vanoe-ai
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to query the Vanoe Market Intelligence API directly for stock verdicts, trend-stage analysis, Point & Figure signals, sector breadth, macro regime, SEC filings, and macro calendar data via MCP tools.
      10
      48 PyPI
      1
      MIT

    • tvsh

      notronel
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI models to pull live market data, including quotes, technical indicators, charts, and TradingView screeners, through MCP tools.
      1
      MIT

    • Data Puller MCP Server

      arisloth
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables fetching live crypto market data from Binance, Bybit, and Hyperliquid via MCP tools, including klines, orderbook, funding rates, technical indicators, and market breadth for real-time analysis by LLMs.
      -
    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

    A4.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool maps to a distinct operation: catalog discovery, single-indicator signal envelope, full per-bar payload, multi-indicator confluence, long-poll subscription, and order composition. The two get_indicator_* tools are clearly separated by payload intent, and get_signal_confluence is explicitly a parallel multi-indicator view.

    Naming Consistency5/5

    All tool names follow a clean snake_case verb_noun pattern: list_indicators, get_indicator_signal, get_indicator_full, get_signal_confluence, subscribe_signal, propose_trade_from_signal. The shared get_ prefix and logical object naming make the API predictable.

    Tool Count5/5

    Six tools is well-scoped for a signals MCP: discovery, light read, heavy read, aggregation, streaming, and downstream trade proposal. No tool feels redundant or missing from the core workflow.

    Completeness5/5

    The tool surface covers the full signal lifecycle: enumerate indicators, fetch current signals, retrieve full history, compare confluence, subscribe to changes, and convert signals into trade payloads. There are no obvious dead ends or critical missing operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources