Skip to main content
Glama
guilyx

t212-mcp

by guilyx

Related Servers

Alternatives to t212-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      D
      maintenance
      A read-only MCP server that provides access to Charles Schwab account data and market information, including portfolio positions, real-time quotes, options chains, price history, and account balances through AI assistants.
      9
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      An MCP server that wraps the Trading 212 Public API, enabling AI agents to interact with your Trading 212 brokerage account through natural language.
      16
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server that connects a Broker trading account to AI clients, providing account data, positions, orders, and market data via 21 tools, with a mock sandbox mode for evaluation.
      -
    • A
      license
      A
      quality
      B
      maintenance
      MCP server that enables AI assistants to answer portfolio questions about a wealthAPI account, with read-only tools for accounts, transactions, investments, dividends, and market data.
      21
      31 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      A read-only MCP server that lets AI clients query real financial data (bank, credit card, loan, brokerage) via Plaid or Teller, offering tools for balances, transactions, investments, liabilities, identity, income, and debt analysis.
      24
      MIT

    TDQS

    A4.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: cash, account info, positions (all vs single), instrument search, exchanges, pending orders, order history, dividends, transactions, pies (list vs get). The only similar pair (list_positions vs get_position) is clearly differentiated by scope and purpose.

    Naming Consistency5/5

    All tools follow the t212_<verb>_<resource> pattern, with 'list' for collections, 'get' for single resources, and 'search' for the catalog. This is perfectly consistent and predictable.

    Tool Count5/5

    12 tools is well-scoped for a read-only brokerage account server. Each tool covers a distinct aspect of account data (cash, positions, orders, history, dividends, transactions, pies, exchanges, instruments) without redundancy or bloat.

    Completeness5/5

    For its stated purpose (read-only access to account and market data), the tool set is comprehensive. It covers all major read operations: account identification, cash, positions, pending and historical orders, dividends, transactions, pies with detail, exchange schedules, and instrument search. The read-only restriction is consistent with no create/update/delete tools, and there are no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues