Skip to main content
Glama
agent-next

polymarket-paper-trader

by agent-next
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to polymarket-paper-trader

No user-submitted related servers found.

    Related Servers

    • Polymarket MCP Server

      prudenteye
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to autonomously trade, analyze, and manage positions on Polymarket prediction markets with 45 tools, real-time WebSocket monitoring, and enterprise-grade safety features.
      MIT

    • Alpha MCP

      Ghost-Network666
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a comprehensive set of tools for Polymarket prediction market trading, including Gamma discovery, CLOB trading, gasless relayer, managed WebSockets, and paper simulation, enabling agents to interact with Polymarket natively.
      MIT

    • oddsrail

      hmesutozsoy
      A
      license
      B
      quality
      A
      maintenance
      Enables MCP-compatible AI agents to research and trade prediction markets on Polymarket and Kalshi, including market search, orderbooks, price history, positions, order routing, and on-chain builder-code attribution, plus overshoot and dispute-risk signals.
      42
      134 PyPI
      1
      MIT

    • Polymarket MCP Server

      Arjein
      A
      license
      B
      quality
      D
      maintenance
      Enables LLM agents to interact with Polymarket prediction markets, including market discovery, real-time pricing, analytics, account management, and trading with built-in safety guards.
      34
      MIT

    • actually-mcp-server

      Sofiia7
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to check news against live Polymarket markets, retrieve market odds, and manage trades including placing, selling, and canceling orders.
      2
      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.9/5.0

    Scored across 33 tools

    Disambiguation4/5

    Descriptions are unusually explicit about cross-references (use X for Y), which cleanly separates most tools like search_markets/list_markets/get_markets_by_tag and stats/stats_card/leaderboard_entry. The main ambiguity is redundant Kalshi tools (kalshi_market, kalshi_book) whose output is already reachable via get_market/get_order_book with 'kalshi:<TICKER>', and the cluster of stat-card variants that overlap in purpose.

    Naming Consistency3/5

    Many tools follow verb_noun snake_case (get_balance, search_markets, place_limit_order, cancel_all_orders, resolve_all), but the set mixes in bare verbs (buy, sell, backtest, resolve) and noun/fragment names (stats_card, pk_battle, leaderboard_entry, share_content). It stays readable but there is no single predictable pattern.

    Tool Count3/5

    33 tools is heavy for this scope, and a noticeable cluster is reporting-oriented variants (stats, stats_card, leaderboard_entry, leaderboard_card, share_content, pk_card, pk_battle) that could arguably be consolidated. The broad domain (discovery, trading, accounts, analytics, social) justifies many of them, but the surface feels larger than necessary.

    Completeness4/5

    Coverage is strong: account lifecycle (init_account/reset_account/get_balance), market discovery across both venues, full order lifecycle (buy, sell, place_limit_order, list/cancel/check), portfolio/history, stats, and settlement (resolve/resolve_all). Minor gaps only, such as no order-modify/deposit operation, but these are easily worked around with existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources