Skip to main content
Glama
fernandezpablo85

Polymarket MCP Tool

by fernandezpablo85
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Polymarket MCP Tool

No user-submitted related servers found.

    Related Servers

    • Polymarket MCP

      ozgureyilmaz
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server for Polymarket prediction markets, providing real-time market data, prices, and AI-powered analysis tools for Claude Desktop integration.
      48
      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.
      30 npm
      MIT

    • kalshi-mcp-server

      cejor6
      A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol server for Kalshi prediction markets, enabling LLMs to query markets, prepare and confirm orders with safety caps and rate limiting.
      165 PyPI
      3
      MIT

    • polymarket-mcp

      amerilain
      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
    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.8/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have distinct primary purposes: getting trending topics, fetching markets by topic, and searching markets by term. However, there is some functional overlap between `prediction_markets_markets_by_topic` and `search_prediction_markets` as both return market data, which could cause minor confusion about when to use each.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with a clear `prediction_markets_` prefix and descriptive suffixes (`trending_topics`, `markets_by_topic`, `search_prediction_markets`). The naming is predictable and follows a logical structure throughout.

    Tool Count3/5

    With only 3 tools, the server feels somewhat thin for a prediction markets domain. While the tools cover basic discovery and search functionality, the limited count suggests potential gaps in comprehensive market interaction capabilities that might be expected from such a service.

    Completeness3/5

    The tools provide good discovery and search capabilities but lack any market interaction functions (like placing bets, viewing user positions, or managing portfolios). For a prediction markets server, this represents notable gaps in the full lifecycle of market participation, though the provided tools work well together for information gathering.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources