Skip to main content
Glama
abuzo

@alexbuzo/dzengi-mcp

by abuzo

Related Servers

Alternatives to @alexbuzo/dzengi-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables local, fail-closed futures trading between WorkBuddy/MCP and InfiniTrader PythonGO v2, exposing 31 MCP tools for market and account queries, trade previews, and order submission while enforcing hard risk controls and an observe-only default.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables secure access to Binance public market data and authenticated account information through a compact set of MCP tools, with optional trading operations that can be explicitly enabled.
      MIT
    • F
      license
      C
      quality
      D
      maintenance
      Provides cryptocurrency market data (prices, symbols) and a gated demo trading flow via MCP tools, with safety defaults like dry-run and confirmation gates.
      6
      -
    • A
      license
      A
      quality
      A
      maintenance
      Unofficial, safety-first MCP server for convenient xRocket market snapshots, with opt-in local account reads and guarded financial workflows.
      10
      951
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to operate a local financial terminal, including market data, backtesting, paper portfolio management, and news digest, through safe, gated tools over MCP.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables safe interaction with a Trading 212 practice/demo account through MCP, providing read-only account and market tools plus guarded order placement and management, strictly limited to the demo API.
      MIT

    TDQS

    A3.7/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools are clearly separated by resource and action (e.g., get_order vs list_open_orders vs place_order). The only potential confusion is between dzengi_edit_order and dzengi_update_order, which both target orders but have different meanings (exchange order edit vs leverage-order protection update), and between dzengi_close_position and dzengi_update_position, which are distinct but could be misread.

    Naming Consistency5/5

    All tools follow a consistent dzengi_<verb>_<noun> pattern with clear verbs like list, get, place, cancel, edit, update, close. The naming convention is uniform and predictable across the entire set.

    Tool Count4/5

    22 tools is on the higher end but appropriate for a trading exchange server covering public market data, account data, order lifecycle, and position management. It is slightly heavy but each tool maps to a distinct exchange operation.

    Completeness4/5

    The surface covers the core trading lifecycle: market data, account info, order placement/cancellation/editing, position management, and preflight validation. Minor gaps include no explicit deposit/withdrawal or historical order archive, but the main workflows are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues