Skip to main content
Glama
igoforth

@igoforth/polymarket-mcp

by igoforth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @igoforth/polymarket-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      77 npm
      MIT

    • CryptoConduit-MCP

      chxndre
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives AI agents direct access to Polymarket Crypto prediction markets, enriched with live spot prices. Discover markets, analyze order books, paper trade strategies, track activity, and execute live trades — all through natural language.
      1
      AGPL 3.0

    • 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
      22 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.
      22 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

    C2.6/5.0

    Scored across 47 tools

    Disambiguation2/5

    Many tools have unclear boundaries. For example, get_tags_related_to_tag and get_related_tags appear to do the same thing, and get_sampling_markets vs get_sampling_simplified_markets are nearly identical. Price-related tools (get_prices, get_midpoint, get_spreads) also overlap significantly.

    Naming Consistency3/5

    The naming pattern is mixed: some tools use list_ (list_markets, list_comments), others use get_ (get_event, get_market_tags), and a few use neither (query_markets, public_search). While most names are readable, the inconsistency makes the API less predictable.

    Tool Count2/5

    With 47 tools, the server feels overloaded. Many are minor variations (e.g., get_sampling_markets vs get_sampling_simplified_markets, get_related_tags vs get_tags_related_to_tag) that could be merged or removed. The large count increases cognitive load without clear added value.

    Completeness4/5

    The server covers a broad range of Polymarket data: events, markets, prices, user positions, comments, tags, sports, and builder analytics. It is almost entirely read-only, which seems intentional, and lacks only minor convenience features like batch queries or combined endpoints.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources