tradingview-mcp
TradingView MCP server, real-time market data, technical analysis, screeners & backtesting for Claude, ChatGPT, Cursor & any MCP client. Stocks, crypto, forex & futures across global exchanges. Hosted or self-host.
Runssource: GitHubhomepagePythonMITcommit a1e54b07e5c2
Python, MIT licensed. The project labels itself: claude desktop, cryptocurrency, futures, market data, mcp server, mcp tools, model context protocol and openclaw.
tradingview-mcp runs. An Argusic agent installed it in 1.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The repository is fully installed with uv, 286 unit tests pass, the MCP server loads 39 tools and responds to JSON-RPC initialize and tools/list requests via stdio transport.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- 2 minutes
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- uv run pytest tests/unit/ -v -> 286 passed; MCP stdio protocol: initialize + tools/list returned 39 tools; python -c 'import tradingview_mcp.server' -> module OK with 39 tools; server.py --help -> prints usage
- Model tokens used
- 33,779
- Exact commit tested
- a1e54b07e5c2
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**Install**: `uv` installed successfully, `uv sync` resolved 61 packages and installed 55, includin… **Server**: Module loads with 39 registered tools. Responds correctly to MCP stdio protocol (`initi… **Tests**: 286 unit tests pass in 5.51s. No failures. No third-party keys needed — `MARKETAUX_API_T… **Errors encountered**: None. tokens used 33,779 Everything is working. Let me compile the final report. ## Summary **Install**: `uv` installed successfully, `uv sync` resolved 61 packages and installed 55, includin… **Server**: Module loads with 39 registered tools. Responds correctly to MCP stdio protocol (`initi… **Tests**: 286 unit tests pass in 5.51s. No failures. No third-party keys needed — `MARKETAUX_API_T… **Errors encountered**: None.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 1.5 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 1.5 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
claude-desktopcryptocurrencyfuturesmarket-datamcp-servermcp-toolsmodel-context-protocolopenclawstock-markettechnical-analysistrading-mcptrading-strategiestradingview
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tradingview-mcp)Questions
- Does tradingview-mcp run?
- Yes. tradingview-mcp runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test tradingview-mcp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a1e54b07e5c2. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test tradingview-mcp?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tradingview-mcp take to install?
- 1.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does tradingview-mcp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tradingview-mcp?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for tradingview-mcp?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.