
Mcp Server
Pull aggregated prediction-market probabilities from Kalshi, Polymarket, and Metaculus while scoping bets, features, or narratives.
Overview
TeleKash Oracle is a Validate-phase MCP server that surfaces prediction-market probabilities from 500+ markets across Kalshi, Polymarket, and Metaculus.
What is this MCP server?
- Prediction market probability oracle across multiple venues
- 500+ markets sourced from Kalshi, Polymarket, and Metaculus
- stdio npm package telekash-mcp-server (v0.6.1 in schema)
- Reads market data via Supabase URL and SUPABASE_ANON_KEY
- GitHub: TeleKashOracle/mcp-server
- 500+ prediction markets from Kalshi, Polymarket, and Metaculus per description
- npm identifier telekash-mcp-server at package version 0.6.1 in schema
What problem does it solve?
You cannot quickly compare implied probabilities across major prediction venues from inside your coding agent.
Who is it for?
Builders prototyping forecasting features, research bots, or validation memos that need multi-venue odds in one MCP call path.
Skip if: Operators who need trade execution, private portfolio data, or markets outside the TeleKash Supabase corpus.
What do I get? / Deliverables
Your agent can query a unified oracle so scope and priors for event-driven products align with market consensus data.
- Agent-queryable probability context across 500+ listed markets
- Faster validation notes grounded in multi-venue implied odds
Recommended MCP Servers
Journey fit
How it compares
Read-only probability oracle over MCP, not a brokerage or on-chain trading integration.
Common Questions / FAQ
Who is TeleKash Oracle MCP for?
Solo builders and researchers who validate ideas with prediction-market data from several platforms in one agent workflow.
When should I use TeleKash Oracle MCP?
Use it in Validate when scoping features or narratives and you want Kalshi, Polymarket, and Metaculus-style odds accessible to the agent.
How do I add TeleKash Oracle MCP to my agent?
Add the telekash-mcp-server npm MCP via stdio and set SUPABASE_URL plus SUPABASE_ANON_KEY per the server schema.