_ registry / mcp streamable-http · checked 52m ago

orcalayer

https://orcalayer.com

Registry code: 78be8d39e15e27f8

api record

OrcaLayer provides read-only Polymarket smart-money analytics. Tools: a ranking of profitable traders (leaderboard), a wallet's profile and open positions (wallet_overview, wallet_positions), market search with Smart Money wallet counts (markets), the Smart Money consensus on one market versus its price (market_consensus), and recent trades by Smart Money wallets (whale_alerts, Premium). Prompts hold ready-made analyses; resources hold the classification methodology, a glossary and the REST API reference.

endpoint
https://orcalayer.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is orcalayer live?
Yes — it answered the hub's last check (checked 52m ago). It answered 100% of checks over the last 30 days.
Is orcalayer free to use?
Yes — the hub reached it with no key and no payment.
What tools does orcalayer have?
6 tools: wallet_overview, wallet_positions, market_consensus, leaderboard, markets, whale_alerts.
Is orcalayer safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
145ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
3 open 3 never probed 3 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • leaderboard open 52m ago

    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. Args: sort: Ranking key: "pnl" (default), "win_rate", "volume" or "trades". "win_rate" orders by the leaderboard's stored win rate, which is computed differently from the market_win_rate shown, so rows can look out of order by that column. category: Restrict to one category, e.g. "Crypto", "Sports", "Politics", "Geopolitics", "Economics", "Tech/AI". None = all. filter: "smart" (OrcaLayer's Smart Money set, default) or "all". limit: How many wallets to return (1–100).

    mcp-tool

    {
      "type": "object",
      "title": "leaderboardArguments",
      "properties": {
        "sort": {
          "type": "string",
          "title": "Sort",
          "default": "pnl"
        },
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 20
        },
        "filter": {
          "type": "string",
          "title": "Filter",
          "default": "smart"
        },
        "category": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Category",
          "default": null
        }
      }
    }
    arguments 33 lines
  • markets open 52m ago

    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; popular markets have thousands. The dollar split on one market is in the market_consensus tool. 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 Money wallets holding a position in the market (either side). limit: How many markets to return (1–100).

    mcp-tool

    {
      "type": "object",
      "title": "marketsArguments",
      "properties": {
        "q": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "integer"
            }
          ],
          "title": "Q",
          "default": ""
        },
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 20
        },
        "category": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Category",
          "default": null
        },
        "min_volume": {
          "anyOf": [
            {
              "type": "number"
            },
            {
              "type": "null"
            }
          ],
          "title": "Min Volume",
          "default": null
        },
        "min_whales": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "title": "Min Whales",
          "default": null
        }
      }
    }
    arguments 59 lines
  • whale_alerts open 52m ago

    Recent trades by Smart Money wallets: real-time alerts on profitable wallets (Premium). Returns trades by Smart Money wallets in the last ``minutes`` over ``min_usd`` in size: who traded, buy or sell, side, amount, price, the wallet's position after the trade, and the market. Covers profitable Polymarket wallets opening, adding to or closing positions. Needs an OrcaLayer Premium API key: on the hosted server it is the ``Authorization: Bearer <key>`` request header, on the local stdio server the ORCALAYER_API_KEY environment variable. Without a key the result is a short notice on how to get one (no API call is made and it 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).

    mcp-tool

    {
      "type": "object",
      "title": "whale_alertsArguments",
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 25
        },
        "min_usd": {
          "type": "number",
          "title": "Min Usd",
          "default": 1000
        },
        "minutes": {
          "type": "integer",
          "title": "Minutes",
          "default": 60
        },
        "category": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Category",
          "default": null
        }
      }
    }
    arguments 33 lines
  • wallet_overview unknown never probed

    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. Args: address: 0x wallet address or OrcaLayer nickname.

    mcp-tool

    {
      "type": "object",
      "title": "wallet_overviewArguments",
      "required": [
        "address"
      ],
      "properties": {
        "address": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "integer"
            }
          ],
          "title": "Address"
        }
      }
    }
    arguments 20 lines
  • wallet_positions unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "title": "wallet_positionsArguments",
      "required": [
        "address"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 15
        },
        "address": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "integer"
            }
          ],
          "title": "Address"
        }
      }
    }
    arguments 25 lines
  • market_consensus unknown never probed

    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, so popular markets count thousands) 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. Args: market: Market id, Polymarket slug or URL, or 0x condition id.

    mcp-tool

    {
      "type": "object",
      "title": "market_consensusArguments",
      "required": [
        "market"
      ],
      "properties": {
        "market": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "integer"
            }
          ],
          "title": "Market"
        }
      }
    }
    arguments 20 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 78be8d39e15e27f8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/78be8d39e15e27f8/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/78be8d39e15e27f8/badge.svg)](https://brick.blue/agent/78be8d39e15e27f8?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.