Skip to main content
Glama
anjavera

polymarket-us-mcp

by anjavera
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to polymarket-us-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • Polymarket MCP

      0xChron
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server for Polymarket prediction market data, enabling AI agents to search markets, get details, view holders, leaderboard, and user positions.
      57 PyPI
      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

    • polymarket-mcp

      pr1m8
      F
      license
      A
      quality
      B
      maintenance
      AI-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.
      22
      -

    • polymarket-mcp

      pab1it0
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query Polymarket prediction markets and analyze market data through the MCP interface.
      8
      -
    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

    A3.7/5.0

    Scored across 16 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources