Quant Desk TradingView MCP
Related Servers
Alternatives to Quant Desk TradingView MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables quantitative trading analysis with 12 tools for real-time market data, 28+ technical indicators, FinBERT-powered news sentiment analysis, and automated trading signal generation for stocks and forex.1-
- 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.-
- AlicenseAqualityAmaintenanceInstitutional-grade zero-lookahead Technical Analysis scanner with quantitative confluence scoring & native Model Context Protocol (MCP) server for AI trading agents.6826 PyPI1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-assisted creation, optimization, and management of PineScript trading strategies, with backtesting and TradingView integration.23 npmMIT
- AlicenseBqualityDmaintenanceProvides advanced cryptocurrency and stock market analysis using TradingView data with real-time screening, technical indicators, and pattern recognition. Supports multiple exchanges and markets for comprehensive trading intelligence through natural language queries.103MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to scan crypto and US stocks for beta-adjusted relative strength, momentum signals, RSI readings, and entry/stop/target trade plans, with watchlists validated against live data. Also lets users start a persistent background bot that pushes high-confidence setup alerts via desktop notifications or Discord/Slack webhooks.1MIT
TDQS
Scored across 38 tools
Several tools overlap in purpose (e.g., egx_sector_scan vs egx_sector_scanner, bollinger_scan vs rating_filter, multiple volume/candle scanners, and several analysis variants like coin_analysis, multi_timeframe_analysis, combined_analysis, multi_agent_analysis). Descriptions offer explicit cross-references and clarify the intended use for many pairs, but boundaries remain fuzzy for a large set. An agent could still misselect without careful reading.
All names use snake_case, but the pattern is not fully predictable: some are prefixed by domain (egx_, futures_, stock_), others are generic, and suffixes vary (scan, scanner, screener, analysis). A single get_ prefix appears, and near-duplicate names like egx_sector_scan and egx_sector_scanner break consistency. Still readable overall.
38 tools is excessive for a single server, exceeding the 25+ threshold and risking tool overload. While the broad trading domain (crypto, stocks, EGX, futures, options, news, backtesting) explains some breadth, many tools are overlapping scanners or analysis variants that could be consolidated. The count makes selection unnecessarily difficult.
Coverage spans technical indicators, screeners, news sentiment, backtesting, options, futures, and market overviews, forming a broad trading analysis toolkit. Some gaps exist (e.g., dedicated historical OHLCV retrieval, portfolio/watchlist management), but core workflows appear well supported. Minor missing operations are workaroundable.