MARKET_AI_HUB
Related Servers
Alternatives to MARKET_AI_HUB
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI agents to operate a local financial terminal, including market data, backtesting, paper portfolio management, and news digest, through safe, gated tools over MCP.61MIT
- AlicenseCqualityDmaintenanceProvides comprehensive Taiwan stock market data and analysis through MCP tools. Enables querying real-time stock prices, historical data, company information, technical analysis, and market overviews for TWSE and TPEx listed companies.816MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and HTTP clients to access market data, technical indicators, fundamentals, news, money flow, filings, and code-export endpoints across A-shares, US equities, ETFs, indices, and crypto via MCP or HTTP.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and backend integrations to query multi-market financial data, technical indicators, fundamentals, money flow, news, and filings, and export structured CSV/JSON through MCP tools and HTTP APIs.-
- FlicenseNot gradedqualityFmaintenanceProvides AI clients access to TdxQuant/通达信 financial data and trading capabilities through MCP. Enables retrieval of market data, financial reports, sector information, and trading operations via stdio or HTTP/SSE connections.30-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and backends to access standardized financial market data and analysis tools across A-shares, US equities, ETFs, indices, and crypto, including technical indicators, fundamentals, news, filings, and money flow. It exposes these capabilities through MCP tools and HTTP endpoints, with agent-friendly artifacts and CSV/JSON exports.-
TDQS
Scored across 21 tools
Most tools target distinct resource/action pairs, but several status/snapshot tools overlap (health_check vs get_system_info, get_data_source_status vs get_official_release_snapshot vs get_data_coverage), and analyze_taiwan_stock/analyze_osaka_nikkei vs get_analysis_packet have unclear boundaries. The detailed descriptions help, but the tool set is not immediately unambiguous.
The dominant patterns get_<noun>, predict_<model>, and analyze_<market> are consistent and readable. Minor deviations like health_check, backtest, and run_ts_validation break the pattern slightly but do not create serious confusion.
21 tools is on the heavy side for an MCP surface, with several status/coverage/snapshot tools that could plausibly be consolidated. The broad hub scope makes the count defensible, but it is borderline and requires agents to absorb a large tool list.
The surface covers health, data ingestion, prediction, backtesting, time-series validation, market analysis, and monitoring/archive status. Minor gaps exist around triggering forward tests and retrieving raw prediction outputs, but the core workflows are represented without major dead ends.