CyberQuant MCP Server
Related Servers
Alternatives to CyberQuant MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityDmaintenanceAn MCP server that lets AI assistants analyze portfolios, stress-test scenarios, generate synthetic market paths, and scan SEC filings — in under 2 minutes.833MIT- AlicenseBqualityDmaintenanceMCP server that exposes QuantXData's institutional crypto market data APIs to AI assistants, enabling natural language queries for trades, order books, OHLCV, options, and more across 120+ exchanges.12MIT

cpzai-mcp-serverofficial
AlicenseNot gradedqualityDmaintenanceMCP server for CPZAI platform, enabling AI agents to manage trading strategies, run backtests, route orders across brokers, and access portfolios, risk analytics, and market data through natural language.1MIT- AlicenseNot gradedqualityCmaintenanceMCP server that makes the CVI Platform a native tool for AI assistants, enabling stock screening, company analysis, and point-in-time research via natural language.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides AI agents with financial tools including real-time quotes, backtesting, technical analysis, and multi-exchange data via a simple CLI interface.1MIT
- AlicenseAqualityDmaintenanceAn MCP server that provides AI agents with real-time access to DEX liquidity pool data, enabling smarter trading, analytics, and automated strategies.101MIT
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: configuration, listing routes, getting route details, querying data, bulk metadata, user profile, cache clearing. No overlapping functionality.
Most tools follow verb_noun pattern (list_routes, get_route_detail, query_data, etc.), but 'configure' is a single verb without a noun, causing a slight inconsistency.
7 tools is well within the ideal 3-15 range. The count feels appropriate for a data query API server without being too heavy or too light.
The tool set covers the full lifecycle: setup (configure), discovery (list_routes, get_route_detail, get_routes_metadata), query (query_data), account info (get_user_profile), and maintenance (clear_routes_cache). No obvious gaps.