Skip to main content
Glama
harsha-moparthy

broker-rails

by harsha-moparthy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to broker-rails

No user-submitted related servers found.

    Related Servers

    • oas-execute-mcp

      zorionarrillaga
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that adds a safety layer with eight independent checks and audit logging between a language model and a broker order, supporting both on-disk simulation and live MetaTrader 5 terminals.
      MIT

    • tradebox-mcp

      dearvn
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI trading agents to trade safely through any broker MCP server by recording every tool call and reasoning in a local blackbox, while enforing configurable guardrails such as symbol whitelists, order size caps, rate limits, and daily-loss circuit breakers before orders reach the exchange.
      MIT

    • Litmus

      Spectrexf
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that lets an AI agent backtest, risk-check, and audit trading strategies, determining if a strategy is overfit or actually works.
      MIT

    • tastytrade-mcp

      joncovington
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables autonomous AI agents to connect to Tastytrade for market scanning, option strategies, account management, and optionally placing trades with built-in safety controls.
      9
      MIT

    • PitBridge

      ToolstackVault
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with a NinjaTrader 8 futures account through MCP, with deterministic guardrails and hard risk limits enforced locally that the agent cannot bypass.
      Apache 2.0
    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

    B3.1/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools are clearly distinct (place_order, get_positions, get_account, get_limits). The only potential overlap is market_context and get_quote, both providing quotes; market_context adds headlines, while get_quote is a focused bid/ask, so descriptions disambiguate them.

    Naming Consistency3/5

    Read methods consistently use get_* prefix, but place_order diverges from verb_noun pattern, and market_context/recent_decisions are noun phrases. The mix is readable but not uniform.

    Tool Count5/5

    7 tools cover a focused trading workflow without bloat. Each tool serves a distinct purpose in the domain, making the count well-scoped.

    Completeness4/5

    Core trading operations are covered: quotes, account, positions, order placement, risk limits, and market context/audit decisions. Missing cancel/update order and order status are minor gaps for a simple broker.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources