Skip to main content
Glama
armaaar

thndr-mcp

by armaaar

Related Servers

Alternatives to thndr-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Read-only MCP server for accessing Spark/Ordernet brokerage accounts, including Meitav Trade, Psagot, IBI, Nesua, and Gaon. Enables querying holdings, transactions, orders, returns, security lookup, price history, standing orders, and market news via natural language.
      11
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that provides access to SiftingIO market data, including live prices, SEC filings, OHLCV bars, 13F holdings, market status, and economic calendar tools for AI assistants.
      36
      29 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      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
      22 npm
      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
      975 PyPI
      67
      Apache 2.0
    • 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
    • F
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that exposes Interactive Brokers and Moomoo brokerage accounts as tools, enabling natural-language queries across positions, trade history, realized P&L, and sector exposure in one merged view.
      -

    TDQS

    B3.1/5.0

    Scored across 52 tools

    Disambiguation3/5

    Most tools target distinct resources, but several clusters overlap: get_watchlist vs get_watchlists, get_alert vs get_alerts, get_index_constituents vs screen_market's index filter, and get_market_movers vs screen_market's top-gainer mode. The detailed descriptions help an agent recover, but the set still requires careful reading to avoid misselection.

    Naming Consistency4/5

    The set is predominantly snake_case with a predictable verb_noun or get_/create_/update_/delete_ prefix pattern. A few outliers like auth_status (noun-only) and logout (verb-only) are minor deviations rather than a broken convention.

    Tool Count1/5

    With 52 tools this server is far beyond the typical well-scoped 3-15 range and exceeds even the '25+ too many' threshold. Although many tools serve real subdomains, the sheer surface size creates an extreme mismatch for an agent to navigate.

    Completeness3/5

    Read-side coverage is broad and CRUD is complete for watchlists and alerts, with full auth and account analysis. However, the surface has notable gaps for a trading integration: no order placement/change/cancel and no savings transfers, both explicitly excluded as read-only.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues