Skip to main content
Glama
nirholas

Binance.US MCP Server

by nirholas

binance_us_new_oco

Place a One-Cancels-the-Other (OCO) order on Binance.US to execute a limit order and stop-loss order simultaneously, automatically cancelling one when the other triggers for risk management.

Instructions

Place a new OCO (One-Cancels-the-Other) order on Binance.US. OCO orders combine a limit order with a stop-loss order. When one triggers, the other is automatically cancelled. Note: For SELL OCOs, limit price > stop price. For BUY OCOs, limit price < stop price.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesTrading pair symbol (e.g., BTCUSD, ETHUSD)
sideYesOrder side: BUY or SELL
quantityYesOrder quantity for both legs of the OCO
priceYesLimit order price
stopPriceYesStop price that triggers the stop-loss order
stopLimitPriceNoLimit price for the stop-loss leg. If provided, stopLimitTimeInForce is required.
stopLimitTimeInForceNoTime in force for stop-limit order: GTC, IOC, or FOK. Required if stopLimitPrice is provided.
listClientOrderIdNoUnique ID for the entire OCO order list
limitClientOrderIdNoUnique ID for the limit order leg
stopClientOrderIdNoUnique ID for the stop-loss leg
limitIcebergQtyNoIceberg quantity for the limit leg
stopIcebergQtyNoIceberg quantity for the stop-loss leg
trailingDeltaNoTrailing delta in BIPS for the stop leg
newOrderRespTypeNoResponse type: ACK, RESULT, or FULL
selfTradePreventionModeNoSelf-trade prevention mode
recvWindowNoReceive window in milliseconds (max 60000)

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