Skip to content
Trend0x

YOUR ASSISTANT. YOUR ACCOUNT. YOUR AUTHORIZATION.

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

Connect Claude, Cursor or a compatible MCP client to 136 discoverable Trend0x tools. Build and edit reviewable strategies, test real historical data, run walk-forward research, and inspect Paper or exchange accounts with your personal agent token. Capabilities depend on your token scope, venue and execution profile.

MCP / 136

From a trading idea to evidence you can review

Market data

Read crypto and stock prices, candles, order books and venue-specific funding or open interest. Tools cover Bybit, Binance, OKX and Hyperliquid, with connected-account data from other supported venues. Data coverage is not identical across exchanges.

Strategy drafts and exact edits

Build from plain language, preserve explicit names and rules, and edit pairs, timeframes, market type and risk settings. Review Apply / Adjust / Backtest before implementation. Applying a draft alone does not start a runner.

Backtests, walk-forward and Paper

Test supported strategies on observed historical candles with disclosed fees and exchange limits. Quote bounded walk-forward research before paying, including for a ready unapplied proposal. Use supported Paper profiles before considering live execution.

Portfolio and managed actions

Review recorded balances, positions, fills, PnL and risk. Preview supported cancellations, owned-strategy position closes and action reconciliation. Live actions require the declared authorization and exchange checks; Bitpanda is read-only.

Connect without sending exchange secrets to chat

  1. Get your personal token

    In Trend0x, open Profile → Security & agent in Pro mode (/app/profile). Connect exchange keys in exchange settings, never 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

POST https://app.trend0x.com/api/mcp
Authorization: Bearer <personal-agent-token>
Content-Type: application/json

{
  "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. Use exchange_capabilities and strategy_capabilities to check the chosen venue, market and draft. Supported paths include Binance, WhiteBIT and Hyperliquid; advanced profiles may still be research-only. Bitpanda is read-only. A connected key does not certify every runner or rule combination.

Before you connect

Does MCP mean the AI can trade without my approval?

No tool grants blanket trading authority. Preview first. Supported direct live tools require an authorized token, confirm=true and dryRun=false, plus the declared request ID, exchange and risk checks. Other operations follow their own tool contract. Once you activate a strategy, its 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.