polyorderbooks
Related Servers
Alternatives to polyorderbooks
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceReference 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.3MIT
- AlicenseAqualityCmaintenanceA 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.14MIT
- AlicenseNot gradedqualityAmaintenanceRead-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 freshnessMIT
- AlicenseNot gradedqualityCmaintenanceEnables querying Polymarket prediction market data, including top active markets and order books, without an API key or database.22 npm1MIT
- AlicenseAqualityDmaintenancePolymarket prediction markets for Claude — market search, order books, price history, and a liquidity-rewards scanner. Credential-free.623 npmMIT
- AlicenseBqualityDmaintenanceEnables 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.221MIT
TDQS
Scored across 8 tools
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.
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.
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.
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.