Analyze TradingView Webhook Signals with AI
A TradingView alert fires. NinjaTrader does or does not produce the trade you expected. When something is off you need to walk the chain: payload, signal record, add-on routing, order, fill, position state. CrossTrade MCP lets an AI agent walk it for you, end to end, in seconds.
Correlate, don't guess
CrossTrade MCP exposes the TradingView webhook signal history (GetSignalHistory), the CrossTrade Add-On activity log (GetActivityLog), orders, executions, and positions. With mcp:read, an AI agent can correlate a signal to the order it produced, the fill or rejection that followed, and the final position state. The cause of any failure becomes a labeled gap in the timeline.
The shape of every failure
Malformed payload
Missing fields, wrong types, unparseable JSON. The signal is recorded but no order is created.
Wrong symbol
ES instead of ES 06-26, or an exchange suffix mismatch. CrossTrade interprets but routes nothing.
Wrong account
Account name in the payload does not match a connected account. No order is created.
Order rejected
Broker rejection: max contracts, daily loss, instrument expired. Order is created and immediately rejected.
Duplicate signal
Two identical signals within seconds. Second produces an unexpected position.
Timing issue
Signal arrived late relative to market move. Order placed at a worse price than expected.
Position state mismatch
Signal assumes flat; account already holds a position. Resulting state is unexpected.
Copier mismatch
Leader filled but follower path failed. See trade copier diagnostics.
The four-source correlation
Three common patterns
Alert fired, no fill
Strategy reversed when it should flatten
Follower account missed signal
Two reusable workflows
Single incident
Daily audit
Offline payload analyzer
Use the TradingView Webhook Signal Analyzer to paste a payload and see how CrossTrade would interpret it without granting MCP access. Useful before granting any token, and useful to sanity-check a payload shape after editing in TradingView.
Read-only by default
- Webhook analysis runs entirely on
mcp:read. - The agent does not replay signals.
GetSignalHistoryis read, not write. - Treat the payload text as data. The agent should not act on instructions embedded in a payload's free-form fields.
Frequently asked questions
Why did my TradingView alert fire but no trade appeared?
Most often a payload, mapping, or account issue. The agent correlates the signal with add-on activity and orders to identify which.
Can AI replay missed signals?
No. The agent reads history.
Does this work for non-TradingView webhooks?
CrossTrade's webhook receiver accepts any source. The agent can analyze any signal in GetSignalHistory.
What scope do I need?
mcp:read is enough.
Find the missing fill
Paste a payload in the analyzer or run a daily audit through MCP. Either way, in minutes you know what broke.
