Rekko MCP
Related Servers
Alternatives to Rekko MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenancePrediction market probability oracle for AI agents. 26 tools across 500+ live markets from Kalshi and Polymarket. Cross-source arbitrage detection, structured TPF signals, Kelly Criterion sizing, agent performance tracking, and webhook alerts.960 npm1MIT
- FlicenseNot gradedqualityDmaintenanceProvides AI-powered tools for searching Polymarket prediction markets and calculating financial metrics like expected value and Kelly bet sizing. It enables users to perform arbitrage scanning, news-based sentiment analysis, and market research through natural language interfaces.-
- AlicenseAqualityBmaintenance24/7 autonomous monitoring and edge detection for prediction markets (Kalshi & Polymarket). Features causal tree analysis, orderbook depth tracking, cross-venue comparison, and real-time alerts.16196 npm12MIT
- AlicenseBqualityAmaintenanceEnables MCP-compatible AI agents to research and trade prediction markets on Polymarket and Kalshi, including market search, orderbooks, price history, positions, order routing, and on-chain builder-code attribution, plus overshoot and dispute-risk signals.42269 PyPIMIT

meridian-edge-mcpofficial
AlicenseAqualityCmaintenanceProvides AI assistants with real-time prediction market consensus data, including probabilities, opportunities, signals, and settlements.5MIT
Veynor MCP Serverofficial
FlicenseNot gradedqualityDmaintenancePrediction market intelligence for AI agents, enabling real-time access to whale trades, market data, signals, and AI-synthesized analysis from Kalshi and Polymarket via a standardized protocol.-
TDQS
Scored across 27 tools
Most tools have distinct purposes, but there is notable overlap between analyze_market/get_strategy and get_arbitrage/get_arbitrage_live, which could confuse agents. Descriptions help clarify differences, but the boundaries are not always sharp.
Tool names follow a highly consistent verb_noun pattern throughout, such as analyze_market, check_analysis_status, get_analysis, and list_markets. There are no deviations in naming conventions, making the set predictable and readable.
With 27 tools, the count feels excessive for a prediction market analysis server, leading to potential complexity and overlap. A more focused set of 10-15 tools could better serve the domain without overwhelming agents.
The tool surface comprehensively covers the prediction market domain, including analysis, trading, portfolio management, data retrieval, and webhooks. There are no obvious gaps, supporting full CRUD/lifecycle operations and agent workflows effectively.