orcalayer-mcp
Official# orcalayer-mcp
[](https://pypi.org/project/orcalayer-mcp/)
[](LICENSE)
[](https://modelcontextprotocol.io)
[](https://lobehub.com/mcp/orcalayer-orcalayer-mcp)
[](https://glama.ai/mcp/servers/orcalayer/orcalayer-mcp)
[](https://glama.ai/mcp/servers/orcalayer/orcalayer-mcp)
Model Context Protocol (MCP) server for the [OrcaLayer API](https://orcalayer.com) —
Polymarket whale and market analytics inside Claude Desktop and other MCP clients.
It is a thin stdio wrapper over the [`orcalayer`](https://pypi.org/project/orcalayer/)
Python SDK and exposes six tools:
| Tool | What it does | Key |
|---|---|---|
| `leaderboard` | Rank smart-money whales by P&L, win rate or volume | No |
| `wallet_overview` | Wallet profit tracking: profile, P&L and win-rate summary | No |
| `wallet_positions` | A wallet's largest open positions | No |
| `markets` | Track smart money flows: search markets where smart whales are accumulating | No |
| `market_consensus` | Smart-money consensus on one market vs its price (head-count + capital-weighted) | No |
| `whale_alerts` | Real-time alerts on profitable wallets: live feed of smart-whale trades | Premium |
Public tools work anonymously. `whale_alerts` needs a Premium API key
([get one](https://orcalayer.com/pricing)) supplied via the
`ORCALAYER_API_KEY` environment variable.
> **New (2026-07-22):** the Premium SSE stream (`/api/public/v1/live/trades`)
> now carries `settlement_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: the `orcalayer://api-reference`
> resource or [orcalayer.com/docs/api](https://orcalayer.com/docs/api).
## Prompts
Ready-to-use prompts for common analytics scenarios:
| Prompt | What it does |
|---|---|
| `analyze_wallet` | Full wallet analysis — smart money or farmer? |
| `find_divergence` | Markets where smart money disagrees with the current price |
| `hedge_check` | Whether a wallet's profit was real alpha or a hedge structure |
| `territorial_markets_review` | Ukraine territorial markets with ISW frontline overlay |
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:
| Resource URI | Content |
|---|---|
| `orcalayer://methodology` | How smart money is filtered from farmers, hedgers and market-makers |
| `orcalayer://glossary` | Prediction-markets glossary |
| `orcalayer://api-reference` | OrcaLayer REST API reference (endpoints, auth, rate limits) |
## 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):
```json
{
"mcpServers": {
"orcalayer": {
"command": "uvx",
"args": ["orcalayer-mcp"]
}
}
}
```
The public tools work as-is. For the Premium `whale_alerts` tool, add your
API key ([get one](https://orcalayer.com/pricing)):
```json
{
"mcpServers": {
"orcalayer": {
"command": "uvx",
"args": ["orcalayer-mcp"],
"env": { "ORCALAYER_API_KEY": "sk_orca_your_key_here" }
}
}
}
```
Restart Claude Desktop after editing the config.
## License
MIT. See [LICENSE](LICENSE).
Data is provided for informational purposes only and is not financial advice.
---
mcp-name: io.github.orcalayer/orcalayer-mcp
TDQS
Scored across 6 tools
Each tool targets a clearly distinct slice of the domain: ranking whales, summarizing a wallet, listing positions, searching markets, reading market consensus, and streaming whale trades. Even the two wallet-focused tools are cleanly separated by performance summary versus open positions.
All tool names follow the same lowercase snake_case noun-phrase pattern, e.g. wallet_overview, wallet_positions, market_consensus, whale_alerts. There is no mixing of verb styles or casing conventions, so an agent can predict related tool names.
Six tools is a well-scoped size for a Polymarket smart-money analytics server. Each tool covers a meaningful capability without redundancy, and the count is comfortably within the ideal range.
The set covers the core analytics workflow: discovering top whales, inspecting a wallet, seeing current positions, finding markets with whale activity, checking consensus on a single market, and following live whale trades. A minor gap is the lack of a wallet-level historical trade or a per-market price history tool, but agents can work around those with the provided surface.