tv-history
Related Servers
Alternatives to tv-history
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceExposes TradingView data including quotes, technical ratings, historical OHLCV, and market screening through an MCP server using unofficial libraries.-
- AlicenseAqualityCmaintenanceEnables MCP clients to retrieve TradingView market data, including historical OHLCV candles, quotes, technical indicators, and screener results over stdio or SSE.4MIT
- AlicenseAqualityBmaintenanceMCP server that connects coding agents to FXAbsolute's candle history, offering tools to query OHLC data, session scans, bucket stats, level touches, and a live chart bridge for backtesting collaboration.1031MIT
- AlicenseAqualityDmaintenanceAn MCP server that streams K-line (candlestick) data from decentralized exchanges (DEXs) to power your AI agents and workflows.14MIT
- FlicenseNot gradedqualityDmaintenancePython-based MCP server that provides real-time and historical cryptocurrency data from 100+ exchanges via CCXT, with tools for tickers, OHLCV, markets, and order books.1-
- AlicenseBqualityFmaintenanceMCP server for querying historical and real-time crypto market data across Hyperliquid, Hyperliquid HIP-3, and Lighter.xyz - orderbooks, trades, candles, funding, open interest, liquidations, and data quality metrics.1006411MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct output: asset_analysis provides derived market analysis, asset_bars returns raw OHLCV data, and asset_chart renders a visual PNG chart. Although they share similar inputs, the purpose of each is unambiguous and there is no functional overlap.
All three tools follow the identical asset_<resource> noun pattern (analysis, bars, chart). This is a clean, consistent convention that makes the tool's purpose predictable from its name.
With only three tools, the server is tightly scoped to its stated purpose of providing historical market data, analysis, and visualization. Each tool earns its place, and the count is not overly thin or excessive for the domain.
For a read-only history server, the tool set covers the core needs: raw data retrieval (asset_bars), derived analysis (asset_analysis), and visual representation (asset_chart). There are no obvious dead ends or missing lifecycle operations, as the domain does not involve creating or modifying data.