Skip to main content
Glama

Related Servers

Alternatives to polyorderbooks

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Reference data layer for prediction markets: resolution-clarity grades (A/B/C), named resolution sources with provenance, cross-venue linking, and per-contract eligibility screens across Kalshi and Polymarket. Open,read-only, no key required.
      3
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server exposing Polymarket's public prediction-market data. Search markets, read live odds and order books, pull historical probability time-series, and inspect public wallet positions.
      14
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Read-only crypto perps microstructure for AI agents: normalized cross-exchange market state (funding + multi-year percentile, OI, volume, CVD, order-book imbalance, liquidations, basis), OHLCV, 15-min state history, and measured conditional outcomes (historical base rates, not predictions) — 6 assets across Binance, Bybit, OKX and Hyperliquid, every metric with self-declared coverage and freshness
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Polymarket prediction market data, including top active markets and order books, without an API key or database.
      22 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Polymarket prediction markets for Claude — market search, order books, price history, and a liquidity-rewards scanner. Credential-free.
      6
      23 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables comprehensive read access to Polymarket prediction market data, including live prices, order books, and market statistics. It allows AI assistants to analyze events, search markets, and monitor real-time signals without requiring API keys or authentication.
      22
      1
      MIT

    TDQS

    A4.1/5.0

    Scored across 8 tools

    Disambiguation4/5

    The three search_* tools target distinct entities (individual markets, recurring series, and event groupings), and the descriptions clarify which search to start with, but an agent could still hesitate between search_series and search_events for some workflows. The get_* tools are clearly separated by data type: order book depth, price series, and derived metrics.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: search_* for discovery and get_* for retrieval. There is no mixed casing, vague verb, or off-pattern name.

    Tool Count5/5

    With eight tools, the server is well-scoped: discovery tools for each Polymarket entity, one market detail tool, three historical data tools, and one usage-account tool. Each tool fills a distinct role.

    Completeness4/5

    The read-only analytics workflow is well covered: find a market, expand to series or events, inspect a market, and then retrieve price, orderbook, or quality time series. A minor gap is the lack of an explicit current-orderbook snapshot endpoint, though historical snapshots and market detail cover most needs.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues