polymarket-us-mcp
Related Servers
Alternatives to polymarket-us-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceRead-only MCP server for Polymarket, providing order books, market metadata, and price history via public GET endpoints. It requires no private keys and cannot place trades.5MIT
- 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
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server for Polymarket prediction market data, enabling AI agents to search markets, get details, view holders, leaderboard, and user positions.56 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceProvides read-only access to Polymarket international public market data, including Gamma events and markets, CLOB order books and quotes, and Data API positions, activity, and analytics.MIT
- AlicenseAqualityCmaintenanceA read-only MCP server that lets Claude query Polymarket's public APIs for markets, events, live order books, price history, trades, open interest, trader leaderboards, and wallet positions and P&L. It also offers arbitrage scanning, market "x-ray" reports, calibration scoring, daily digests, and a local simulated paper-trading ledger — with no keys, no signer, and no real orders ever placed.2324 npmMIT
- FlicenseAqualityBmaintenanceAI-agent ready FastMCP server for Polymarket market discovery, wallet analytics, and public CLOB data, providing a read-only interface for querying markets, wallets, and order books.2232 PyPI-
TDQS
Scored across 16 tools
Most tools have clearly distinct purposes: get_bbo provides top-of-book snapshot while get_order_book gives full depth; event_basket and line_ladder_check both target mispricing but at different scopes (event-wide vs line ladders). A couple of tools (e.g., list_events vs search) overlap thematically, but descriptions are specific enough to avoid confusion.
All tools share the pmus_ prefix, and most follow a verb-first convention (get_, list_, search, analyze, scan). However, event_basket and line_ladder_check break the pattern by using noun phrases rather than imperative verbs, which is a minor deviation from an otherwise consistent scheme.
With 16 tools, the server sits at the boundary of the 'heavy' range. Each tool has a distinct data or analysis role, but some reference lists (series, sports, tags) could potentially be consolidated, and the overall count starts to feel cluttered for the apparent scope.
For a read-only market data and analysis API, the coverage is thorough: quoting, order book, event/market retrieval, price history, settlement, plus advanced spread and arbitrage analysis. There are no obvious dead ends or missing operations within the server's stated purpose.