Skip to main content
Glama
phon3

graph-polymarket-mcp

by phon3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to graph-polymarket-mcp

No user-submitted related servers found.

    Related Servers

    • graph-polymarket-mcp

      PaulieB14
      A
      license
      B
      quality
      B
      maintenance
      An MCP server that enables querying Polymarket prediction market data through The Graph subgraphs. It provides tools for accessing market stats, trader P\&L, user positions, and orderbook activity using AI agents.
      35
      68 npm
      4
      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.
      35 PyPI
      MIT

    • @igoforth/polymarket-mcp

      igoforth
      A
      license
      C
      quality
      D
      maintenance
      MCP server exposing 47 Polymarket API tools for AI assistants. Covers the full Gamma, CLOB, and Data APIs plus a fluent MarketBuilder for multi-source queries.
      47
      10 npm
      2
      MIT

    • Polymarket MCP Server

      Franzferdinan51
      A
      license
      A
      quality
      D
      maintenance
      MCP server for Polymarket prediction markets, enabling search, market details, pricing, and bet analysis through 6 tools, with optional authenticated trading via API key.
      6
      30 npm
      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 32 tools

    Disambiguation3/5

    Several tools have overlapping purposes (e.g., get_market_data vs get_market_info, search_markets vs search_markets_enriched, and the multiple live CLOB tools). Descriptions help differentiate them, but misselection is still possible.

    Naming Consistency4/5

    Most tools follow a get_ prefix with snake_case (e.g., get_market_resolution, get_live_orderbook), but a few use search_, list_, or query_, and search_markets_enriched adds an inconsistent suffix. The pattern is mostly consistent but has deviations.

    Tool Count2/5

    32 tools is excessive for a single server. Many tools are excessively granular (e.g., get_live_prices, get_live_spread, get_live_orderbook, get_last_trade could be one tool with parameters), making the surface feel bloated.

    Completeness4/5

    The server covers the main needs of Polymarket data consumers: market discovery, live order book, trader analytics, resolution status, and platform stats. Minor gaps exist (e.g., per-trader trade history), but the core is solid.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources