Skip to main content
Glama
xch1tbllc

storm-mcp

by xch1tbllc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to storm-mcp

No user-submitted related servers found.

    Related Servers

    • pmxt-mcp by pmxt-dev

      pmxt-mcpofficial

      pmxt-dev
      A
      license
      C
      quality
      D
      maintenance
      MCP server that provides a unified prediction market API for multiple venues like Polymarket and Kalshi, allowing AI agents to discover markets, fetch order books, and execute trades through a single interface.
      32
      315 npm
      8
      MIT

    • @igoforth/polymarket-mcp

      igoforth
      A
      license
      C
      quality
      D
      maintenance
      MCP server exposing 47 Polymarket API tools for AI assistants. Covers the full Gamma, CLOB, and Data APIs plus a fluent MarketBuilder for multi-source queries.
      47
      16 npm
      2
      MIT

    • AltSportsData MCP Server

      asd-git-master
      A
      license
      B
      quality
      D
      maintenance
      MCP-compatible server that gives AI agents access to alternative sports data across 30+ leagues — odds, events, probabilities, settlement, and futures for prediction markets, DFS platforms, and sportsbooks.
      29
      16 npm
      MIT

    • oracle3

      YichengYang-Ethan
      A
      license
      A
      quality
      A
      maintenance
      Prediction-market MCP server for Kalshi and Polymarket: market search, live order books and quotes, each venue's fee schedule, fee-aware no-arbitrage checks across related event contracts, and paper orders that walk the book.
      2
      13
      204 PyPI
      367
      Apache 2.0
    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

    A4.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource: acking alerts, polling inbox, fetching events/markets, listing events/spreads/venues. No two tools have overlapping purposes, and descriptions clearly differentiate them.

    Naming Consistency5/5

    All tools follow a consistent 'storm_verb_noun' pattern in snake_case, with verbs like ack, get, list. This makes it easy for an agent to infer functionality from names.

    Tool Count5/5

    7 tools is a well-scoped set for a prediction market data server. Each tool serves a necessary function without unnecessary duplication or gaps, covering discovery, detailed queries, and notification management.

    Completeness5/5

    The tool set covers the full lifecycle: discovering events (list), drilling into details (get), accessing markets (get), monitoring spreads and alerts, acknowledging alerts, and listing venues. No obvious missing operations for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources