Skip to main content
Glama
Speccy-Agent

x402-mcp

by Speccy-Agent

Related Servers

Alternatives to x402-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      228 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to access crypto prices, DeFi yields, Polymarket data, Base chain info, and security scans with pay-per-call via USDC on Base mainnet.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to query live Polymarket and Kalshi odds, price history, movers, resolved and closing markets, cross-platform gaps, watch-based change tracking, and X/Twitter sentiment in a single call, paying per request in USDC on Base via x402. Also surfaces ticker-linked event markets and a free example call so agents can inspect results before spending.
      23 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to query Polymarket data such as top wallets, live trades, market details, and smart money flows using natural language through MCP tools.
      MIT
    • 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
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to discover and analyze prediction markets, execute trades, and manage positions on Polymarket via the Model Context Protocol.
      7
      43 npm
      20
      MIT

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are completely distinct in purpose: one fetches Polymarket prediction markets, the other executes Python code. There is no realistic risk of an agent confusing them.

    Naming Consistency5/5

    Both tool names follow the same lowercase snake_case verb_noun pattern: get_prediction_markets and exec_python. The naming is predictable and consistent.

    Tool Count3/5

    Two tools is on the thin side, and the tools are unrelated, making the server feel like a loose collection rather than a focused toolkit. The count is not unreasonable for a paid utility server, but it is borderline.

    Completeness2/5

    The tools have no shared domain and each is a single isolated operation. get_prediction_markets only returns top markets with no drill-down or follow-up actions, and exec_python is a one-off sandbox execution primitive. The broader x402 workflow is unclear, leaving significant gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive