Skip to content
Trend0x

YOUR ASSISTANT. YOUR ACCOUNT. YOUR AUTHORIZATION.

Trend0x MCP Server: AI trading tools for Claude, Cursor and compatible MCP clients

Connect your AI assistant to Trend0x through the Model Context Protocol. Discover 115 tools for market research, reviewable strategy drafts, historical backtests, paper trading and account analysis. Use your personal agent token; available actions depend on the connected exchange and supported workflow.

MCP / 115

From a trading idea to evidence you can review

Market data

Read prices, candles and order books through venue-specific tools. Bybit, Binance and OKX expose different market-data capabilities; funding and open interest depend on the tool.

Strategy drafts and backtests

Describe an idea, review its explicit rules and test multiple pairs and timeframes against available historical data. A saved draft is not a running strategy.

Paper trading

Run supported saved drafts in a simulated account. Paper results and positive backtests are not forecasts or permission to trade live.

Portfolio, research and risk

Review recorded trades, positions, PnL and risk. WhiteBIT, Bitpanda, Alpaca and Bitunix have account-specific tools; missing amounts or cost basis remain unknown.

Connect without sending exchange secrets to chat

  1. Get your personal token

    In Trend0x, open Account → Security and agent in Pro mode. Connect exchange keys in the exchange settings, not in an AI conversation.

  2. Choose a compatible client

    Use the maintained stdio bridge for clients that support local MCP servers, or a supported authenticated HTTP integration. Follow the setup guide for your client.

  3. Start with read-only discovery

    Inspect the tools and account context before proposing changes. The supplied bridge blocks writes by default; enabling writes does not replace approval for the exact action.

Read-only discovery request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list",
  "params": {}
}

Client compatibility, stated precisely

The remote endpoint accepts authenticated HTTP JSON-RPC and has a legacy SSE transport. It is not a guarantee of one-click support in every client. The included stdio bridge is the documented route for compatible Claude, Cursor, VS Code, Cline or CLI setups. Check client authentication and transport requirements; do not put your token in a URL.

Your token is not an exchange password

Use a personal agent token for MCP. Keep exchange API keys in Trend0x connection settings, use only the read/trade permissions needed, and disable withdrawals. Never share exchange passwords, seed phrases or private wallet keys with an assistant or support.

Connected does not mean every action is available

Market data, account reads, direct orders and saved-strategy runners are separate capabilities. Bitpanda account access is read-only. The audited MCP saved-draft launch path supports Paper and WhiteBIT Spot; other app connectors do not automatically extend that MCP path. Verify current capabilities before a launch.

Before you connect

Does MCP mean the AI can trade without my approval?

No skill grants blanket trading authority. Review and authorize live actions. Some direct tools do not have a separate server confirmation field, so use the bridge write guard and approve the exact operation. Once you activate a strategy, matching rules may submit orders until you pause it.

Will I see my exchange keys in the assistant?

Use the account token, not exchange credentials, to connect your client. Do not paste exchange secrets into chat. Tool outputs should be masked; if any credential appears, stop sharing the response and contact support.

Does a backtest prove a strategy will be profitable?

No. Historical results depend on data, rules, costs and the tested period. Paper fills can differ from real execution. Missing data and unverified runner states must not be presented as successful trading.