Back to Browse

Orcalayer MCP Server

Developer ToolsModerate5.6MCP RegistryLocalRemote
Free

Server data from the Official MCP Registry

Polymarket smart money and whale analytics: win rate, smart money flags, consensus, whale alerts

About

Polymarket smart money and whale analytics: win rate, smart money flags, consensus, whale alerts

Remote endpoints: streamable-http: https://orcalayer.com/mcp

Security Report

5.6
Moderate5.6Moderate Risk

The orcalayer-mcp server is a read-only wrapper around the OrcaLayer analytics API. Premium keys are read from request headers or an environment variable, errors are scrubbed of the key, and no shell execution, eval, or data exfiltration is present in the visible code. The main concerns are code quality: reliance on a private SDK method, broad silent exception handling, and the server not rate-limiting callers in HTTP mode; the code is also truncated, so the remaining part was not reviewed. Supply chain analysis found 5 known vulnerabilities in dependencies (0 critical, 1 high severity). Package verification found 1 issue.

3 files analyzed · 10 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Optional Premium API key from orcalayer.com/pricing: adds the whale_alerts, pnl_leaderboard and resolution_events tools. Public tools work without it.Required

Environment variable: ORCALAYER_API_KEY

How to Install & Connect

Available as Local & Remote

This plugin can run on your machine or connect to a hosted endpoint. during install.

Documentation

View on GitHub

From the project's GitHub README.

orcalayer-mcp

PyPI MIT License MCP MCP Badge Glama MCP orcalayer-mcp MCP server

MCP server for the OrcaLayer Polymarket smart money and whale analytics API, inside Claude, Cursor and other MCP clients.

OrcaLayer is an analytics layer on top of Polymarket's free Data API: the official API returns raw trades, positions and P&L, and OrcaLayer returns what you would otherwise compute from them: win rate per resolved market, smart money, farmer and bot flags, smart money consensus on each market, and whale alerts. What it adds over the official API.

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 eight read-only tools:

ToolWhat it doesKey
leaderboardRank wallets from the Smart Money set by P&L, win rate, volume or trade countNo
wallet_overviewWallet profit tracking: profile, P&L, market win rate, profit factor, rankingsNo
wallet_positionsA wallet's largest open positionsNo
marketsTrack smart money flows: search markets and see how many Smart Money wallets hold each sideNo
market_consensusSmart-money consensus on one market vs its price (head-count + capital-weighted)No
whale_alertsReal-time alerts on profitable wallets: live feed of smart-whale tradesPremium
pnl_leaderboardWallets ranked by realized P&L over the last 7 or 30 days (any window since June 2026)Premium
resolution_eventsMarkets just proposed, disputed, resolved (with the winner) or reopenedPremium

Public tools work anonymously. whale_alerts, pnl_leaderboard and resolution_events need 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 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.

Prompts

Ready-to-use prompts for common analytics scenarios:

PromptWhat it does
analyze_walletFull wallet analysis — smart money or farmer?
find_divergenceMarkets where smart money disagrees with the current price
hedge_checkWhether a wallet's profit was real alpha or a hedge structure
territorial_markets_reviewUkraine 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 URIContent
orcalayer://methodologyHow smart money is filtered from farmers, hedgers and market-makers
orcalayer://glossaryPrediction-markets glossary
orcalayer://api-referenceOrcaLayer 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):

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

The public tools work as-is. For the Premium tools (whale_alerts, pnl_leaderboard, resolution_events), add your API key (get one):

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

Restart Claude Desktop after editing the config.

Use the hosted server

The same eight 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 the Premium tools, 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

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

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

Reviews

No reviews yet

Be the first to review this server!