tradingview-mcp-proof
Related Servers
Alternatives to tradingview-mcp-proof
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI co-pilots to interact with TradingView charts, manage alerts via REST API, automate morning briefs with custom trading rules, and perform real-time market analysis.-
- AlicenseAqualityAmaintenanceProvides AI agents with a TradingView-centric toolkit for screener queries, historical FX data, pattern scanning, chart rendering, backtesting, Pine tooling, and optional account/desktop integration.6MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to read and control TradingView Desktop charts in real time, supporting chart analysis, Pine Script development, alerts, replay practice, and multi-pane automation.76 npm-
- AlicenseNot gradedqualityBmaintenanceEnables AI models to pull live market data, including quotes, technical indicators, charts, and TradingView screeners, through MCP tools.1MIT
- AlicenseAqualityBmaintenanceEnables AI agents and terminals to control TradingView Desktop over the Chrome DevTools Protocol, providing 29 tools for reading charts and indicator values, exporting data to CSV, managing alerts and layouts, and paper trading.29MIT
- AlicenseBqualityBmaintenanceProvides real-time market data, technical analysis, screeners, and backtesting for stocks, crypto, forex, and futures across global exchanges, enabling AI assistants to fetch quotes, indicators, and strategy results via natural language.2371MIT
TDQS
Scored across 3 tools
Each tool targets a clearly distinct concern: feed liveness, current market state, and recent bar history. There is no overlap because the metadata exposed by each tool is unique to its purpose.
All three tools follow the same get_<noun> pattern in lower_snake_case. The naming is perfectly uniform and predictable.
Three tools is a minimal but well-scoped set for a market-data proof server. Each tool earns its place and adds a non-redundant capability.
The set covers the core lifecycle of checking whether data is live, retrieving a current state, and inspecting recent bars. It lacks broader historical queries or symbol metadata, but those are reasonable gaps for a proof-focused server.