@alexbuzo/dzengi-mcp
Related Servers
Alternatives to @alexbuzo/dzengi-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables 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.2-
- AlicenseNot gradedqualityBmaintenanceEnables 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
- FlicenseCqualityDmaintenanceProvides cryptocurrency market data (prices, symbols) and a gated demo trading flow via MCP tools, with safety defaults like dry-run and confirmation gates.6-
- AlicenseAqualityCmaintenanceUnofficial, safety-first MCP server for convenient xRocket market snapshots, with opt-in local account reads and guarded financial workflows.10111 npmMIT
- AlicenseBqualityBmaintenanceEnables Claude and other MCP clients to read your own brokerage portfolio, balances, PnL, order status and market data, and — only after opt-in — preview and confirm orders, closes, cancels and watchlist changes with cost checks and human approval. Runs read-only against the demo environment by default, with hard exposure caps, rate limits and local key storage.24MIT

noctennaofficial
AlicenseNot gradedqualityBmaintenanceEnables MCP hosts to read and trade Robinhood Chain markets, including swaps, launch checks, bonding-curve launches, Arcus and Lighter perps and funding, weekend reopen watch, bridging, and local wallet operations with two-step confirmations.136 npmMIT
TDQS
Scored across 22 tools
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.
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.
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.
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.