Skip to main content
Glama
storm-mcp

storm-mcp

by xch1tbllc

storm-mcp

将 Storm 跨平台预测市场情报 API 公开给任何模型上下文协议 (MCP) 客户端的 MCP 服务器。

Storm 是一个自主 AI 代理,负责运营 Eyewall Markets,这是一个涵盖 Polymarket、Kalshi、Manifold、Futuur、Betfair、ForecastEx 等平台的跨平台预测市场情报服务。此包是一个轻量级的 stdio MCP 桥接器,允许 LLM 客户端(Claude Desktop、Claude Code、Cursor、Zed 以及任何其他支持 MCP 的主机)将 Storm 的规范事件、跨平台价差、平台目录和用户个人警报收件箱作为原生工具调用进行读取。

它专为已经拥有 Storm 订阅并希望其 LLM 工作区能够看到 Storm 所见内容的分析师、交易员和代理构建者而设计。


需要 Edge 层级

Storm API 仅限 Edge 层级 订阅者(每月 499 美元)使用。请在 https://eyewallmarkets.com/account 生成您的 api_key。较低层级无法访问 API,并且此服务器调用的每个端点都将收到 HTTP 403 错误。

API 密钥格式为 stk_ 后跟 48 个十六进制字符(总共 52 个字符),并绑定到单个账户。请像对待其他持有者凭据一样对待它们。

完整的 API 参考文档位于 https://eyewallmarkets.com/api/docs。


Related MCP server: pmxt-mcp

快速入门 — Claude Desktop

编辑您的 Claude Desktop MCP 配置文件,并在 mcpServers 下添加一个 storm 条目:

{
  "mcpServers": {
    "storm": {
      "command": "npx",
      "args": ["-y", "@eyewallmarkets/storm-mcp"],
      "env": {
        "STORM_API_KEY": "stk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

macOS 路径为:

~/Library/Application Support/Claude/claude_desktop_config.json

Linux: ~/.config/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json。

重启 Claude Desktop。七个 storm_* 工具应出现在任何新对话的工具列表中。


快速入门 — Claude Code

claude mcp add storm npx -- -y @eyewallmarkets/storm-mcp

然后将 API 密钥导出到 Claude Code 启动服务器的环境中(或在您的 shell 配置文件中设置它):

export STORM_API_KEY=stk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

确切的 CLI 调用可能因 Claude Code 版本而异;请参阅 https://docs.claude.com/en/docs/claude-code/mcp 上的官方文档以获取规范形式(包括如何在 mcp add 行本身上传递环境变量)。

安装后,在 Claude Code 中运行 /mcp 以确认 storm 服务器已连接且七个工具已注册。


快速入门 — Cursor

Cursor 从 ~/.cursor/mcp.json 读取 MCP 服务器定义。添加与 Claude Desktop 相同的配置:

{
  "mcpServers": {
    "storm": {
      "command": "npx",
      "args": ["-y", "@eyewallmarkets/storm-mcp"],
      "env": {
        "STORM_API_KEY": "stk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

重新加载 Cursor 的 MCP 集成(设置 → MCP → 刷新)。


快速入门 — Zed

Zed 在 ~/.config/zed/settings.json 中的 assistant.context_servers 下配置 MCP 服务器:

{
  "assistant": {
    "context_servers": {
      "storm": {
        "command": "npx",
        "args": ["-y", "@eyewallmarkets/storm-mcp"],
        "env": {
          "STORM_API_KEY": "stk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
        }
      }
    }
  }
}

重启 Zed 或重新加载助手面板。


配置

所有配置均通过服务器启动时读取的环境变量进行。

变量

必需

默认值

描述

STORM_API_KEY

是

—

Edge 层级 API 密钥,格式为 stk_<48 hex>。没有它,服务器可以启动,但每个工具调用都会失败。

STORM_API_BASE

否

https://eyewallmarkets.com/api/v1

覆盖 API 根路径。对暂存环境或本地开发服务器很有用。

STORM_HTTP_TIMEOUT

否

15000

每次请求的超时时间(毫秒)。

STORM_MCP_LOG_LEVEL

否

info

silent、error、warn、info、debug 之一。日志发送到 stderr,因此它们不会破坏 stdio MCP 传输。


工具参考

所有七个工具都是只读且幂等的。参数形状在下方的 JSON-schema 形式中记录;实时架构是 MCP 客户端实际看到的内容。

storm_list_events

列出规范(跨平台)事件。支持游标分页。

{
  "limit":    { "type": "integer", "default": 50, "max": 200 },
  "cursor":   { "type": "string",  "optional": true },
  "category": { "type": "string",  "optional": true, "example": "politics" },
  "status":   { "type": "string",  "optional": true, "enum": ["open", "closed", "resolved"] }
}

示例提示:“列出 Storm 上接下来的 20 个开放政治事件。”

storm_get_event

通过 slug 获取单个事件,包括所有关联的结果和各平台的报价。

{
  "slug": { "type": "string", "required": true, "example": "us-pres-2028" }
}

示例提示:“拉取 us-pres-2028 的完整 Storm 记录,并告诉我哪个结果具有最宽的跨平台价差。”

storm_list_spreads

列出净优势(扣除费用后)超过底线的近期跨平台价差。按优势降序排列。

{
  "min_edge_bps": { "type": "integer", "default": 100 },
  "limit":        { "type": "integer", "default": 50, "max": 200 },
  "cursor":       { "type": "string",  "optional": true }
}

示例提示:“向我展示目前至少有 250 bps 优势的前 10 个 Storm 价差。”

storm_get_market

通过 (venue_slug, external_id) 查找单个平台/市场记录。

{
  "venue":       { "type": "string", "required": true, "example": "polymarket" },
  "external_id": { "type": "string", "required": true }
}

示例提示:“在 Storm 上查找 Polymarket 市场 0xabc...。”

storm_list_venues

列出 Storm 跟踪的每个平台,包括监管状态(CFTC 注册的 DCM、离岸等)、费用表和能力标志(订单簿、AMM、平分彩)。

{}

示例提示:“Storm 跟踪的哪些平台是 CFTC 注册的 DCM?”

storm_get_alerts_inbox

轮询用户的 API 通道警报收件箱。Edge 订阅者可以将警报路由到 api 交付通道;此工具会清空未确认的队列。

{
  "since": { "type": "integer", "minimum": 0, "optional": true, "example": 4521 }
}

游标是您看到的最后一个警报的整数 id。从上一个响应中传递 next_since 以仅获取较新的警报;省略则从用户持久化的确认游标读取。示例提示:“轮询我的 Storm 收件箱并总结我尚未确认的所有内容。”

storm_ack_alerts

推进持久化确认游标,以便未来的收件箱轮询跳过已处理的警报。游标位于服务器端,并在 MCP 会话之间保持有效。

{
  "up_to": { "type": "integer", "minimum": 0, "required": true, "example": 4530 }
}

示例提示:“确认截至目前的所有 Storm 警报。”


示例记录

查找高优势价差集群

用户: 帮我找到所有优势超过 300 bps 的 2028 年选举 Storm 价差,并告诉我前 3 名。

助手: (调用 storm_list_spreads,参数为 min_edge_bps: 300, limit: 50,按事件 slug 前缀 2028_us_presidential_ 过滤响应,然后对前三个调用 storm_get_event 进行丰富)

返回当前开放的三个最宽的 2028 年选举价差、每一侧的平台对,以及哪个平台处于低价端。

收件箱分类

用户: 轮询我的 Storm 收件箱并总结未确认的警报,然后确认你总结的所有内容。

助手: (调用不带 since 的 storm_get_alerts_inbox,按类别总结项目,然后调用 up_to 设置为它看到的最大的 id 的 storm_ack_alerts)

返回未确认警报的分类摘要(价差优势交叉、平台状态更改、解析事件)并确认游标推进,以便后续轮询仅返回新项目。


速率限制和错误处理

Storm API 在服务器端强制执行 每个 API 密钥每秒 10 次请求。如果您超过该限制,服务器将返回带有 Retry-After: 1 的 HTTP 429。此 MCP 桥接器不会自动重试;它将错误作为工具结果中的纯文本内容呈现给 LLM,以便模型可以决定是退避、重试还是放弃。

错误以这种形式返回给 LLM(工具结果上的文本内容,isError: true):

Storm API error (HTTP 429, rate_limited): too many requests Retry after 1000 ms.
Storm API error (HTTP 403, edge_tier_required): edge_tier_required
Storm API error (HTTP 401, invalid_credentials): invalid_credentials

网络级故障(DNS、TCP、TLS、超时)显示为:

Storm API error (HTTP 0, transport): request timeout

完整的 HTTP 状态、Storm 错误代码和人类可读的消息始终包含在内,以便 LLM 可以据此采取行动。


开发

git clone https://github.com/lsudduth/storm-mcp.git
cd storm-mcp
npm install
npm test

通过覆盖 API 根路径指向本地 Storm 开发服务器:

STORM_API_BASE=http://localhost:8080/api/v1 \
STORM_API_KEY=stk_dev_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx \
node src/index.mjs

服务器使用 stdio MCP,因此您可以使用任何 MCP 测试工具直接驱动它,或者手动通过管道传输 JSON-RPC 帧。

测试使用 Node 内置的测试运行器;没有 Jest,没有 Vitest,没有转译器。


许可证

MIT — 参见 LICENSE。

© 2026 XCH1TB, LLC dba Eyewall Markets。

Storm 本身——运营 Eyewall Markets 并生成此服务器所公开数据的自主 AI 代理——是一个独立的内部代码库。此包仅是通往 Storm 公共只读 API 表面的面向客户端的 MCP 桥接器。


免责声明

本软件及其呈现的数据仅供 参考。Storm 或此 MCP 服务器返回的任何内容均非法律、财务、税务或投资建议。参与预测市场受您当地法律和平台自身资格规则的约束;特别是,Polymarket 在美国受 CFTC 命令限制,大多数美国人无法使用。平台资格是您的责任,而不是 Storm 或本服务器的责任。 Storm 聚合了可公开观察的市场状态,不会代表您进行交易。

Available Tools

7 tools
storm_ack_alertsA

Advance the persistent ack cursor to the given sequence id, removing items at or below it from the api-channel inbox. Call this after the LLM / agent has processed items returned by storm_get_alerts_inbox; otherwise the same items will keep being returned. Sourced from Eyewall Markets / Storm. The cursor is server-side and survives across MCP sessions.

Inputs: up_to (required).

storm_get_alerts_inboxA

Poll the subscriber's api-channel notification inbox for cross-venue price-difference and event notifications that haven't been ack'd yet. Each item is a descriptive notification — it names the canonical event, the two venues, the prices each venue was publishing at the observation timestamp, and the rule that matched. Sourced from Eyewall Markets / Storm. Pass the next_since returned by the previous call as since to get only newer items. After processing, call storm_ack_alerts to advance the persistent cursor.

Inputs: since.

storm_get_eventA

Fetch a single canonical event by its Storm slug, including the full set of cross-venue markets attached to that event and each venue's currently published price. Use after storm_list_events when you need the canonical question text, resolution criteria, and per-venue market handles. Sourced from Eyewall Markets / Storm; describes the published-price observation, not a buy or sell recommendation.

Inputs: slug (required).

storm_get_marketA

Fetch the canonical Storm view of a single market on a specific venue, including the venue's currently published bid/ask, volume, and the canonical event it's joined to. Use when you have a venue + the venue's native market id (e.g. a Kalshi ticker or Polymarket condition id) and want Storm's normalized representation. Sourced from Eyewall Markets / Storm; describes published price snapshots from the venue's public read endpoints, not a recommendation.

Inputs: venue (required), external_id (required).

storm_list_eventsA

List canonical prediction-market events (questions/topics) tracked by Eyewall Markets / Storm across the public venues it covers (Kalshi, Polymarket, Manifold, ForecastEx, and others). Use this to discover what events exist before drilling into a specific event with storm_get_event. Supports filtering by category (e.g. 'politics', 'economics') and status (e.g. 'open', 'resolved'), and is cursor-paginated. Read-only market reference data; describes the event ontology, not a recommendation.

Inputs: limit, cursor, category, status.

storm_list_spreadsA

List recent cross-venue published-price observations — pairs of markets on different venues that are publishing different prices for the same canonical outcome. Returns rows whose published-price difference net of each venue's posted fees clears the configured floor, ordered by net_edge_bps DESC. Sourced from Eyewall Markets / Storm. Descriptive market-data only: each row reports what each venue is publishing, not a buy or sell recommendation, and does not warrant fillable depth at any price reported.

Inputs: min_edge_bps, limit, cursor.

storm_list_venuesA

List all public prediction-market venues covered by Eyewall Markets / Storm, with their slugs, display names, regulatory posture (CFTC-registered DCM, offshore, etc.), posted fee schedules, capability flags (orderbook / AMM / parimutuel), and current ingestion status. Call this first when you need the venue slug to pass to storm_get_market. Reference data only — venue eligibility for any individual user is governed by the venue and the user's local law.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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 recent community issues

    Related MCP Connectors

    Related MCP Servers

    • 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
      18 PyPI
      MIT
    • 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
      8
      MIT