Skip to main content
Glama
senjoyee

Trading 212 MCP Server

by senjoyee

Related Servers

Alternatives to Trading 212 MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that exposes the Trading 212 API with a hard-enforced safety layer—including idempotency ledger, circuit breaker, and position limits—to enable safe live and paper trading through natural language.
      MIT
    • 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
    • A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for Trading 212 accounts, enabling AI assistants to query balances, positions, orders, dividends, pies, and instruments without trading capabilities.
      12
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      This MCP server connects AI assistants to a Public.com brokerage account, enabling natural language trading of stocks, options, and crypto, along with portfolio management, quotes, and orders.
      37
      808 PyPI
      65
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for the Trading 212 API. Provides 28 tools for portfolio management, trading, pies, dividends, market data, and analytics.
      28
      115 PyPI
      8
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      A security-hardened MCP server that wraps the eToro public API, enabling AI assistants to trade, access market data, manage portfolios, and interact with social feeds via 34 tools.
      6
      -

    TDQS

    A4.3/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. Place order tools are clearly differentiated by order type, and get tools are separated by resource (account, instruments, positions, orders, dividends, transactions, reports). No two tools appear to perform the same function.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (get_, place_, cancel_, request_) using lowercase snake_case. The naming is predictable and uniform across the entire set.

    Tool Count4/5

    16 tools is slightly above the ideal 3-15 range but justified by the scope of a trading API covering account info, instruments, orders, history, dividends, transactions, and reports. Each tool serves a distinct purpose and none feel redundant.

    Completeness4/5

    The tool set covers the core lifecycle of trading: viewing account and instruments, managing orders (place/cancel), retrieving positions and historical data, plus reporting. Minor gap: no tool for modifying an existing order, but this can be worked around by cancelling and re-placing.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues