
Orcalayer Mcp
io.github.orcalayer由 GitHub 账号 orcalayer 发布v0.3.2更新于 Oct 24, 2026
Polymarket smart-money analytics: whale leaderboard, wallet P&L, market consensus, live alerts
概览
只读的 Polymarket 聪明钱分析:巨鲸排行榜、钱包盈亏、市场共识以及付费的实时巨鲸提醒。
- 可以做什么
- 封装 OrcaLayer API,提供六个只读工具:leaderboard 按盈亏、胜率、成交量或交易笔数对聪明钱钱包排名;wallet_overview 与 wallet_positions 展示钱包的盈利、胜率和最大持仓;markets 与 market_consensus 显示每个市场中聪明钱钱包持有多空两侧的数量并与价格对比。whale_alerts 提供盈利钱包的实时成交流。还附带 analyze_wallet、find_divergence 等提示词,以及方法论、术语表和 API 参考等只读资源。
- 适用场景
- 适合让助手研究预测市场动态:判断某个钱包是聪明钱还是刷量者、找出聪明钱与价格背离的市场,或跟踪实时巨鲸交易。公开工具无需账号,可先试用再决定是否为提醒付费。
- 运行要求
- 可通过 uvx orcalayer-mcp 以 stdio 在本地运行(需要 Python),也可使用托管的 Streamable HTTP 端点。公开工具无需账号或密钥。付费的 whale_alerts 需要付费 API 密钥:本地用环境变量 ORCALAYER_API_KEY,托管服务器用 Authorization Bearer 请求头。需要能访问 OrcaLayer API 的网络。
安装
在 SourceWeft 中
- 打开 控制台中的 Orcalayer Mcp,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
orcalayer-mcp
[PyPI] [MIT License] [MCP] [MCP Badge] [Glama MCP] [orcalayer-mcp MCP server]
Model Context Protocol (MCP) server for the OrcaLayer API — Polymarket whale and market analytics inside Claude, Cursor and other MCP clients.
Two ways to use it:
- Hosted, nothing to install:
https://orcalayer.com/mcp(Streamable HTTP). Add it as a connector in Claude (Settings → Connectors → Add custom connector, paste the URL) or in any client that supports remote MCP servers. - Local (stdio):
uvx orcalayer-mcp, for Claude Desktop and other local clients.
Either way it is a thin wrapper over the orcalayer
Python SDK and exposes six read-only tools:
Public tools work anonymously. whale_alerts needs a Premium API key
(get one): on the hosted server send it as the
Authorization: Bearer <key> request header (clients that support request
headers for a connector), on the local server set the ORCALAYER_API_KEY
environment variable. Without a key the tool answers with a short notice, not
an error.
Every tool carries readOnlyHint: true: nothing is created, changed or
deleted on your behalf. Data is read from the OrcaLayer API only.
Each result carries a short notes block that defines its fields, so a model
comparing two tools never meets two different numbers under one name:
market_win_rate (share of resolved markets won) has the same basis in
leaderboard and wallet_overview; profit_factor is capped at 99.99 on the
leaderboard (profit_factor_capped) and uncapped net in the overview;
indexed_volume_usd is the volume of fills in OrcaLayer's index, not
Polymarket's figure; Smart Money counts are wallets, whatever their size.
New (2026-07-22): the Premium SSE stream (
/api/public/v1/live/trades) now carriessettlement_type(MINT/MERGE/COMPLEMENTARY/null) on every event — live-derived settlement mechanics, shadow-verified 100.000% accurate on MINT/MERGE. It describes how the match settled, not trader intent (~80% of all fills settle as MINT;null= honest refusal, not "not a mint"). Details: theorcalayer://api-referenceresource or orcalayer.com/docs/api.
Prompts
Ready-to-use prompts for common analytics scenarios:
In Claude Desktop, pick a prompt from the prompt menu (the + / slash-command
picker) — each one orchestrates the tools above for you.
Resources
Read-only context the model can pull directly — no tool call needed:
Use with Claude Desktop
Add this to your claude_desktop_config.json
(%APPDATA%\Claude\claude_desktop_config.json on Windows,
~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
The public tools work as-is. For the Premium whale_alerts tool, add your
API key (get one):
Restart Claude Desktop after editing the config.
Use the hosted server
The same six tools, prompts and resources are served at
https://orcalayer.com/mcp over Streamable HTTP. No account is needed for the
public tools. In Claude: Settings → Connectors → Add custom connector → paste
the URL. For whale_alerts, send your Premium key as the
Authorization: Bearer <key> request header where your client supports
connector headers; keys are never accepted in the URL.
Self-host over HTTP
The server is stateless and answers plain JSON, so any reverse proxy with TLS
in front of it will do (forward POST /mcp to 127.0.0.1:8020/mcp). The
ORCALAYER_MCP_HTTP=1, ORCALAYER_MCP_HOST, ORCALAYER_MCP_PORT and
ORCALAYER_MCP_PATH environment variables are equivalent to the flags.
ORCALAYER_MCP_ANON_BASE_URL optionally routes anonymous calls to a different
API host (the hosted server points it at its local backend); calls that carry
a key always go to https://orcalayer.com. Put your own per-client rate limit
in the proxy: the server itself does not limit callers.
License
MIT. See LICENSE.
Data is provided for informational purposes only and is not financial advice.
mcp-name: io.github.orcalayer/orcalayer-mcp
来源:README.md,提交 501c366
工具
0版本历史
1- v0.3.2最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分