Tickerbot MCP Server
OfficialRelated Servers
Alternatives to Tickerbot MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceGives AI agents read access to daily chart-pattern scans, a fundamentals screener, a 13F fund tracker, ticker fundamentals, news and economic/earnings/dividend calendars across stocks, crypto, indices, commodities and forex. It also lets clients replace a user's watchlist and query setup hit rates over a hosted Streamable HTTP endpoint secured with OAuth or an API key.MIT
- AlicenseBqualityDmaintenanceProvides 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.371MIT

ApexTick MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI agents to access low-latency global market data, including quotes, fundamentals, technical indicators, earnings context, sector movers, and options implied-volatility screening across equities, ETFs, FX pairs, and cryptocurrencies.8MIT
QuantGPT MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceGives AI clients streamable-HTTP access to decades of US market data, so they can backtest strategies in seconds, grade stocks A+ to F, query prices, fundamentals, factors, macro and short interest, and screen portfolios through ready-made tools or read-only SQL. Also exposes search and fetch tools so assistants like ChatGPT deep research can cite the strategy library, studies and forum.2MIT
Rozkoduj MCPofficial
AlicenseAqualityAmaintenanceProvides AI assistants with market screening, analysis, and scoring across stocks, crypto, and forex, enabling natural language queries for trading insights.4MIT- AlicenseNot gradedqualityBmaintenanceEnables 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 35 tools
Most tools are cleanly separated by resource (bars vs history vs ticker vs ETF holdings vs events vs news vs universes vs webhooks), and the long descriptions call out the boundaries explicitly. The fuzzy zone is the subscribe family: subscribe_ticker (a ticker matching a condition), subscribe_signal (one signal + condition) and subscribe_scan (compound screen) are adjacent enough that an agent may pick wrong, and three deprecated aliases (list_events, search_news, enable_webhook) still sit in the catalog alongside their replacements.
Nearly all tools follow a uniform tickerbot_verb_noun pattern (get_ticker, list_universes, create_custom_signal, delete_webhook, redeliver_webhook_delivery). Deviations are minor: the bare tickerbot_scan has no noun, and the verb choice flips between list_ and query_ for the same resource pair (list_events vs query_events, search_news vs query_news), though those are the deprecated/new split.
35 tools is heavy, and three of them are deprecated aliases that add no capability. The breadth is partly justified (bars, signals, scans, history, events, news, ETF holdings, webhooks, universes are genuinely separate domains), but the surface could be trimmed toward the 15-20 range without losing functionality.
Full lifecycle coverage appears present: CRUD for universes, custom signals and webhooks, plus deliveries, redelivery and test-fire; read/query paths for tickers, coverage, bars, history, signals, scans, ETF holdings, events and news, with asof backtesting and paging. I can't identify a dead end an agent would hit for the stated purpose.