TradingView's official MCP now has 8 Pine Script tools. Your AI assistant can validate code against the real Pine compiler, run an indicator on any symbol, backtest a strategy and save the script to your account. Code that doesn't compile is never saved.
Replying to @MerrymenAI @claudeai
Cool to see trading inside a Claude Code plugin. What I'd want to know before using it on a live account: does it confirm each order before sending, where are size limits enforced, and can it run in paper mode first?
4
Replying to @fere_ai
"You pick the side and the size" is the right split. The agent finds and explains, the human commits the capital. Even better if size caps live at the account level, so a bad prompt can't push past them.
4
Replying to @cyrilXBT
Great resource to learn from. One thing to keep in mind with 4,843 strategies: test enough of them and some will rank high by luck alone. The t stat column helps. Out of sample data and a paper trading run are the next filters before any real money.
3
Replying to @RohOnChain
Turning candles into structured data is the right idea, models read numbers better than pictures. Before it trades on its own: paper trade it for a few weeks, set size and loss caps at the broker so the model can't change them, and log every decision so you can see why it acted.
5
Lots of "my LLM reads every candle now" setups this week. Reading charts and placing orders are different jobs. Start your AI in analyst mode: it reads, explains and flags, you decide. Trader mode only after weeks of paper trading, with caps set at the broker.
If your trading agent reads posts, news or web pages, any of that text can try to give it orders. That's prompt injection. The fix is structure, not a better prompt: the agent that reads has no trading keys, and the one that trades has limits set at the broker.
At least 7 accounts posted the same "19 year old built a trading bot with Claude Code in 2 days, $68 to $750,000" story in the last day, nearly word for word. We can't verify it. Before you copy any bot from a viral post, ask these 5 questions:
Hooking TradingView alerts up to a bot? From TradingView's own help page: webhooks need 2FA on, only ports 80 and 443 work, your server has 3 seconds to respond, and IPv6 isn't supported. Never put passwords or API keys in the alert message. 15 seconds:
Replying to @aiedge_
If anyone wires a setup like this into a brokerage account: give the trading part its own small, separate portfolio and set limits on the broker's side, not in the prompt. Coinbase's new Agent Controls do that with a per-trade cap, 24h volume cap and auto-stop.
3
Replying to @Promirexy @fr0gger_
If you self-host a bot, this is the checklist: no Redis or database ports open to the internet, SSH keys only, no private keys in plain text on the box, and keep the bot's wallet small. Agents scanning for open ports find the easy targets first.
2
Replying to @fere_ai
Good one to ask. Before any plain English swap runs, I'd want the agent to show the exact pair, amount, network and fees, then wait for a yes. And start with a small test amount the first time.
2
Replying to @yugacohler
Enforced by Coinbase, not the agent, is exactly the right design. It's the first thing I'd tell anyone to check before connecting a bot. Looking forward to product permissions, so an agent can be kept to spot and away from derivatives.
1
4
Connecting an AI agent to your broker? We put up free setup guides for Coinbase, Robinhood and Interactive Brokers, education only. Tip from Coinbase's own docs: give the agent a small, separate portfolio and access to that one only. traderstacks.com/guides/brok…














