Activity
Stars and mentions · Last 30 days, Oct 6 – Nov 4
Top repositories
tradesdontlie’s repositories ranked by new stars, as on trending.
Contributes to
Repositories outside tradesdontlie’s account where tradesdontlie opened or reviewed pull requests in the past 365 days.
Who noticed tradesdontlie
Everyone who starred or forked tradesdontlie’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
Achievements
Awards earned by the repositories tradesdontlie owns. Select an award to embed its badge.
No awards yet
Repositories earn awards by reaching the top three in a completed trending day or week.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
Tu agente de IA ya puede manejar tu TradingView: watchlists, screener, alertas y brief diario. MCP oficial (plan Essential+): mcp.tradingview.com Open source: tradesdontlie/tradingview-mcp Mi regla: solo lectura y que pida OK antes de tocar alertas. No es consejo de inversión. t.co
tradingview-mcp lets Claude Code drive TradingView Desktop: switch symbols, read indicators and OHLCV, draw, set alerts, write and compile Pine Script. About 80 tools, MIT. It needs a subscription, and automation may violate TradingView's terms: tradesdontlie/tradingview-mcp t.co
𝟲,𝟭𝟬𝟬 𝘁𝗿𝗮𝗱𝗲𝗿𝘀 𝘀𝘁𝗮𝗿𝗿𝗲𝗱 𝘁𝗵𝗶𝘀 𝗿𝗲𝗽𝗼. 𝗜𝘁 𝗹𝗲𝘁𝘀 𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝘄𝗿𝗶𝘁𝗲, 𝗰𝗼𝗺𝗽𝗶𝗹𝗲 𝗮𝗻𝗱 𝗿𝗲𝗽𝗹𝗮𝘆-𝘁𝗲𝘀𝘁 𝗣𝗶𝗻𝗲 𝗦𝗰𝗿𝗶𝗽𝘁 𝗶𝗻 𝗧𝗿𝗮𝗱𝗶𝗻𝗴𝗩𝗶𝗲𝘄. tradesdontlie/tradingview-mcp MIT licensed, 2.8k forks. It drives TradingView Desktop on your own machine: Symbols and intervals Indicators and alerts Pine Script: write, compile, read the errors Bar replay with simulated buy and sell Screenshots sent back to the model Three things I would test first: 1. The compile loop. Hand it one of my published scripts and see if it fixes a real compile error without quietly changing the logic. 2. Replay honesty. Run one setup in bar replay and check whether the simulated fills agree with what my own backtest says. 3. Alerts. Build an alert from a Pine condition and confirm it fires on the right bar, not the one after. What it is not: the interfaces are unofficial, so a TradingView update can break them. The author flags TradingView's terms himself. Nothing here places a real order. A research assistant, not a trading bot. Would you let a model touch your indicator code, or only your research scripts?