PolyOrderbooks MCP Server
Related Servers
Alternatives to PolyOrderbooks MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP clients to query historical Polymarket order book depth at 1-second resolution, including full L2 bid and ask ladders with resolved outcomes, alongside market search, price history, and liquidity metrics. It also exposes depth data that Polymarket's own API does not archive, letting users analyze what could actually have been traded at a specific past moment.88 npmMIT
- AlicenseAqualityAmaintenanceHistorical Polymarket order book depth — full L2 bid/ask ladders at 1-second resolution on resolved markets, plus prices, spread and liquidity. Polymarket archives no order book history, so this serves depth captured live.88 npmMIT
- 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.1435 PyPIMIT
- AlicenseAqualityBmaintenanceProvides read-only access to Polymarket US public market data, including prices, order books, and spread/fee analytics, via MCP tools.16MIT
- 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
- AlicenseBqualityBmaintenanceRead-only Hyperliquid data for AI agents: trades, fills, candles, funding, open interest, liquidations, wallet analytics and 12 months of fill history.32196 npmMIT
TDQS
Scored across 8 tools
Each tool targets a distinct entity or data type: search_markets, search_series, and search_events operate at different granularities of Polymarket structure, and the get_* tools cleanly separate market detail, order book depth, price history, metrics, and usage info. The descriptions explicitly call out when to use one search tool over another, so an agent should not confuse them.
All tool names follow a consistent snake_case verb_noun pattern: search_* for discovery and get_* for retrieval. There is no mixing of camelCase, bare verbs, or inconsistent naming styles.
Eight tools is well-scoped for a read-only historical data server: three search tools for navigation, four retrieval tools for different data dimensions, and one usage/limits tool. Every tool has a clear role and none feels redundant.
The server covers the full exploration workflow: search series/events/markets, get market detail, then fetch order book history, price history, or derived metrics. It also includes a usage tool for rate-limit planning, and the search tools handle closed/resolved markets for historical analysis, leaving no obvious dead ends.