Skip to main content
Glama
tivojn

ibkr-mcp-guard

by tivojn

Related Servers

Alternatives to ibkr-mcp-guard

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to interact with Interactive Brokers trading accounts to retrieve market data, check positions, and place trades. Includes pre-configured IB Gateway and handles OAuth authentication automatically.
      14
      60 npm
      226
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables LLM agents to interact with Interactive Brokers accounts for market data, account info, and order entry with built-in risk controls and a two-step confirmation flow.
      9
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to Interactive Brokers for intelligent portfolio management, options analysis, risk monitoring, and automated trading strategy suggestions. Enables real-time account tracking, Greeks calculations, option chain analysis, and playbook-based risk adjustments through natural language.
      5
      -
    • A
      license
      B
      quality
      D
      maintenance
      Gives AI assistants real-time access to Interactive Brokers accounts via the Client Portal Web API, with 26 read-only tools for portfolio, market data, options, and scanner.
      32
      14 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to connect to brokerage accounts in read-only mode so users can inspect balances, positions, and orders, and provides a local lab for backtesting strategies and simulated trading with pretend money.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI models with secure access to Interactive Brokers trading data and functionality, enabling account management, market data retrieval, and trading operations through natural language interactions.
      18
      MIT

    TDQS

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools map cleanly to distinct authentication lifecycle actions: sign in, inspect status, and sign out. There is no overlap in purpose, and the descriptions make the boundaries clear.

    Naming Consistency5/5

    All tools use the same predictable prefix and verb pattern: ibkr_sign_in, ibkr_status, ibkr_sign_out. The convention is consistent and readable.

    Tool Count5/5

    For an authentication/guard server, three tools are sufficient and each earns its place. There are no redundant or filler tools.

    Completeness5/5

    The server covers the full auth lifecycle: sign in, check current status and scopes, and sign out/revoke tokens. No obvious operations are missing for its stated purpose as a guard around IBKR access.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues