Polymarket Gamma MCP Server
Related Servers
Alternatives to Polymarket Gamma MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables interaction with Polymarket prediction markets through read-only access to market data, events, orderbooks, and user positions, plus authenticated trading capabilities for creating and managing orders.1-
- AlicenseNot gradedqualityCmaintenanceProvides read-only market data for the CFTC-regulated Polymarket US prediction-market exchange, enabling keyword search and category browsing of markets along with top-of-book quotes, full order-book depth, historical Yes/No price series, and final settlement prices. All lookups are keyless and operate on market slugs, with every response tagged by venue and data timestamp so results are never confused with other prediction-market platforms.15 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables access to Polymarket's prediction markets for analyzing market probabilities, trading activity, and event outcomes across politics, sports, crypto, and other categories through natural language queries.26 npm10MIT
- AlicenseNot gradedqualityDmaintenanceEnables querying Polymarket prediction market data, including top active markets and order books, without an API key or database.26 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query Polymarket prediction markets, accessing real-time odds, market data, price history, order books, and trending markets across categories like politics, crypto, and sports through natural language.26 npm7MIT
- 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
Most tools are distinct: trending, category, search, details, events, event details, API usage. However, get_events and get_sports_events overlap somewhat, though the descriptions clarify sports is a subset. Search and category are clearly different. Overall, boundaries are mostly clear.
All tools follow the consistent pattern of 'get_' + noun, with clear nouns like 'trending_markets', 'market_details', 'events', etc. No mixed conventions or unexpected verbs.
8 tools are well-scoped for a read-only market data server. Each covers a distinct query type, and none feel redundant or excessive.
The surface covers market retrieval (trending, by category, search), market details, event listings and details, and API usage. Minor gaps like historical price data or market resolution info exist, but core read-only workflows are complete.