No user-submitted related servers found.
Scored across 93 tools
The tool set covers distinct areas like account info, trading, staking, and custodial operations, but there is significant overlap and ambiguity within categories. For example, multiple tools for OCO orders (binance_us_new_oco, binance_us_get_oco, binance_us_open_oco, binance_us_all_oco_orders) and custodial transfers (binance_us_cust_transfer, binance_us_custodial_custodian_transfer, binance_us_custodial_wallet_transfer) have similar purposes, making it easy for an agent to misselect. Descriptions help clarify, but the sheer number of similar tools creates confusion.
Tool names follow a highly consistent snake_case pattern with a clear binance_us_prefix, using verb_noun conventions like get_order, cancel_order, and create_listen_key. There are no deviations in style (e.g., no camelCase or mixed conventions), making the naming predictable and readable throughout the set.
With 93 tools, the count is excessive for a single server, indicating poor scoping. While Binance.US has a broad API, many tools are redundant (e.g., multiple custodial balance tools) or highly specialized (e.g., credit line alerts), creating an overwhelming surface that will be difficult for agents to navigate efficiently. A more modular approach with separate servers for different domains would be more appropriate.
The tool set provides comprehensive coverage of the Binance.US API domain, including account management, trading (spot, OCO, OTC), market data, staking, custodial operations, sub-accounts, and withdrawals. There are no obvious gaps; it supports full CRUD/lifecycle operations for each area (e.g., create, get, cancel orders) and handles edge cases like testing and maintenance checks, ensuring agents can perform all necessary workflows without dead ends.