Skip to main content
Glama
Sign In
chand1012

Polymarket US MCP server

by chand1012
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Polymarket US MCP server

No user-submitted related servers found.

    Related Servers

    • Polymarket MCP Server

      AStheTECH
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
      -

    • polymarket-mcp

      fzlzjerry
      A
      license
      A
      quality
      C
      maintenance
      A 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.
      14
      MIT

    • Kalshi MCP Server

      yakub268
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to search, analyze, and trade on Kalshi prediction markets directly through MCP-compatible clients. It supports portfolio management, market data retrieval, and limit order execution with production-grade authentication and rate limiting.
      20 PyPI
      1
      MIT

    • polymarket-us-mcp

      anjavera
      A
      license
      A
      quality
      B
      maintenance
      Provides read-only access to Polymarket US public market data, including prices, order books, and spread/fee analytics, via MCP tools.
      16
      MIT

    • polymarket-info

      wtfsayo
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides 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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 58 tools

    Disambiguation2/5

    The set contains many overlapping read tools: get_sports vs get_all_sports, get_events vs get_events_by_sport_slug/get_events_by_league_slug/get_events_for_a_tag, and get_price_history vs the bucketed OHLC tool. Descriptions add parameters, but an agent still faces multiple near-duplicate retrieval paths and must infer which variant to use.

    Naming Consistency4/5

    Most names use snake_case with a clear verb (get_, create_, cancel_, modify_, delete_), which is predictable. There are minor deviations such as the extremely long get_a_bucketed_ohlc... name and inconsistent 'all' qualifiers (get_sports vs get_all_sports), but not mixed casing/styles.

    Tool Count1/5

    58 tools is an extreme overload for an MCP surface; the calibration explicitly treats 50+ tools as a mismatch. Many retrieval variants and batch/lifecycle operations could be consolidated or exposed via parameters.

    Completeness4/5

    The surface covers the domain broadly: events/markets/series/sports/tags, price history/OHLC, order lifecycle (create/preview/modify/cancel/batch), RFQs/quotes/combos, and account/positions/activities/balances/incentives. Minor gaps remain around some alternate lookup keys and post-trade/order-history specifics, but core workflows are represented.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources