Skip to main content
Glama

Related Servers

Alternatives to nodusai-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Real-time prediction market intelligence for AI agents. Query Polymarket and Kalshi markets, wallet profiles, smart money leaderboards, social pulse signals, price candlesticks, and orderbook data — 13 agents, one MCP connection. Powered by 1.1TB+ of historical data.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Prediction market probability oracle for AI agents. 26 tools across 500+ live markets from Kalshi and Polymarket. Cross-source arbitrage detection, structured TPF signals, Kelly Criterion sizing, agent performance tracking, and webhook alerts.
      9
      27 npm
      1
      MIT
    • 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.
      21
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Prediction market intelligence for AI agents, enabling real-time access to whale trades, market data, signals, and AI-synthesized analysis from Kalshi and Polymarket via a standardized protocol.
      -
    • 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
      -
    • A
      license
      A
      quality
      C
      maintenance
      MCP server providing Polymarket weather-market bucket-transition signals for AI agents, with free city/signal inspection tools and paid signal bundles via USDC on Base using x402.
      5
      9 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have distinct purposes: admin queries vs. admin stats, get_signal vs. verify_signal, pricing vs. query history. However, 'nodus_admin_queries' and 'nodus_admin_stats' could be slightly confused as both provide administrative data, though their specific focuses differ.

    Naming Consistency5/5

    All tool names follow a consistent 'nodus_' prefix with descriptive suffixes in snake_case, such as 'nodus_admin_queries', 'nodus_get_signal', and 'nodus_verify_signal'. This pattern is uniform across all six tools, making them predictable and easy to identify.

    Tool Count5/5

    With 6 tools, the server is well-scoped for its purpose of providing Oracle signals and related administrative and historical functions. Each tool serves a clear role without unnecessary bloat, covering core operations like signal retrieval, verification, pricing, and history.

    Completeness4/5

    The tool set covers key aspects: signal retrieval, verification, pricing, query history, and admin functions. A minor gap is the lack of a tool for managing session tokens or handling payments directly, but agents can work around this using the provided pricing and signal tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues