Skip to main content
Glama
Ax3lsk3r3

QuantVibe

by Ax3lsk3r3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to QuantVibe

No user-submitted related servers found.

    Related Servers

    • diyan-research-mcp

      mikeli20221102-ux
      A
      license
      B
      quality
      B
      maintenance
      Read-only MCP server that provides enterprise research frameworks, frozen snapshots, and historical factor summaries with sources and falsification conditions, without trading advice.
      6
      1
      MIT

    • etfedge-mcp

      a7351220
      F
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server for Taiwan active ETF research database, providing tools to list ETFs, track buy/sell deltas, view stock history and PnL, and find consensus buys across ETFs.
      5
      -
    • Haruspex by Haruspex-guru

      Haruspexofficial

      Haruspex-guru
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server exposing the Haruspex stock-analysis API, headline scores (0-100), score history, batched watchlist scores, stock search, and recent news for US-listed
      1
      MIT

    • market-data-mcp

      SmashToes
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Real-time financial market data MCP server. Stocks, crypto, technicals, sentiment, FDA calendar. No API keys required.
      -

    • dsh-quant-data-mcp

      helibeiqi
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server providing A-share market data tools (daily OHLCV, real-time quotes, financials, northbound capital flow, sector lists) with zero dependencies, also serving as a template for building custom MCP servers.
      2
      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

    A4.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: retrieving signals, listing the universe, and checking signal health. No overlap or ambiguity between them.

    Naming Consistency4/5

    Two tools follow the verb_noun pattern (get_latest_signals, list_universe) while signal_health is a noun-based name. Minor inconsistency but still readable and predictable.

    Tool Count5/5

    With 3 tools, the server is right at the lower bound of the well-scoped range. Each tool earns its place and covers the core read-only quant signal workflow.

    Completeness4/5

    The surface covers latest signals, universe, and health checks. Missing historical signal retrieval or per-symbol queries are minor gaps that can be worked around by filtering the full list.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources