Skip to main content

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:

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): 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.

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:

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):

{
  "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):

{
  "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 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

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.

License

MIT. See LICENSE.

Data is provided for informational purposes only and is not financial advice.


mcp-name: io.github.orcalayer/orcalayer-mcp

Metadata

Release files for orcalayer-mcp 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for orcalayer-mcp 0.4.0
File Size Uploaded Provenance Actions
orcalayer_mcp-0.4.0.tar.gz 83.6 kB Without provenance Details for orcalayer_mcp-0.4.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for orcalayer-mcp 0.4.0
File Interpreter ABI Platform Actions
orcalayer_mcp-0.4.0-py3-none-any.whl Python 3 none any Details for orcalayer_mcp-0.4.0-py3-none-any.whl

Total release size: 100.5 kB

Release files / orcalayer_mcp-0.4.0.tar.gz

Download URL orcalayer_mcp-0.4.0.tar.gz
Size 83.6 kB
Tags Source
SHA-256 checksum
How to use checksums
b29ac4c7cb2fa901b0e7d9298c1248e79599986b0990ea18fdc9d5f11a62dfec
BLAKE2b-256 checksum
How to use checksums
b8ec261f4d5d08252c4ef62884c97fc1e901a00849aa3e970b2d00df7d3b5b36
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.24 {"installer":{"name":"uv","version":"0.11.24","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / orcalayer_mcp-0.4.0-py3-none-any.whl

Download URL orcalayer_mcp-0.4.0-py3-none-any.whl
Size 16.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c06af0e6f6dceb23b79346c0ce0094b5ef4b98ba713f122a803eb392171100f3
BLAKE2b-256 checksum
How to use checksums
cda78dff611c27945e4dca448a3207ffee85d9abdd822afb2027e78db2966ec3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.24 {"installer":{"name":"uv","version":"0.11.24","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for orcalayer-mcp 0.4.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page