Skip to main content
Glama
amerilain

polymarket-mcp

by amerilain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to polymarket-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

    • graph-polymarket-mcp

      phon3
      A
      license
      B
      quality
      C
      maintenance
      MCP server to query Polymarket prediction market data via The Graph subgraphs and REST APIs, enabling AI agents to search markets, get live prices, order books, on-chain analytics, and trader profiles.
      32
      63 npm
      MIT

    • Polymarket MCP Server

      yashhsm
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables seamless integration with Polymarket, providing tools to search markets, fetch events, analyze leaderboards, query user activity, and more via MCP-compatible clients like Claude.
      17 npm
      MIT

    • Polymarket MCP

      0xChron
      A
      license
      Not graded
      quality
      D
      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
    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

    B3.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: detection of volume spikes, arbitrage, specific market details, events listing, narrative clustering, ecosystem summary, keyword search, top markets by volume, and top movers. No two tools overlap in functionality, so an agent can easily distinguish them.

    Naming Consistency4/5

    Seven out of nine tools follow a consistent verb_noun pattern (e.g., detect_volume_spikes, get_market, search_markets). Two tools, market_narratives and market_summary, use a noun_noun format, which is a minor deviation but still clear.

    Tool Count5/5

    With 9 tools, the server provides a broad yet focused set of functionalities for analyzing Polymarket prediction markets. The count is well-scoped for a single-purpose server, neither too few nor too many.

    Completeness5/5

    The tools cover key analytical tasks for Polymarket: searching, listing, summarizing, detecting anomalies, and identifying opportunities. For a read-only analysis server, the surface is complete; adding betting or account tools would shift scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources