Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Trend0x

REMOTE · APP.TREND0X.COM

AI trading terminal: market data, backtests, strategies and portfolio for crypto and stock exchanges

Available components

53 Trust /100

Last scanned (20 hours ago)

Scores higher than 42% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability52
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 6321 tokens (~54/item across 115 items; 115 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 11% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_trade" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 115 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 3 Nov 26 53

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://app.trend0x.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=trend0x.com CN=WE1,O=Google Trust Services,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA256 7953c543641023dd132a0c531c48cb7e
SANs: trend0x.com, *.trend0x.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.trend0x.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
trend0x.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 3 probes
Transport URL Outcome Status Location
streamable-http https://app.trend0x.com/api/mcp Verified 200
sse https://app.trend0x.com/api/mcp Verified 200
http (plaintext) http://app.trend0x.com/api/mcp HTTPS enforced 301 https://app.trend0x.com/api/mcp
MCP tools · 115 exposed · ~6,321 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
account_risk_settings ~90

Read or update only the authenticated account's risk settings with an agent token; dry_run validates an update without saving.

NameTypeReqDescription
actionstring––
dry_runboolean––
fixedTradeAmountnumber––
leveragenumber––
riskSettingsobject––
stopLossPercentnumber––
takeProfitPercentnumber––

No output schema declared.

No examples provided.

agent_reports ~46

List or push agent reports into the terminal dashboard.

NameTypeReqDescription
actionstring––
contentstring––
titlestring––
typestring––

No output schema declared.

No examples provided.

assistant_operation ~81

Natural-language strategy inventory, bulk run/pause, pair/exchange filters and positive-PnL selection. Returns contextual questions and reply options; requires the exact preview confirmation phrase to start runners. Never switches existing exchange bindings or fabricates PnL. Use a unique conversation_id per chat.

NameTypeReqDescription
conversation_idstring––
textstringyes–

No output schema declared.

No examples provided.

backtest_results ~37

Read recorded backtest results.

NameTypeReqDescription
limitnumber––
strategy_idstring––
symbolstring––

No output schema declared.

No examples provided.

binance_account_balance ~58

Binance authenticated balances. For spot, returns account balances; for futures, returns USD-M account data. Respects configured remote proxy for IP-whitelisted users.

NameTypeReqDescription
marketTypestring––
nonZeroOnlyboolean––

No output schema declared.

No examples provided.

binance_agent_skills ~26

List Binance Skills Hub categories and Trend0x Binance MCP/API routing guidance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

binance_exchange_info ~42

Binance public instrument metadata, filters, tick sizes, lot sizes, and trading status.

NameTypeReqDescription
marketTypestring––
symbolstring––

No output schema declared.

No examples provided.

binance_funding_rate ~39

Binance USD-M futures funding rate history.

NameTypeReqDescription
limitnumber––
symbolstring–e.g. BTCUSDT

No output schema declared.

No examples provided.

binance_income_history ~66

Binance authenticated USD-M futures income history, including funding fees and realized PnL.

NameTypeReqDescription
incomeTypestring–Optional Binance income type, e.g. REALIZED_PNL or FUNDING_FEE
limitnumber––
symbolstring––

No output schema declared.

No examples provided.

binance_market_klines ~59

Binance public candlesticks for spot or USD-M futures.

NameTypeReqDescription
intervalstring––
limitnumber––
marketTypestring––
symbolstringyese.g. BTCUSDT

No output schema declared.

No examples provided.

binance_market_ticker ~56

Binance public ticker data for spot or USD-M futures. Use for current price and 24h stats.

NameTypeReqDescription
marketTypestring––
symbolstring–Optional symbol, e.g. BTCUSDT

No output schema declared.

No examples provided.

binance_open_interest ~33

Binance USD-M futures open interest for a symbol.

NameTypeReqDescription
symbolstringyese.g. BTCUSDT

No output schema declared.

No examples provided.

binance_open_orders ~36

Binance authenticated open orders for spot or USD-M futures.

NameTypeReqDescription
marketTypestring––
symbolstring––

No output schema declared.

No examples provided.

binance_order_history ~50

Binance authenticated order history for one symbol. Symbol is required to prevent account-wide request storms.

NameTypeReqDescription
limitnumber––
marketTypestring––
symbolstringyes–

No output schema declared.

No examples provided.

binance_orderbook ~50

Binance public order book snapshot for spot or USD-M futures.

NameTypeReqDescription
limitnumber––
marketTypestring––
symbolstringyese.g. BTCUSDT

No output schema declared.

No examples provided.

binance_positions ~43

Binance authenticated USD-M futures positions. Respects configured remote proxy for IP-whitelisted users.

NameTypeReqDescription
nonZeroOnlyboolean––
symbolstring––

No output schema declared.

No examples provided.

binance_trade_history ~52

Binance authenticated trade/fill history for one symbol. Symbol is required to prevent account-wide request storms.

NameTypeReqDescription
limitnumber––
marketTypestring––
symbolstringyes–

No output schema declared.

No examples provided.

bybit_cancel_order ~60

Official Bybit V5 cancel order. Requires confirm=true.

NameTypeReqDescription
categorystring––
confirmboolean––
orderIdstring––
orderLinkIdstring––
symbolstringyes–

No output schema declared.

No examples provided.

bybit_instruments_info ~64

Official Bybit V5 instrument metadata, filters, tick sizes, and trading status.

NameTypeReqDescription
baseCoinstring––
categorystring––
limitnumber––
statusstring––
symbolstring––

No output schema declared.

No examples provided.

bybit_internal_transfer ~112

Official Bybit V5 internal transfer between account types under the same UID. Live transfer requires confirm=true.

NameTypeReqDescription
amountstringyes–
coinstringyes–
confirmboolean–Must be true to execute a live transfer.
dryRunboolean–If true, validate and return the payload without transferring funds.
fromAccountTypestring––
toAccountTypestring––
transferIdstring–Optional UUID. Generated automatically when omitted.

No output schema declared.

No examples provided.

bybit_market_kline ~83

Official Bybit V5 candlesticks. Intervals use Bybit values such as 1, 5, 15, 60, 240, D, W, M.

NameTypeReqDescription
categorystring––
intervalstring––
limitnumber––
symbolstringyese.g. BTCUSDT

No output schema declared.

No examples provided.

bybit_market_tickers ~53

Official Bybit V5 market ticker data for spot, linear, inverse, or option markets.

NameTypeReqDescription
categorystring––
symbolstring–Optional symbol, e.g. BTCUSDT

No output schema declared.

No examples provided.

bybit_open_orders ~41

Official Bybit V5 authenticated open orders.

NameTypeReqDescription
categorystring––
openOnlynumber––
symbolstring––

No output schema declared.

No examples provided.

bybit_order_history ~40

Official Bybit V5 authenticated historical orders.

NameTypeReqDescription
categorystring––
limitnumber––
symbolstring––

No output schema declared.

No examples provided.

bybit_orderbook ~46

Official Bybit V5 order book snapshot.

NameTypeReqDescription
categorystring––
limitnumber––
symbolstringyese.g. BTCUSDT

No output schema declared.

No examples provided.

bybit_place_order ~141

Official Bybit V5 order placement. Live execution requires confirm=true and connected Bybit trade permissions.

NameTypeReqDescription
categorystring––
confirmboolean–Must be true to place a live order.
dryRunboolean–If true, validate and return the payload without placing the order.
orderTypestring––
pricestring––
qtystringyes–
reduceOnlyboolean––
sidestringyes–
stopLossstring––
symbolstringyes–
takeProfitstring––
timeInForcestring––

No output schema declared.

No examples provided.

bybit_positions ~40

Official Bybit V5 authenticated open positions.

NameTypeReqDescription
categorystring––
settleCoinstring––
symbolstring––

No output schema declared.

No examples provided.

bybit_set_leverage ~67

Official Bybit V5 set leverage for linear or inverse contracts. Requires confirm=true.

NameTypeReqDescription
buyLeveragestringyes–
categorystring––
confirmboolean––
sellLeveragestringyes–
symbolstringyes–

No output schema declared.

No examples provided.

bybit_set_trading_stop ~103

Official Bybit V5 take-profit, stop-loss, and trailing stop update. Requires confirm=true.

NameTypeReqDescription
activePricestring––
categorystring––
confirmboolean––
positionIdxnumber––
stopLossstring––
symbolstringyes–
takeProfitstring––
tpslModestring––
trailingStopstring––

No output schema declared.

No examples provided.

bybit_trade_history ~41

Official Bybit V5 authenticated trade execution history.

NameTypeReqDescription
categorystring––
limitnumber––
symbolstring––

No output schema declared.

No examples provided.

bybit_wallet_balance ~56

Official Bybit V5 authenticated wallet balance. Requires connected Bybit API keys.

NameTypeReqDescription
accountTypestring––
coinstring–Optional comma-separated coins, e.g. USDT,USDC,BTC

No output schema declared.

No examples provided.

calculate_position_size ~66

Calculate position size using risk-per-trade logic.

NameTypeReqDescription
account_balancenumberyes–
entry_pricenumberyes–
exchangestring––
leveragenumber––
risk_pctnumber––
stop_loss_pricenumberyes–

No output schema declared.

No examples provided.

circuit_breaker ~50

Evaluate or trip trading circuit breaker guardrail.

NameTypeReqDescription
bypassboolean––
exchangestring––
price_spike_pctnumber––
volatility_multipliernumber––

No output schema declared.

No examples provided.

cognitive_control ~59

Read or update cognitive brain mode, guardian, kill switch, and profit lock.

NameTypeReqDescription
actionstring––
activateboolean––
enabledboolean––
limitnumber––
modestring––

No output schema declared.

No examples provided.

create_scanner_task ~115

Create an active Trend0x scanner task for the authenticated user and optionally enable scanner/autopilot. Use this for requests like 'create scanner task', 'monitor pairs', or 'scan market'.

NameTypeReqDescription
durationMsnumber––
enableScannerboolean––
labelstring––
pairstring––
pairsarray––
promptstring––
strategystring––
timeframestring––
timeframesarray––

No output schema declared.

No examples provided.

create_task ~115

Create an autonomous agent workflow task. For scanner tasks, pass type=SCAN plus pair/pairs, timeframe, strategy, and status=active.

NameTypeReqDescription
detailsstring––
durationMsnumber––
labelstring––
pairstring––
pairsarray––
progressnumber––
promptstringyes–
statusstring––
strategystring––
timeframestring––
typestring––

No output schema declared.

No examples provided.

disable_scanner ~25

Convenience tool: disable Trend0x scanner/autopilot for the authenticated user.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

earnings_recap ~25

Market intelligence alias: earnings and fundamentals recap.

NameTypeReqDescription
symbolstringyes–

No output schema declared.

No examples provided.

emergency_close_all ~38

Kill switch: close all open positions on an exchange. Requires confirm=true.

NameTypeReqDescription
confirmboolean––
exchangestring––

No output schema declared.

No examples provided.

enable_scanner ~51

Convenience tool: enable Trend0x scanner/autopilot for the authenticated user.

NameTypeReqDescription
primaryTimeframestring––
scannerPairsarray––
scannerTimeframesarray––

No output schema declared.

No examples provided.

execute_alpaca_trade ~53

Place a stock order through the Trend0x executor using Alpaca.

NameTypeReqDescription
qtystringyes–
sidestringyes–
symbolstringyes–
typestring––

No output schema declared.

No examples provided.

execute_bitunix_trade ~65

Execute a trade on Bitunix through the Trend0x executor.

NameTypeReqDescription
amountnumber––
leveragestring––
qtystring––
sidestringyes–
symbolstringyes–
typestring––

No output schema declared.

No examples provided.

execute_trade ~172

Execute a market order on a connected exchange.

NameTypeReqDescription
amountstring–Alias for qty / quote amount
dryRunboolean–Validate and normalize the request without sending an order.
exchangestring––
leveragestring––
marketTypestring–For BINANCE, explicitly choose spot or futures.
orderTypestring––
pricestring–Limit price when orderType is Limit
qtystring–Quantity or quote amount
quantitystring–Alias for qty
sidestringyes–
slstring–Optional stop loss
symbolstringyese.g. BTCUSDT
tpstring–Optional take profit
triggerPricestring–Optional trigger price

No output schema declared.

No examples provided.

fetch_terminal_state ~23

Fetch balances, positions, news, and health from unified terminal state.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

financial_instruments ~29

Return the Trend0x scanner financial instrument universe used by market-intelligence-enhanced research and scanning.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_alpaca_account ~20

Fetch Alpaca account configuration and connection status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_alpaca_news ~41

Get latest market news for one or more symbols.

NameTypeReqDescription
symbolsstring–Comma separated symbols, e.g. TSLA,NVDA

No output schema declared.

No examples provided.

get_alpaca_positions ~22

List Alpaca stock positions from the unified account state.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_balance ~22

Get account balance for an exchange.

NameTypeReqDescription
exchangestringyes–

No output schema declared.

No examples provided.

get_bitpanda_portfolio ~40

Read the authenticated user's Bitpanda asset and fiat wallets. Bitpanda retail API access is read-only; this tool never places orders.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Trend0x MCP server?

Trend0x is a hosted endpoint at https://app.trend0x.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · app.trend0x.com

# add to Claude Code
claude mcp add --transport http trend0xai-trend0x 'https://app.trend0x.com/api/mcp'
Common questions

What is the Trend0x MCP server?

Trend0x is an MCP server listed in the public MCP registry as io.github.trend0xai/trend0x. AI trading terminal: market data, backtests, strategies and portfolio for crypto and stock exchanges. This page covers its hosted endpoint (https://app.trend0x.com/api/mcp).

Is the Trend0x MCP server safe to use?

Trend0x scores 53 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Trend0x MCP server expose?

Trend0x exposes 115 tools: get_market_data, execute_trade, get_balance, paper_profit_policy, assistant_operation, and 110 more. Their descriptions and schemas cost roughly 6,321 tokens of context every time the server is loaded.

Does the Trend0x MCP server require authentication?

No. We connected to Trend0x without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Trend0x MCP server still maintained?

Trend0x is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.