# io.github.orcalayer/orcalayer-mcp (pypi · orcalayer-mcp)

Polymarket smart-money analytics: whale leaderboard, wallet P&L, market consensus, live alerts

- Trust score: 65/100 (medium)
- Change this week: −1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- pypi · `orcalayer-mcp`: 65/100 (this document), [markdown](https://verifymcp.io/servers/orcalayer-orcalayer-mcp/orcalayer-mcp.md), [page](https://verifymcp.io/servers/orcalayer-orcalayer-mcp/orcalayer-mcp)

## Channel facts

- Registry: `pypi`
- Package: `orcalayer-mcp`
- Version: `0.3.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 0 of 30 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 30 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1300 tokens (~144/item across 9 items; 6 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.orcalayer/orcalayer-mcp server?

io.github.orcalayer/orcalayer-mcp runs locally as a PyPI package, launched with uvx orcalayer-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add orcalayer-orcalayer-mcp -- uvx orcalayer-mcp
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "orcalayer-orcalayer-mcp": {
      "command": "uvx",
      "args": [
        "orcalayer-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add orcalayer-orcalayer-mcp -- uvx orcalayer-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "orcalayer-orcalayer-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "orcalayer-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add orcalayer-orcalayer-mcp --command uvx --arg orcalayer-mcp
```

### Hermes

```yaml
mcp_servers:
  orcalayer-orcalayer-mcp:
    command: "uvx"
    args: ["orcalayer-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "orcalayer-orcalayer-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "orcalayer-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add orcalayer-orcalayer-mcp -t stdio -c uvx -a orcalayer-mcp
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 65, −3)

- [functional] Stability: pass → 0.77

### 2026-09-19 (score 68, 0)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 66, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-13 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-11 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 64, −14)

- [security regression] Malware scan: pass → unverified

## MCP tools (6)

### `leaderboard` (~192 tokens)

Rank the most successful Polymarket whales (smart-money traders).

Use this to find top traders by realized profit, win rate, or volume —
optionally narrowed to one market category. Returns each whale's wallet,
name, total P&L, win rate, profit factor and resolved-market count.

Args:
    sort: Ranking key — "pnl" (default), "win_rate", "volume" or "trades".
    category: Restrict to one category, e.g. "Crypto", "Sports",
        "Politics", "Geopolitics", "Economics", "Tech/AI". None = all.
    filter: "smart" (curated profitable whales, default) or "all".
    limit: How many whales to return (1–100).

Input parameters:

- `category`
- `filter` (string)
- `limit` (integer)
- `sort` (string)

### `wallet_overview` (~167 tokens)

Summarize one wallet's trading profile and performance.

Wallet profit tracking for any Polymarket address: lifetime P&L, win
rate, ROI-style stats (profit factor), volume and activity. Accepts a 0x
wallet address or an OrcaLayer nickname. Returns a compact summary —
identity, lifetime activity, and P&L stats — rather than the full raw
record, so it stays readable for heavy wallets.

If the wallet's stats are still being computed server-side, this returns
a ``{"status": "computing", "retry_after_seconds": N}`` notice instead of
data — call the tool again after that delay.

Args:
    address: 0x wallet address or OrcaLayer nickname.

Input parameters:

- `address` (string, required)

### `wallet_positions` (~120 tokens)

List a wallet's largest open positions by current value.

Accepts a 0x wallet address or an OrcaLayer nickname. Returns the
positions with the largest current value first, in a compact form, plus a
count of how many more are not shown.

Args:
    address: 0x wallet address or OrcaLayer nickname.
    limit: How many positions to return (1–50). The wallet may hold more;
        the response reports how many were omitted.

Input parameters:

- `address` (string, required)
- `limit` (integer)

### `markets` (~194 tokens)

Search Polymarket markets, optionally where smart whales are clustering.

Use this to track smart money flows: find markets by topic and surface
where smart money is accumulating right now. Returns each market's
question, YES price, smart-whale counts on each side, volume and days
left.

Args:
    q: Free-text query; also accepts a Polymarket URL or slug. "" browses.
    category: One of "Crypto", "Geopolitics", "Sports", "Politics",
        "Economics", "Tech/AI". None = all.
    min_volume: Minimum market volume in USD.
    min_whales: Minimum number of smart whales active in the market.
    limit: How many markets to return (1–100).

Input parameters:

- `category`
- `limit` (integer)
- `min_volume`
- `min_whales`
- `q` (string)

### `market_consensus` (~249 tokens)

Smart-money consensus on one Polymarket market versus its current price.

Shows where smart money stands on a market: how many profitable
smart-money whales hold YES vs NO, how much capital each side has
invested, the current market price, and the divergence between
smart-money positioning and that price. Use it to answer "what does
smart money think about this market?" and to spot markets where smart
money disagrees with the crowd.

Two consensus reads are returned side by side and can disagree:
\``head_count`` (one whale = one vote) and ``capital_weighted`` (dollars
invested per side). Head-count is the weaker signal — a $5 wallet counts
the same as a $500K one — so when the two disagree, trust the capital
split more. On cheap longshots (YES under ~15 cents) head-count skews
YES structurally. Divergence from price is positioning information, not
proof the market is mispriced; never present it as "the market is wrong".

Args:
    market: Market id, Polymarket slug or URL, or 0x condition id.

Input parameters:

- `market` (string, required)

### `whale_alerts` (~208 tokens)

Recent trades by smart-money whales — real-time alerts on profitable
wallets (Premium).

Returns whale trades in the last ``minutes`` over ``min_usd`` in size:
who traded, buy/sell, side, amount, price and the market. Use it to get
alerts when profitable Polymarket wallets open or close positions.

Requires a Premium API key set via the ORCALAYER_API_KEY environment
variable. Without a key this returns a short notice on how to get one (it
does not call the API and is not an error).

Args:
    minutes: Lookback window in minutes (max 1440 = 24h).
    min_usd: Minimum trade size in USD.
    category: Restrict to one market category. None = all.
    limit: How many alerts to return (1–100).

Input parameters:

- `category`
- `limit` (integer)
- `min_usd` (number)
- `minutes` (integer)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/orcalayer-orcalayer-mcp/orcalayer-mcp#diagnostics

## Score history

- 2026-09-21: 65
- 2026-09-20: 68
- 2026-09-19: 68
- 2026-09-18: 68
- 2026-09-17: 67
- 2026-09-16: 67
- 2026-09-15: 66
- 2026-09-14: 66
- 2026-09-13: 81
- 2026-09-12: 65
- 2026-09-11: 65
- 2026-09-10: 64
- 2026-09-09: 64
- 2026-09-08: 78
- 2026-09-07: 78
- 2026-09-06: 77
- 2026-09-05: 77
- 2026-09-04: 76
- 2026-09-03: 61
- 2026-09-02: 60
- 2026-09-01: 75
- 2026-08-31: 74
- 2026-08-30: 74
- 2026-08-29: 74
- 2026-08-28: 73
- 2026-08-27: 73
- 2026-08-26: 72
- 2026-08-25: 70
- 2026-08-24: 69
- 2026-08-23: 69

## Common questions

### What is the io.github.orcalayer/orcalayer-mcp server?

io.github.orcalayer/orcalayer-mcp is listed in the public MCP registry as io.github.orcalayer/orcalayer-mcp. Polymarket smart-money analytics: whale leaderboard, wallet P&L, market consensus, live alerts. This page covers its PyPI package (orcalayer-mcp).

### Is the io.github.orcalayer/orcalayer-mcp server safe to use?

io.github.orcalayer/orcalayer-mcp scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.orcalayer/orcalayer-mcp server expose?

io.github.orcalayer/orcalayer-mcp exposes 6 tools: leaderboard, wallet_overview, wallet_positions, markets, market_consensus, whale_alerts. Their descriptions and schemas cost roughly 1,130 tokens of context every time the server is loaded.

### Is the io.github.orcalayer/orcalayer-mcp server still maintained?

io.github.orcalayer/orcalayer-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.orcalayer/orcalayer-mcp server under?

io.github.orcalayer/orcalayer-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/orcalayer-mcp/
- Socket report: https://socket.dev/pypi/package/orcalayer-mcp
- Repository: https://github.com/orcalayer/orcalayer-mcp
- Website: https://orcalayer.com/
- Changelog RSS feed: https://verifymcp.io/servers/orcalayer-orcalayer-mcp/orcalayer-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/orcalayer-orcalayer-mcp/orcalayer-mcp.json
- HTML version of this page: https://verifymcp.io/servers/orcalayer-orcalayer-mcp/orcalayer-mcp