Skip to main content
Glama
PaulieB14

graph-polymarket-mcp

Related Servers

Alternatives to graph-polymarket-mcp

Related Servers

  • 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
    68 npm
    MIT
  • 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
  • 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
  • A
    license
    B
    quality
    C
    maintenance
    MCP server for Polymarket prediction markets enabling query of markets, events, narratives, arbitrage, and more via MCP or HTTP.
    9
    MIT
  • A
    license
    C
    quality
    C
    maintenance
    MCP server that provides a unified prediction market API for multiple venues like Polymarket and Kalshi, allowing AI agents to discover markets, fetch order books, and execute trades through a single interface.
    32
    262 npm
    8
    MIT

TDQS

B3.4/5.0

Scored across 35 tools

Disambiguation2/5

Several tools have overlapping purposes, such as get_market_data, get_market_info, and search_markets, or get_live_prices, get_live_spread, get_last_trade, and get_clob_market. While descriptions do provide some differentiation, the boundaries remain unclear, especially between search_markets and search_markets_enriched, or get_global_stats and get_global_open_interest.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case (e.g., get_market_info, search_markets, check_subgraph_freshness). There are no deviations in style, making the naming predictable and coherent.

Tool Count2/5

With 35 tools, the server is overstuffed. While the scope (multiple subgraphs, CLOB, Gamma API) might justify a larger surface, it exceeds the typical 3-15 range and feels heavy. Many tools could be consolidated or removed without loss.

Completeness4/5

The tool set is extremely comprehensive, covering market data, CLOB order books, user positions, P&L, open interest, resolution status, and even custom subgraph queries. Minor gaps exist, such as no direct way to fetch a specific market's full trade history, but overall the domain is well covered.

Maintenance

ActivitySlowing
ResponsivenessNo issues