PolyOrderbooks MCP Server
OfficialRelated Servers
Alternatives to PolyOrderbooks MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables access to historical Polymarket order book depth, with full L2 bid and ask ladders at 1-second resolution and resolved outcomes, for use in MCP clients like Claude and Cursor.824 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.1432 PyPIMIT
- 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.824 npmMIT
- AlicenseAqualityBmaintenanceA read-only MCP server for EdgeDepth's market microstructure search engine, enabling users to query recorded crypto and TradFi perpetuals for market conditions, outcomes, and reproducibility-keyed evidence directly from MCP clients.10106 npm3MIT
- AlicenseAqualityBmaintenanceProvides read-only access to Polymarket US public market data, including prices, order books, and spread/fee analytics, via MCP tools.16MIT

oyapicks-mcpofficial
AlicenseNot gradedqualityCmaintenanceProvides 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.46 npmMIT
TDQS
Scored across 8 tools
The three search tools (search_markets, search_series, search_events) form a clearly explained hierarchy of market vs. series vs. event, and the three history tools target distinct data (prices, L2 order book depth, derived metrics). Boundaries are mostly clear, though search_markets/search_series and the trio of get_*_history/metrics tools could still be conflated at a glance since they all return time-series data.
All eight names follow a strict snake_case verb_noun pattern with a consistent get_/search_ prefix split. The pattern is predictable and readable throughout.
Eight tools is well within the ideal range and each earns its place: a search hierarchy, per-market detail, three distinct history/metric tools, and a usage check. Nothing feels redundant or padded.
The surface covers the full read path for a market-data server: discovery (markets/series/events), market detail with token ids, price history, order book depth, quality metrics, and account limits. Read-only is appropriate for this analytics domain, so no create/update/delete gaps are meaningful.