io.github.orcalayer/orcalayer-mcp
PYPI · ORCALAYER-MCP
Polymarket smart-money analytics: whale leaderboard, wallet P&L, market consensus, live alerts
Available components
Last scanned (23 hours ago)
Scores higher than 86% of PyPI servers
Category Finance and Payments
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Stability: pass → 0.97 functional
- 30 Oct 26 +15
- Provenance: unverified → fail ▼ security
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 0
- Provenance: fail → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 26 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/orcalayer-mcp@0.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
leaderboard ~192
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).
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| filter | string | – | – |
| limit | integer | – | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
market_consensus ~249
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.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | – |
No output schema declared.
No examples provided.
markets ~194
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).
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| limit | integer | – | – |
| min_volume | – | – | – |
| min_whales | – | – | – |
| q | string | – | – |
No output schema declared.
No examples provided.
wallet_overview ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
wallet_positions ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
whale_alerts ~208
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).
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| limit | integer | – | – |
| min_usd | number | – | – |
| minutes | integer | – | – |
No output schema declared.
No examples provided.
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.
pypi · orcalayer-mcp
claude mcp add orcalayer-orcalayer-mcp -- uvx orcalayer-mcp
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 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 5 November 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.
What did VerifyMCP test on the io.github.orcalayer/orcalayer-mcp server?
VerifyMCP ran 16 checks on io.github.orcalayer/orcalayer-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.