Setting a take-profit and accidentally clearing an existing stop-loss is the kind of mistake that only shows up when the position moves against you. Defining null as no-change rather than as clear removes it. Beyond that, be clear about what this surface is: place_order transacts on a live account, and raw_api_call reaches commands nobody wrapped or reviewed. Between them, an agent holding these credentials can do anything the account can. That is a decision about supervision rather than a criticism of the tool, but it should be a deliberate one.
A brokerage client covering account and portfolio reads, order placement and management, market data, and price alerts, with a raw call for anything the tools do not wrap.
- get_user_data and get_portfolio return account info, funds, positions and the portfolio summary.
- place_order covers buy, sell, short and margin and returns an order id, with cancel_order to withdraw an active one.
- set_stop_loss_take_profit sets either or both, and passing null leaves one unchanged rather than clearing it.
- Market data: search_tickers with a market filter, get_security_info for a ticker's detail, and get_quotes_history returning OHLCV candles.
- Price alerts added and deleted, so a condition can be watched rather than polled.
- get_security_sessions lists open sessions for two-factor authentication.
- raw_api_call reaches any Tradernet command the dedicated tools do not cover.
TRADERNET_PUBLIC_KEY and TRADERNET_PRIVATE_KEY. place_order executes against a real brokerage account with real money.
One command plus a key — claude mcp add tradernet -- npx -y tradernet-mcp, then supply credentials