Skip to main content
Glama
hamzafaiz17

TradeZylo MCP Server

by hamzafaiz17

Related Servers

Alternatives to TradeZylo MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to perform cryptocurrency trading analysis and execution with 38+ tools including real-time market data, technical indicators, risk management, and support for both paper trading and live execution on Hyperliquid.
      7
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to interact with a complete trading infrastructure, including live futures bots, real market data, backtesting, and copy-trading signals. Supports 503 tools across 20 domains, from market data to order execution, with zero synthetic data.
      168
      1
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Provides 32 trading analysis tools for AI-powered market analysis, including real-time data, technical indicators, options Greeks, scanners, and Interactive Brokers portfolio management, all accessible via natural language in Claude Desktop.
      35
      358
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Provides 31 AI-powered crypto trading tools for Claude, Cursor, and any MCP client, enabling strategy creation, backtesting, bot deployment, copy trading, and portfolio management across multiple exchanges.
      34
      23
      MIT

    TDQS

    A3.6/5.0

    Scored across 38 tools

    Disambiguation3/5

    Many analytical tools have clear boundaries, but significant overlap exists among account management and freeze-related tools. pause_account, freeze_trading, and unfreeze_trading operate on similar concepts (deactivating/reactivating), and resume_account overlaps with unfreeze_trading. get_risk_limits vs get_risk_check are distinct, but overall, an agent could easily misselect among the freeze/pause/resume tools.

    Naming Consistency4/5

    Most tool names follow a consistent snake_case verb_noun pattern (get_, log_, update_, close_, add_, etc.). Minor inconsistencies include 'close_trade' vs 'log_trade' (different verbs for trade actions) and 'unfreeze_trading' vs 'resume_account' (both reactivation but different naming styles). Overall, the pattern is predictable and readable.

    Tool Count3/5

    With 38 tools, the server is on the heavy side for an MCP server. While the domain (trading journal and analytics) is broad and each tool appears to have a purpose, the count likely exceeds what an agent can efficiently manage, and some tools (e.g., pause_account vs freeze_trading vs resume_account) seem redundant or could be consolidated.

    Completeness4/5

    The tool surface covers a wide range of trading journal operations: trade CRUD, analytics, risk management, account management, playbook strategies, and notebook. Minor gaps include no explicit tool to delete a trade, account, or strategy, and no tool to fetch a single account's full details (only get_accounts with filter). However, most core workflows are well-supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues