Skip to main content
Glama
pmxt-dev

pmxt-mcp

Official
by pmxt-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to pmxt-mcp

No user-submitted related servers found.

    Related Servers

    • predmarket-mcp

      johnsmithxy1mmm-sys
      F
      license
      Not graded
      quality
      B
      maintenance
      A monetizable remote MCP server that provides prediction-market intelligence tools for AI agents, enabling discovery, evaluation, and mispricing detection across venues like Polymarket and Kalshi with per-call payment.
      1
      -

    • Polymarket MCP Server

      joinQuantish
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to trade on Polymarket prediction markets via a self-hosted MCP server, supporting wallet management, order placement, position syncing, and gasless transactions on the Polygon network.
      12 npm
      PolyForm Noncommercial 1.0.0

    • Hunch

      FaustasRi
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes Kalshi prediction markets as tools for AI agents, enabling conversational trading with safety features like demo mode, preview-before-place, and hard caps.
      MIT

    • 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
      68 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.7/5.0

    Scored across 32 tools

    Disambiguation3/5

    Many tools have distinct purposes but several pairs (e.g., fetchMatchedMarkets vs fetchMarketMatches, compareMarketPrices vs fetchMatchedPrices) are closely related and could confuse an agent. Descriptions help but the overlap introduces ambiguity.

    Naming Consistency4/5

    Tool names predominantly follow a 'fetch'+noun pattern for data retrieval and verb+noun for actions. Minor inconsistencies exist (e.g., 'getExecutionPrice' vs 'fetch...', 'compareMarketPrices' vs 'fetchMatchedPrices'), but the overall pattern is clear and predictable.

    Tool Count2/5

    With 32 tools, the server is overloaded. Many fetch variants (e.g., fetchEvents vs fetchEventsPaginated, fetchMarkets vs fetchMarketsPaginated) could be consolidated into fewer tools with optional parameters, reducing cognitive load.

    Completeness4/5

    The tool set covers core trading workflows: order management, market data, account info, and cross-venue matching/arbitrage. Missing an update order tool is a minor gap, but overall the surface supports the intended domain well.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources