Skip to main content
Glama
nirholas

Binance.US MCP Server

by nirholas

binance_us_cust_oco_order

Place OCO orders on Binance.US with a custodial solution to automatically cancel one order when the other executes, managing risk in cryptocurrency trading.

Instructions

Place a new OCO (One-Cancels-the-Other) order through the custodial solution.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

OCO orders combine a limit order with a stop-loss order. When one executes, the other is automatically canceled.

Price Restrictions:

  • SELL: Limit Price > Last Price > Stop Price

  • BUY: Limit Price < Last Price < Stop Price

Quantity: Both legs must have the same quantity (iceberg qty can differ).

Note: OCO counts as 2 orders against rate limits.

Response includes orderListId, orders array, and orderReports with details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.
symbolYesTrading pair (e.g., BTCUSD, ETHUSD)
sideYesOrder side: BUY or SELL
quantityYesOrder quantity (same for both legs)
priceYesLimit order price
stopPriceYesStop trigger price
limitClientOrderIdNoUnique ID for the limit order
limitIcebergQtyNoIceberg qty for limit leg
stopClientOrderIdNoUnique ID for the stop leg
stopLimitPriceNoLimit price for stop-limit leg
stopIcebergQtyNoIceberg qty for stop leg
stopLimitTimeInForceNoTime in force for stop-limit leg
assetNoAsset for ExpressTrade
allowExpressTradeNoEnable ExpressTrade

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nirholas/Binance-US-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server