
Orcalayer Mcp
io.github.orcalayerPublished by GitHub account orcalayerv0.3.2Updated Oct 24, 2026
Polymarket smart-money analytics: whale leaderboard, wallet P&L, market consensus, live alerts
Overview
Read-only Polymarket smart-money analytics: whale leaderboards, wallet P&L, market consensus and premium live whale alerts.
- What you can do
- Wraps the OrcaLayer API to expose six read-only tools: leaderboard ranks Smart Money wallets by P&L, win rate, volume or trade count; wallet_overview and wallet_positions cover a wallet's profit, win rate and largest open positions; markets and market_consensus show how many smart-money wallets hold each side of a market versus its price. whale_alerts streams live trades from profitable wallets. It also ships prompts such as analyze_wallet and find_divergence, plus read-only resources on methodology, glossary and API reference.
- When to use it
- Use it when you want an assistant to research prediction-market activity: judging whether a wallet is smart money or a farmer, spotting markets where smart money diverges from price, or following live whale trades. Public tools need no account, so it is easy to try before paying for alerts.
- Requirements
- Runs locally over stdio via uvx orcalayer-mcp (Python), or as a hosted Streamable HTTP endpoint. Public tools need no account or key. The premium whale_alerts tool needs a paid API key: ORCALAYER_API_KEY as an environment variable locally, or an Authorization Bearer header on the hosted server. Network access to the OrcaLayer API is required.
Installation
In SourceWeft
- Open Orcalayer Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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
Source: README.md at commit 501c366
Tools
0Version history
1- v0.3.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts