Skip to main content
Glama
florinel-chis

oanda-mcp

by florinel-chis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to oanda-mcp

No user-submitted related servers found.

    Related Servers

    • IG Trading MCP

      MarkHorwell
      A
      license
      B
      quality
      A
      maintenance
      A local MCP server for IG's REST Trading API, providing account/history, market data, position, working-order, and trade-confirmation tools with guarded OTC trade actions.
      20
      MIT

    • trading212-mcp

      florinel-chis
      A
      license
      A
      quality
      B
      maintenance
      MCP server for the Trading 212 public API, enabling account, portfolio, order, pie, and history access with read tools always available and trading tools opt-in.
      13
      1
      MIT

    • tastytrade-mcp

      bholzer
      F
      license
      A
      quality
      D
      maintenance
      MCP server for the tastytrade brokerage API, providing tools for account management, market data, and order execution.
      18
      -

    • IG Integration MCP

      MarkHorwell
      A
      license
      B
      quality
      B
      maintenance
      MCP server for IG's REST Trading API and Lightstreamer streaming API. Provides tools for accounts, markets, positions, orders, watchlists, sentiment, OTC trades, and streaming price/account/trade/chart data.
      22
      Apache 2.0

    • paper-fx-mcp

      dommy-i
      F
      license
      Not graded
      quality
      B
      maintenance
      Integrates OANDA FX trading with technical analysis, economic news, stock/indices quotes, corporate financials, EDINET disclosures, and composite scoring into a unified MCP server.
      -

    • ibkr-mcp

      jgalea
      A
      license
      B
      quality
      C
      maintenance
      A read-only-by-default MCP server for Interactive Brokers that exposes account, positions, PnL, market data, and trade history from a local TWS/IB Gateway session, with optional trading capabilities.
      15
      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 22 tools

    Disambiguation4/5

    Each tool targets a distinct resource or filtered view, such as list_orders vs list_pending_orders and list_trades vs list_open_trades. The only overlapping pair is get_account/get_account_summary, but the descriptions explicitly clarify the cost tradeoff. Overall, purposes are clearly delineated.

    Naming Consistency5/5

    All tools follow a consistent list_X or get_X pattern with clear resource nouns (accounts, instruments, candles, orders, trades, positions, transactions). There are no mixed conventions or vague verbs.

    Tool Count3/5

    At 22 tools, the server is on the heavy side, with several near-duplicate filter tools (list_open_*, list_pending_orders) and convenience wrappers (get_latest_candles) that could be folded into the base tools. Still, each tool maps to a clear endpoint and the count is within reason for a comprehensive trading data API.

    Completeness2/5

    The read side is exhaustive: accounts, instruments, market data, orders, trades, positions, and transactions are all covered. However, there are zero write or mutation tools—no way to create, modify, or cancel orders, close trades, or change account settings. This is a critical gap for a trading server and will cause agent failures when action is required.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources