Skip to main content
Glama
LuxAlgo

LuxAlgo Library MCP

Official
by LuxAlgo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to LuxAlgo Library MCP

No user-submitted related servers found.

    Related Servers

    • EdgeDepth Research MCP Server by edgedepthhq

      EdgeDepth Research MCP Serverofficial

      edgedepthhq
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for EdgeDepth's market microstructure search engine, enabling users to query recorded crypto and TradFi perpetuals for market conditions, outcomes, and reproducibility-keyed evidence directly from MCP clients.
      10
      1,033 npm
      3
      MIT

    • MCP TradingView Server

      mathieubernardi
      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

    • Schwab Read-Only MCP

      chensirui2008
      F
      license
      A
      quality
      C
      maintenance
      MCP server for read-only access to Charles Schwab market data and account information. It provides quotes, price history, technical indicators, fundamentals, option chains, market hours, movers, and account/transaction data via the official Schwab API.
      10
      -

    • tradingview-mcp

      GlynnCarson
      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
    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.0

    Scored across 48 tools

    Disambiguation4/5

    Tools are cleanly namespaced by domain (journal_, broker_, library_, propfirms_, trackers_, edge_), and even the crowded propfirms simulation cluster (simulate vs simulate_trades vs pass_rates vs validate_strategy vs compare) is explicitly differentiated in the descriptions. A few pairs like journal_search_notes vs journal_list_trades and broker_stats vs broker_trades sit close together, but cross-references resolve them.

    Naming Consistency4/5

    Consistent domain-prefix + verb_noun convention throughout (journal_get_trade, library_list_indicators, trackers_query). Minor deviations: creation uses both 'add' (journal_add_trade) and 'write' (journal_write_note), and broker_setup/broker_refresh skip the noun.

    Tool Count3/5

    48 tools is heavy for a single server and sits well past the comfortable range. Each of the six bundled domains (journal, broker, library, propfirms, trackers, edge) is individually well-scoped and each tool earns its place within its area, but the aggregate is a monolithic surface that could be split.

    Completeness4/5

    Coverage is deep and near-complete per domain: journal has full read/annotate/note lifecycle, propfirms has search-to-simulation-to-optimization, and library/trackers/edge cover browse, get, and search. Gaps are minor and intentional (no journal delete/remove of fills or trades — corrections are done in-app; broker is read-only by design).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources