Skip to main content
Glama
kingmadellc

Prediction Market MCP

by kingmadellc

Related Servers

Alternatives to Prediction Market MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Prediction-market quant tools — expected value, Kelly sizing, Bayesian updating, odds conversion, base-rate gaps, cross-platform arbitrage, and mispricing edge — for Kalshi and Polymarket contracts, exposed as a remote MCP server.
      2
      6
      5 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Exposes a machine-callable proof-market surface for agents to submit proof requests, monitor market state, compare coordination regimes, and compose multi-step workflows with no human in the loop.
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides prediction-market data as MCP tools, including live prices, keyword search, probability history, volume spikes, arbitrage gaps, and resolutions. Pay per call in USDC on Base with no API key or signup.
      11 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables querying consolidated Bitcoin pricing, ML signals, funding skew, and market briefings via the BPE API, without HTTP boilerplate.
      5
      17 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      21
      522 PyPI
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables interaction with the PolyMarket API to fetch prediction market data such as market information, prices, and historical data, with robust error handling and rate limit management.
      4
      142
      MIT

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a distinct primary purpose: estimate for single-question probability, size for position sizing, scan for ranking multiple markets, ensemble for a full pipeline, and info for service details. However, ensemble overlaps with estimate and size by including them, which could confuse agents choosing between atomic and composite options.

    Naming Consistency5/5

    All tools follow the same snake_case pattern with a consistent 'prediction_market_' prefix followed by a clear action or noun (estimate, size, scan, ensemble, info). This makes the set highly predictable and readable.

    Tool Count5/5

    Five tools is well-scoped for a prediction market analysis service, with each tool earning its place by covering a distinct step in the workflow from information to estimation, sizing, scanning, and full pipeline execution.

    Completeness4/5

    The surface covers the core analysis lifecycle: service info, single-market estimation, position sizing, multi-market scanning, and an ensemble pipeline. Minor gaps exist around raw market data retrieval or trade execution, but agents can work around these for the stated analysis purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues