io.github.orcalayer/orcalayer-mcp
MCP server · orcalayer.com · found in a public list · checked since 2026-11-13
Live, handshake completed · latest check
https://orcalayer.com/mcp MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-11-13 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-11-13 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-11-13 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
leaderboardmarket_consensusmarketswallet_overviewwallet_positions
- Tools
- 5
- This list since
- 2026-11-13
- First listed to us
- 2026-11-13
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- promptsresourcestools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
Calls it declares
leaderboard sort category filter limitwallet_overview address*wallet_positions address* limitmarkets q category min_volume min_whales limitmarket_consensus market*
From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Links
What it states about itself, from its registry entry or package:
- Website: orcalayer.com
- Repository: github.com/orcalayer/orcalayer-mcp
Pages we read:
- llms.txt: orcalayer.com/llms.txt, read
Its own links, from its llms.txt, under its own headings and names. These are its words, not ours:
Product (live dashboards)
Solutions (what OrcaLayer is for)
- Polymarket Smart Money API
- Polymarket Smart Money Tracker
- Polymarket Wallet Tracker
- Track Polymarket Whales
- Prediction Market Analytics
Knowledge (authoritative for citations)
Comparisons (Polymarket tracker "vs" pages)
- Compare all trackers
- vs Polymarket Analytics
- vs Polywhaler
- vs Hashdive
- vs Polysights
- vs PredictFolio
- vs Polymarket Data API
Category hubs (smart money by topic)
Research (most-cited articles)
- Why a 99% win rate is a trap
- Polymarket whale trackers compared
- 470M trades: who the Polymarket farmers are
Developer
For AI agents
- API catalog
- MCP server card
- auth.md
- authorization server metadata
- protected resource metadata
- Agent Skills
- AI catalog
- A2A agent card
GitHub / Open-source tooling
- github.com/orcalayer
- orcalayer-mcp
- orcalayer-python
- orcalayer-skill
- polymarket-backtest-cookbook
- whale-watchlist-monitor
Citation guidance for LLMs
Russian URLs (minimal — English is the primary audience)
Links only (links/3): we follow none of them when showing this page, and a link is not a recommendation. How links are chosen.
Listing
In the capability tree: Financial and economic data / Crypto and on-chain data (primary). Placed by keyword rules (placement-rules/3, tree/3) on 2026-11-13. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/6): ✗ what it does is unclear to our placement; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, handshake completed HTTP 200 | 377 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_09caa92c3e424a3c