MarketMaster MCP server
Which servers in the official MCP registry are MarketMaster's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-10
- Registry namelive.marketmaster/mcpverified in the MCP registry
The registry name sits under marketmaster.live. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-10
- Tools6
- Server calls itselfmarketmaster
- Server version0.1.2
- Protocol version2025-06-18
On 2026-10-10 the server answered initialize and tools/list without a sign-in. First answer in 534 ms.
mm_edgesMispriced prediction-market edges (model fair value vs live price), ranked by edge size, across Kalshi and Polymarket.
mm_marketsLatest normalized market snapshots across venues (title, YES/NO price, 24h volume, close time).
mm_marketA single market's latest snapshot plus any live edges for it.
mm_arbitrageCross-platform price spreads for matched markets — buy-cheap / sell-dear venue per outcome. Indicative, gross of fees and slippage; not guaranteed arbitrage.
mm_whalesRecent large real-money trades (whale fills) across venues, newest first.
mm_statusYour API key's tier, rate limits, and current usage.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"marketmaster": {
"type": "http",
"url": "https://api.marketmaster.live/mcp"
}
}
}Also shipped through: npm
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.