MCP server

Hosted endpoint

Nothing to install. Add this URL to your client as a remote MCP server (Streamable HTTP):

https://orcalayer.com/mcp

The same tools, prompts and resources are also available as the orcalayer-mcp Python package for clients that run local servers (see Run it locally).

Tools

Every tool carries readOnlyHint: true: nothing is created, changed or deleted on your behalf. Results are capped (up to 100 rows per call) so they stay readable for the model, and each one carries a short notesblock that defines its fields. "Smart Money wallets" are wallets from OrcaLayer's Smart Money set, counted whatever their position size; market_win_rate means the same thing in every tool.

Connect your client

Claude (web, desktop, mobile)

1. Open Settings, then Connectors, then Add custom connector
2. Name: OrcaLayer, URL: https://orcalayer.com/mcp, no OAuth
3. Enable the connector in a chat and ask, for example: Show the top 5 smart-money whales on Polymarket by P&L

Claude Code

claude mcp add --transport http orcalayer https://orcalayer.com/mcp

Cursor

{
  "mcpServers": {
    "orcalayer": { "url": "https://orcalayer.com/mcp" }
  }
}

VS Code (GitHub Copilot)

{
  "servers": {
    "orcalayer": { "type": "http", "url": "https://orcalayer.com/mcp" }
  }
}

Run it locally (stdio)

For Claude Desktop and other clients that launch local servers, the orcalayer-mcp package runs the same server on your machine:

{
  "mcpServers": {
    "orcalayer": {
      "command": "uvx",
      "args": ["orcalayer-mcp"]
    }
  }
}

Premium key for whale_alerts

whale_alerts needs an OrcaLayer Premium API key (Premium, key on Settings). Without a key the tool answers with a short notice instead of an error, so the rest keeps working. On the hosted server the key travels as a request header on the connection, in clients that support headers for a connector. It is never read from the URL.

claude mcp add --transport http orcalayer https://orcalayer.com/mcp \
  --header "Authorization: Bearer sk_orca_XXXXXX"

{
  "mcpServers": {
    "orcalayer": {
      "url": "https://orcalayer.com/mcp",
      "headers": { "Authorization": "Bearer sk_orca_XXXXXX" }
    }
  }
}

{
  "mcpServers": {
    "orcalayer": {
      "command": "uvx",
      "args": ["orcalayer-mcp"],
      "env": { "ORCALAYER_API_KEY": "sk_orca_XXXXXX" }
    }
  }
}

Prompts and resources

Four ready-made analyses, available from the prompt picker in clients that support MCP prompts. Each one orchestrates the tools above.

• 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 recent profit was real alpha or a hedge structure
• territorial_markets_review: Ukraine territorial markets with the ISW frontline overlay

Three resources the model can read without a tool call:

• orcalayer://methodology: how smart money is separated from farmers, hedgers and market makers (full version)
• orcalayer://glossary: prediction-market terms used in the data
• orcalayer://api-reference: the REST endpoints behind the tools (API docs)

Things to ask

• Who are the top 10 smart-money whales in Crypto by win rate?
• What does smart money think about this market: <Polymarket URL>
• Find Politics markets where at least 5 Smart Money wallets are positioned
• Analyze wallet 0x56687bf447db6ffa42ffe2204a05edaa20f55839: smart money or farmer?
• Is this wallet's recent profit real alpha or a hedge? (uses the hedge_check prompt)

Limits and reliability

• 60 requests per minute per client address on /mcp, with room for a session's opening handshake; Claude's connector traffic has a separate shared pool
• Over the limit: 429 with Retry-After: 10; clients that retry recover on their own
• Tool calls made with a Premium key count against that key's API limit (600 per minute)
• The server is stateless: a restart on our side is invisible to a connected client, there is no session to lose
• Data freshness is the API's: positions and consensus update in batches, typically 15 to 20 seconds behind chain; leaderboard stats refresh within minutes of trading activity

Data handling

The server reads from the OrcaLayer API only and writes nothing. When your AI client calls a tool we receive the tool name and its parameters (for example a wallet address or a market id) and keep the same request log as for every API call: time, client address, client software and, if a key is sent, the key's identifier, never the key itself. We do not receive or store your conversation; the AI client you use processes it under its own privacy policy. The API request log is kept for 45 days, web server access logs for 15 days. Details in our Privacy Policy.

Self-host over HTTP

The package can serve Streamable HTTP itself, for a team server behind your own reverse proxy:

pip install orcalayer-mcp
orcalayer-mcp --http --host 127.0.0.1 --port 8020 --path /mcp

Source, changelog and issues: github.com/orcalayer/orcalayer-mcp (MIT).