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
      C
      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
      227 PyPI
      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

    B3/5.0

    Scored across 30 tools

    Disambiguation3/5

    Core trading tools are mostly distinct, but there is real overlap between get_balance and portfolio (both surface positions and P&L), and the cluster of stats_card, leaderboard_card, pk_card, leaderboard_entry, and share_content all produce shareable performance content. Descriptions help, but an agent could easily choose the wrong analytics/presentation tool.

    Naming Consistency3/5

    There are consistent subfamilies like get_market/get_order_book/get_event and list_orders/cancel_order/cancel_all_orders, but the overall set mixes bare verbs (buy, sell, resolve), nouns (portfolio, history, stats), and noun_noun compounds (leaderboard_card, pk_battle). No single naming convention governs the full surface.

    Tool Count2/5

    With 30 tools, the server is over-scoped for a paper trading tool; many of the card/share/leaderboard tools could be consolidated into fewer general-purpose tools. The core trading functionality is solid, but the surface feels padded with social and vanity-format variants.

    Completeness4/5

    The paper trading lifecycle is well covered: account init/reset/balance, market data, market orders, limit orders, positions/history, resolution, and backtesting. Minor gaps exist such as no deposit/withdraw or order modification, but agents can complete real trading workflows without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources