Tickerbot MCP Server
OfficialRelated Servers
Alternatives to Tickerbot MCP Server
No user-submitted related servers found.
Related Servers
- 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.371MIT

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 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
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to access and analyze 250+ financial data tools covering stocks, ETFs, crypto, forex, commodities, economics, and more, with runtime toolset management and hosted or self-hosted HTTP/SSE deployment.569 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to access and analyze stocks, ETFs, crypto, forex, commodities, economics, company fundamentals, and market insights through 250+ financial data tools. Supports dynamic toolset loading and multiple deployment modes for flexible integration.569 npmApache 2.0
- AlicenseAqualityBmaintenanceA modular MCP server providing 64 tools across 13 modules for real-time stock and crypto market data, including scanning, technical analysis, options flow, insider trades, and personalized watchlists.39610 npm8MIT
TDQS
Scored across 35 tools
Most tools have distinct purposes, but a few pairs could be confused: get_ticker_history vs get_series (snapshot vs series), and list_universes vs list_system_universes (the latter is a subset of the former). Also, subscribe_* tools overlap with create_webhook, though descriptions clarify the differences.
All tools share the tickerbot_ prefix and largely follow a verb_noun pattern. However, 'scan' is a bare verb without an object, 'patch_webhook' uses 'patch' while other updates use 'update_', and 'list_system_universes' duplicates functionality already in 'list_universes'.
35 tools is well over the 25+ threshold. The server's broad scope justifies many tools, but the count feels excessive, especially with redundant webhook creation routes and overlapping universe listing tools. Some consolidation is needed.
The tool set thoroughly covers the domain: data retrieval (tickers, bars, history, series, ETF data), scanning, signals, events, news, webhooks (full lifecycle), universes (full CRUD), and custom signals (full CRUD). No obvious gaps or dead ends exist for the described functionality.