Skip to content

OrcaLayer MCP server

io.github.orcalayer/orcalayer-mcporcalayerstreamable-httpv0.5.22Scanned

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

5 tools: 2 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 2 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 5
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the OrcaLayer MCP server can do

The OrcaLayer MCP server is published by the GitHub account orcalayer. It has 5 tools. It can create or change data (2 tools: leaderboard and market_consensus), but cannot delete data. 3 tools only read.

5 tools bring in text other people can write (leaderboard, wallet_overview, wallet_positions and 2 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 8 times since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 0.5.22.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 2Claude Code: ask
  • leaderboardRank Polymarket traders from OrcaLayer's Smart Money set (or all wallets).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Rank Polymarket traders from OrcaLayer's Smart Money set (or all wallets). Returns the top traders by lifetime profit, win rate, volume or trade count, optionally within one market category. Per wallet: name, total_pnl (Polymarket's lifetime P&L), market_win_rate with market_wins / market_losses / resolved_markets, profit_factor (capped at 99.99, with profit_factor_capped), indexed_volume_usd, indexed_trades, main category, average entry price, open positions and the last trade date. `total` is how many wallets match the filter. A `notes` block defines each field.

    Annotations the server declares

    • title: Smart-money leaderboard
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • market_consensusSmart-money consensus on one Polymarket market versus its current price.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Smart-money consensus on one Polymarket market versus its current price. Returns how Smart Money wallets are positioned on one market: how many hold YES and NO, how much capital each side has invested, the current market price, and the gap between that positioning and the price. Two consensus reads are returned side by side and can disagree: ``head_count`` (one Smart Money wallet = one vote; wallets from OrcaLayer's Smart Money set; the busiest markets count hundreds, a handful over a thousand; a wallet holding both sides is in both counts, while ``head_count.took_side`` counts each wallet once, on the side holding more of its dollars and only with $10 or more on that side, as the OrcaLayer market page does; ``dust`` is how many were left out under $10) and ``capital_weighted`` (dollars invested per side). In head_count a $5 wallet weighs the same as a $500K one, so it is the weaker of the two reads; the capital split reflects the money at stake. On cheap longshots (YES under ~15 cents) head_count leans YES structurally. The divergence fields measure positioning against the price; they are not evidence that the price is wrong. ``market_makers`` counts the market makers among the holders on each side, for all holders and for the Smart Money ones (a market maker: 90%+ of its last 30 days of volume came from its own resting orders that others filled, over 5,000+ fills, the Market maker label of the OrcaLayer market page). A market maker's position is inventory it trades around, not a view on the outcome. These wallets are still counted in head_count and capital_weighted; null when the market has no position snapshot. An event slug or event URL (a Polymarket event groups several markets) returns the event's markets with their ids and Smart Money wallet counts instead, since the consensus is per market.

    Annotations the server declares

    • title: Smart-money consensus on a market
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • marketsSearch Polymarket markets, optionally where Smart Money wallets cluster.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Search Polymarket markets, optionally where Smart Money wallets cluster. Finds markets by topic, slug or URL and shows how many wallets from OrcaLayer's Smart Money set hold each side right now. Returns each market's id, question, YES price, smart_wallets_yes / smart_wallets_no, volume, end date and days left. The counts are wallets, whatever their position size; the busiest markets count hundreds, a handful over a thousand. The dollar split on one market is in the market_consensus tool.

    Annotations the server declares

    • title: Market search
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • wallet_overviewSummarize one wallet's trading profile and performance.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "summarize": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Summarize one wallet's trading profile and performance. Wallet profit tracking for any Polymarket address: lifetime P&L (Polymarket's figure), market_win_rate over resolved markets, a net profit factor, indexed volume and activity, category mix and leaderboard rankings. Accepts a 0x wallet address or an OrcaLayer nickname. Returns a compact summary rather than the full raw record, so it stays readable for heavy wallets. A `notes` block defines each field; market_win_rate has the same basis and value as in the leaderboard tool. While the wallet's stats are still being computed server-side, the result is a ``{"status": "computing", "retry_after_seconds": N}`` notice instead of data; N is the number of seconds after which the stats are expected to be ready.

    Annotations the server declares

    • title: Wallet overview
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • wallet_positionsList a wallet's largest open positions by current value.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Wallet open positions
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:21 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://orcalayer.com/.well-known/oauth-protected-resource
Authorization servers
https://orcalayer.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://orcalayer.com/mcp: tools/list returned 5 tools to an anonymous client, including leaderboard (write), market_consensus (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools1 changed.~1 changedView diff
  3. Tools2 changed.~2 changedView diff
  4. Tools1 changed.~1 changedView diff
  5. Tools2 changed.~2 changedView diff
  6. Tools5 changed.~5 changedView diff
  7. Tools1 changed.~1 changedView diff
    • Changed:leaderboardChanges thingsdescriptioninputSchema
  8. Tools1 changed.~1 changedView diff
    • Changed:leaderboardChanges thingsdescriptioninputSchema

Install

Pinned to version 0.5.22. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__orcalayer__wallet_overview",
      "mcp__orcalayer__wallet_positions",
      "mcp__orcalayer__markets"
    ],
    "ask": [
      "mcp__orcalayer__leaderboard",
      "mcp__orcalayer__market_consensus"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as orcalayer. Review it before you use it.

Capability tags behind 5 rules
  • mcp__orcalayer__leaderboard untrusted-input
  • mcp__orcalayer__wallet_overview untrusted-input
  • mcp__orcalayer__wallet_positions untrusted-input
  • mcp__orcalayer__markets untrusted-input
  • mcp__orcalayer__market_consensus untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.orcalayer/orcalayer-mcp/verify?hash=8cbd7e394861c44e8ef8b164224adb03ae38dbf11c0e6d25eb5ab407b2ddd25f" | jq -e '.changed == false'

Pinned hash 8cbd7e394861, from Nov 21, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.orcalayer/orcalayer-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.orcalayer/orcalayer-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.orcalayer/orcalayer-mcp.svg)](https://radar.anlyon.com/servers/io.github.orcalayer/orcalayer-mcp)

Source: MCP Registry · repository. Synced Nov 21, 2026, 21:18 UTC.

OrcaLayer MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the OrcaLayer MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the OrcaLayer MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the OrcaLayer MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the OrcaLayer MCP server have?

5 tools: 2 write, 3 read. leaderboard, market_consensus, wallet_overview, wallet_positions and markets.

Does the OrcaLayer MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the OrcaLayer MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the OrcaLayer MCP server changed its tools?

Yes, 8 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.