Python MCP server that connects Claude to market screening, TradingView-style technical analysis, Yahoo Finance prices, financial news, Reddit sentiment, backtesting, options-chain lookups, and multi-timeframe trading research workflows for crypto and stock markets.
TradingView MCP Server is an informational analysis tool and does not execute trades, manage money, or guarantee market outcomes., Treat screeners, technical indicators, backtests, walk-forward results, sentiment, options data, and generated trade-plan language as research signals that require independent verification., Market data, news feeds, Reddit sentiment, and third-party technical-analysis providers can be delayed, incomplete, rate-limited, unavailable, or inaccurate., Do not use MCP output as investment, legal, tax, accounting, or trading advice; consult qualified professionals for financial decisions., Keep automated agents from turning analysis output into orders unless a separate, human-approved trading system and compliance process handles execution.
Privacy notes
Symbols, watchlists, exchanges, timeframes, strategy parameters, backtest assumptions, portfolio-like prompts, and research questions may be sent to the MCP client, model, and third-party data providers., Generated analyses can reveal trading interests, research hypotheses, position-like intent, risk preferences, or account-related context if pasted into prompts., Avoid sharing brokerage credentials, account balances, order history, private portfolio allocations, API keys, or non-public investment information through prompts or environment variables., Hosted connector usage may expose prompts and market-research requests to the hosted provider under its terms; self-hosting keeps the MCP server local but still calls external data sources.
Author
Atila Ahmettaner
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
5 safety and 4 privacy notes across 5 risk areas. Review closely: credentials & tokens, network access, third-party handling.
5 areas
SafetyExecution & processesTradingView MCP Server is an informational analysis tool and does not execute trades, manage money, or guarantee market outcomes.
SafetyGeneralTreat screeners, technical indicators, backtests, walk-forward results, sentiment, options data, and generated trade-plan language as research signals that require independent verification.
SafetyThird-party handlingMarket data, news feeds, Reddit sentiment, and third-party technical-analysis providers can be delayed, incomplete, rate-limited, unavailable, or inaccurate.
SafetyGeneralDo not use MCP output as investment, legal, tax, accounting, or trading advice; consult qualified professionals for financial decisions.
SafetyExecution & processesKeep automated agents from turning analysis output into orders unless a separate, human-approved trading system and compliance process handles execution.
PrivacyThird-party handlingSymbols, watchlists, exchanges, timeframes, strategy parameters, backtest assumptions, portfolio-like prompts, and research questions may be sent to the MCP client, model, and third-party data providers.
PrivacyGeneralGenerated analyses can reveal trading interests, research hypotheses, position-like intent, risk preferences, or account-related context if pasted into prompts.
PrivacyCredentials & tokensAvoid sharing brokerage credentials, account balances, order history, private portfolio allocations, API keys, or non-public investment information through prompts or environment variables.
PrivacyNetwork accessHosted connector usage may expose prompts and market-research requests to the hosted provider under its terms; self-hosting keeps the MCP server local but still calls external data sources.
Disclosure: The upstream README describes free self-hosting and a paid hosted connector option from CryptoSieve. This entry documents the open-source self-hosted MCP package and notes the hosted option only as upstream context.
Safety notes
TradingView MCP Server is an informational analysis tool and does not execute trades, manage money, or guarantee market outcomes.
Treat screeners, technical indicators, backtests, walk-forward results, sentiment, options data, and generated trade-plan language as research signals that require independent verification.
Market data, news feeds, Reddit sentiment, and third-party technical-analysis providers can be delayed, incomplete, rate-limited, unavailable, or inaccurate.
Do not use MCP output as investment, legal, tax, accounting, or trading advice; consult qualified professionals for financial decisions.
Keep automated agents from turning analysis output into orders unless a separate, human-approved trading system and compliance process handles execution.
Privacy notes
Symbols, watchlists, exchanges, timeframes, strategy parameters, backtest assumptions, portfolio-like prompts, and research questions may be sent to the MCP client, model, and third-party data providers.
Generated analyses can reveal trading interests, research hypotheses, position-like intent, risk preferences, or account-related context if pasted into prompts.
Avoid sharing brokerage credentials, account balances, order history, private portfolio allocations, API keys, or non-public investment information through prompts or environment variables.
Hosted connector usage may expose prompts and market-research requests to the hosted provider under its terms; self-hosting keeps the MCP server local but still calls external data sources.
Prerequisites
Python 3.10 or newer.
uv or another Python package runner that can launch the `tradingview-mcp-server` package.
Network access to third-party market-data, news, Reddit, Yahoo Finance, and TradingView-related data providers used by the server.
Review of local rules, exchange/data-provider terms, rate limits, and financial-compliance constraints before using live market data.
The upstream README describes free self-hosting and a paid hosted connector option from CryptoSieve. This entry documents the open-source self-hosted MCP package and notes the hosted option only as upstream context.
TradingView MCP Server exposes market-research tools to Claude and other MCP
clients through the tradingview-mcp Python entry point. It can scan crypto and
stock markets, run Bollinger Band and candle-pattern analysis, fetch Yahoo
Finance prices, summarize financial news, inspect Reddit sentiment, compare
backtest strategies, run walk-forward checks, and retrieve options-chain or
unusual-options activity for supported symbols.
The project is designed for analysis and education, not trade execution. Its
README includes an explicit financial-advice disclaimer and positions the server
as an informational tool whose outputs must be independently verified before any
financial decision.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, installation guide, PyPI package metadata, Codex MCP config, Python
package metadata, MCP server implementation, backtesting service, license file,
and project homepage for current install commands, tool coverage, hosted-option
context, financial disclaimers, and licensing.
Features
Python package tradingview-mcp-server with the tradingview-mcp entry point.
MCP configuration for uvx --from tradingview-mcp-server tradingview-mcp.
Market screeners for top gainers, top losers, Bollinger squeezes, ratings,
volume breakouts, candle patterns, and multi-timeframe analysis.
Technical-analysis workflows for crypto exchanges and stock markets.
Yahoo Finance price and market snapshot helpers.
Financial news, Reddit sentiment, and combined analysis tools.
Strategy backtesting, strategy comparison, walk-forward validation, trade-log,
and equity-curve workflows.
Options-chain and unusual-options activity tools for US stock symbols.
The upstream documentation also includes source-based and Windows-specific
setup paths. Use the tradingview-mcp-server package name; tradingview-mcp on
PyPI is a different package from a different repository.
Use Cases
Ask Claude for a top-gainers or top-losers scan for a supported exchange.
Run Bollinger Band, candle-pattern, volume-breakout, or multi-timeframe
analysis for a symbol.
Compare technical-analysis output with Reddit sentiment and current financial
news for research.
Backtest a supported strategy and compare the result with a walk-forward
validation check.
Explore crypto and stock market data without wiring Claude to a brokerage or
trade-execution API.
Safety and Privacy
TradingView MCP Server should be treated as an analysis assistant, not a trading
system. Its outputs can contain trade-plan language, ratings, indicators,
targets, stop-loss-like values, sentiment summaries, and backtest statistics,
but those outputs are not financial advice and can be wrong. Independently
verify data quality, timestamp freshness, exchange coverage, assumptions, fees,
slippage, and provider terms before using any result.
Keep execution separate from analysis. Do not connect MCP-generated conclusions
directly to automated order placement without a separate human-approved trading,
risk, and compliance process. Watch for rate limits, provider outages, delayed
feeds, symbol mismatches, stale prices, and overfit backtests.
Prompts and results can reveal watched symbols, market interests, strategy
ideas, timeframes, private research notes, and position-like intent. Do not
paste brokerage credentials, balances, order history, account identifiers, API
keys, or confidential portfolio information into the MCP client. The self-hosted
server runs locally, but its tools still call external market, news, and
sentiment data sources; the upstream hosted connector is a separate commercial
option with its own trust boundary.
Duplicate Check
Existing MCP content includes finance and market-data entries such as Financial
Datasets MCP Server, SEC EDGAR entries, Drillr, and blockchain-oriented servers.
TradingView MCP Server is distinct because it documents
atilaahmettaner/tradingview-mcp and the tradingview-mcp-server package for
TradingView-style screeners, technical indicators, sentiment/news aggregation,
backtesting, walk-forward validation, Yahoo Finance lookups, and options-chain
research. No dedicated TradingView MCP entry was found in content/mcp.
Show that TradingView MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/tradingview-mcp-server)
How it compares
TradingView MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
Python MCP server that connects Claude to market screening, TradingView-style technical analysis, Yahoo Finance prices, financial news, Reddit sentiment, backtesting, options-chain lookups, and multi-timeframe trading research workflows for crypto and stock markets.
Streamable HTTP MCP server for financial research workflows, including standardized financial data, SEC filing search, company discovery, market signals, ticker resolution, and alternative-data table exploration.
Official Alpaca MCP server for Trading API workflows, including account and portfolio data, orders, positions, watchlists, assets, stocks, crypto, options, news, corporate actions, and market data.
✓TradingView MCP Server is an informational analysis tool and does not execute trades, manage money, or guarantee market outcomes.
Treat screeners, technical indicators, backtests, walk-forward results, sentiment, options data, and generated trade-plan language as research signals that require independent verification.
Market data, news feeds, Reddit sentiment, and third-party technical-analysis providers can be delayed, incomplete, rate-limited, unavailable, or inaccurate.
Do not use MCP output as investment, legal, tax, accounting, or trading advice; consult qualified professionals for financial decisions.
Keep automated agents from turning analysis output into orders unless a separate, human-approved trading system and compliance process handles execution.
✓Drillr's MCP endpoint is a remote Streamable HTTP server at `https://gateway.drillr.ai/mcp/data` and requires a bearer API key.
Tool calls can consume Drillr credits or billable API usage. Check plan limits and remaining credit balance before high-volume research loops.
run_sql is documented as read-only SELECT access, but broad queries across 90-plus tables can still be expensive, slow, or noisy.
Treat outputs as research inputs, not investment, legal, accounting, tax, or trading advice.
Drillr documents that it does not place trades, manage brokerage positions, expose options chains, or provide its own price forecasts.
Review cited SEC filing paragraphs, table schemas, ticker resolution, and source coverage before relying on results in reports or decisions.
✓This server retrieves financial market data; do not treat tool output or model summaries as investment, trading, tax, or legal advice.
Current prices, crypto prices, filings, and news can be delayed, incomplete, rate limited, or unavailable depending on API plan and market conditions.
Review generated analysis before using it in portfolio decisions, trading workflows, client reports, or compliance-sensitive research.
The server sends ticker symbols, date ranges, filing filters, and research queries to the Financial Datasets API.
✓Alpaca MCP Server can expose account balances, buying power, positions, orders, activities, watchlists, assets, market data, news, corporate actions, stocks, crypto, options data, and trading tools to the MCP client.
Trading tools can place stock, ETF, crypto, and option orders, cancel orders, close positions, liquidate portfolios, replace orders, and exercise or mark do-not-exercise option contracts.
Paper trading is the default documented mode; setting `ALPACA_PAPER_TRADE=false` points trading calls at live Alpaca accounts and can result in real financial losses.
Require explicit human approval before any order placement, cancellation, liquidation, option exercise, live-account change, or strategy involving leverage, margin, extended hours, crypto, or options.
Use `ALPACA_TOOLSETS` to restrict the server to read-only or data-only toolsets when trading tools are not needed.
The upstream order override code warns that read timeouts may happen after an order was sent; users should check open orders before retrying to avoid duplicate trades.
Privacy notes
✓Symbols, watchlists, exchanges, timeframes, strategy parameters, backtest assumptions, portfolio-like prompts, and research questions may be sent to the MCP client, model, and third-party data providers.
Generated analyses can reveal trading interests, research hypotheses, position-like intent, risk preferences, or account-related context if pasted into prompts.
Avoid sharing brokerage credentials, account balances, order history, private portfolio allocations, API keys, or non-public investment information through prompts or environment variables.
Hosted connector usage may expose prompts and market-research requests to the hosted provider under its terms; self-hosting keeps the MCP server local but still calls external data sources.
✓Prompts, ticker lists, research themes, SQL queries, and retrieved financial context are sent to Drillr's hosted gateway and the connected MCP client.
Drillr API keys are sensitive credentials. Keep them out of prompts, shared configs, issue comments, logs, screenshots, and repository files.
Research prompts may reveal portfolio interests, watchlists, investment theses, client names, diligence topics, or confidential strategy.
SEC filing excerpts, analyst consensus, alt-data, market signals, and generated summaries may be retained by MCP clients, AI providers, logs, or downstream tools.
Use synthetic prompts or public tickers for demos, screenshots, and examples when client, portfolio, or internal research strategy is sensitive.
✓API keys must be stored in environment variables or local secret managers and never committed to configuration files.
Queried tickers, crypto symbols, time ranges, filings, and news requests can reveal research interests, watchlists, client assignments, or trading hypotheses.
Tool outputs may include financial statements, prices, filings, and news that become part of the model context and logs.
Avoid sending private portfolio holdings, customer identifiers, or material non-public information through prompts or tool arguments.
✓Alpaca API keys, secret keys, account IDs, balances, buying power, portfolio history, activities, positions, orders, watchlists, option contracts, crypto holdings, and trade history can be exposed to the MCP client.
Prompts and responses may include private trading strategy, portfolio allocation, order intent, symbols, quantities, prices, client order IDs, and market data queries.
MCP clients, model providers, terminal history, logs, and chat transcripts may retain financial data and trading instructions.
Upstream documentation states the server sends an Alpaca MCP user agent string for API calls; review Alpaca privacy and disclosure materials for account data handling.
Prerequisites
Python 3.10 or newer.
uv or another Python package runner that can launch the `tradingview-mcp-server` package.
Network access to third-party market-data, news, Reddit, Yahoo Finance, and TradingView-related data providers used by the server.
Review of local rules, exchange/data-provider terms, rate limits, and financial-compliance constraints before using live market data.
Drillr account at `https://drillr.ai`.
External-scope Drillr API key from `https://drillr.ai/developer/keys`.
MCP client that supports Streamable HTTP servers with bearer headers.
Secure secret storage for `DRILLR_API_KEY` outside prompts, repository files, screenshots, and shell history.
Python 3.11 or newer, matching the upstream project metadata.
uv installed on the machine running the MCP server.
A cloned checkout of `financial-datasets/mcp-server`.
Financial Datasets API key stored as `FINANCIAL_DATASETS_API_KEY`.
Python 3.10 or newer and uv or uvx available.
Alpaca API key and secret key for a paper trading account or an explicitly approved live account.
Review of Alpaca account permissions, paper versus live mode, options approval, crypto availability, and market data subscription limits.
A narrow `ALPACA_TOOLSETS` allowlist for the workflow whenever full trading access is not required.