polymarket-kalshi-arb-mcp
Related Servers
Alternatives to polymarket-kalshi-arb-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables Claude Desktop, Cursor, and other AI agents to query prediction markets, inspect Level 2 orderbooks, calculate regulatory fees and arbitrage breakevens, estimate implied probabilities, and scan cross-venue spreads.564 npmMIT
- 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.983 npm1MIT
- AlicenseAqualityDmaintenanceAggregates prediction market data from 5 major platforms (Manifold, Polymarket, Metaculus, PredictIt, Kalshi), enabling users to search markets, compare odds across platforms, detect arbitrage opportunities, and track predictions through natural language.85MIT
- AlicenseAqualityBmaintenanceEnables AI agents to search and quote live Kalshi and Polymarket prediction markets, inspect order books, trades, and price history, and compare cross-venue prices using venue-neutral probabilities.6MIT
- AlicenseAqualityDmaintenanceProvides search, trending, odds, arbitrage, and category browsing for prediction markets (Polymarket & Kalshi) via the Model Context Protocol, enabling AI agents to access live market data without API keys.51MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to query live Polymarket and Kalshi odds, price history, movers, resolved and closing markets, cross-platform gaps, watch-based change tracking, and X/Twitter sentiment in a single call, paying per request in USDC on Base via x402. Also surfaces ticker-linked event markets and a free example call so agents can inspect results before spending.54 npmMIT
TDQS
Scored across 2 tools
Both tools query overlapping venues (Polymarket and Manifold, plus Kalshi in one) for prediction market data, so an agent could be unsure which to call just to get odds. The descriptions do offer a meaningful distinction — one is a cross-venue arbitrage/spread scanner (paid), the other is a raw odds/probability lookup — which helps separate them, but the shared venue coverage creates real overlap.
Both names use snake_case, but they follow different conventions: kalshi_polymarket_arb is a venue-listing compound noun while prediction_markets is a generic noun with no verb or action cue. It is readable but there is no predictable verb_noun pattern to guide selection.
Two tools is thin for the stated scope of aggregating and scanning across three prediction markets. A single focused service could justify this, but the two tools carry a lot of combined responsibility (both multi-venue aggregation and arbitrage), leaving little granularity.
There is no way to list available markets/events, retrieve details or historical odds for a specific market, or select venues — the surface jumps straight to odds lookup and arbitrage scanning. For a prediction market aggregator this leaves significant gaps that could cause agent failures when it needs to discover what can be queried.