ClaudeListedTier: partner
etoro
etoro. Where Our Collective Intelligence Meets Your Claude
First seen 10 Oct 2026. Evidence as of 16 Nov 2026.
11
Tools
From an anonymous probe
2
Source listings
Each with its own history
9
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| execute-read | Executes a READ against the eToro Public API and relays the response faithfully: `statusCode`, `isSuccess`, `body` (the upstream JSON verbatim, as a string), the `RateLimit-*` headers and the `xRequestId` that was sent (generated when omitted). `path` is the route's RELATIVE path, e.g. `/api/v1/me` - there is no URL to compose, the server owns the destination; `query` (optional) is appended as the query string. Sends a GET by default. When `path` is one of the catalog's read-semantics POST routes (listed under `readOnlyPostRouteIds` by get-all-routes: what-if cost previews, eligibility dry-runs, bulk lookups - POST only carries the request body) it sends a POST with the supplied raw-JSON-string `body`; a body on any other path is refused before anything is sent, because a state-changing route cannot be reached through this server at all. Find routes with get-all-routes (filter with `query`/`tag`) and read one route's parameters, required OAuth scopes and rate limit with get-route-spec - both on this server. Upstream 4xx/5xx come back in `statusCode`/`body`, never as tool errors: a 401 means the connection's OAuth token was rejected and the MCP connection must be re-authorized (never retry the same token); a 403 names the missing scope; a 429 carries `retryAfterSeconds`; `statusCode` 0 means no response at all and is safe to retry. Credentials are NOT tool arguments and never travel in a call: this server accepts only the connection's `Authorization: Bearer` token, set by your MCP client after the user signs in with eToro; `x-user-key` / `x-api-key` headers are not accepted. This server has no write tool - state-changing operations (orders, transfers, copy-trading, watchlist edits) are not available here and must not be attempted. | Read-only |
| get-all-routes | Returns the eToro Public API READ routes this server can execute, with a short explanation for each. Route paths are RELATIVE - execute-read knows where to send them; there is no URL to compose. Each 'routes' entry maps a route id to '<HTTP METHOD> <path> - <summary>'; a deprecated route is prefixed '[DEPRECATED] '. NARROW THE CATALOG when you already know what you are looking for: pass 'query' (keywords matched against route id, method, path, summary and tags - all must match; the route that fits them best is listed first, and when no route contains every keyword you get the closest read routes instead, which 'filterNote' says) and/or 'tag' (one group, or several comma-separated, any of which may match). Both are OPTIONAL - calling with neither returns the entire read catalog and is a perfectly good call for open-ended questions ('what can I read with this API?'). 'tags' (tag -> read-route count) is ALWAYS returned, so you can see the available groups and drill into one; 'totalRouteCount' is the unfiltered read-catalog size, and 'filterNote' tells you how far a filter narrowed it and how to widen again. 'deprecatedRouteIds' lists deprecated routes - avoid them; 'supersededBy' maps a deprecated route id to the read route that replaces it. 'readOnlyPostRouteIds' lists the POST routes that are semantically READ-ONLY (cost/what-if previews, eligibility dry-runs, bulk lookups - POST only carries the request body): run these with execute-read passing 'body'; every other listed route is a GET. This server lists READ routes only: state-changing routes (orders, transfers, copy-trading, watchlist edits) are not listed and cannot be executed here - do not look for them or try to call them. Per-route OAuth scopes and rate limits are NOT in this listing - call get-route-spec for the route you picked; it carries both. 'skillVersion' is the current version of this server's skill document: if it is newer than the version stamped in your installed copy, tell the user to re-download it. Credentials are NOT tool arguments: the connection authenticates with OAuth (Authorization: Bearer, set by your MCP client). | Read-only |
| get-instruments-overview | Batch overview of 1 to 100 eToro instruments in ONE call — the FIRST tool for ANY question about an instrument or market: current price, spread, recent performance, whether and how the user can trade it. Use it BEFORE prepare-trade when exploring a trade, and instead of composing market-data calls via execute-read. BATCH-FIRST: 1 and 100 instruments cost the SAME single call, so ALWAYS pass every instrument of interest in one call — NEVER loop this tool per instrument. Identify instruments by 'symbols' (tickers) and/or 'instrumentIds' (at most 100 combined), or pass 'query' (free-text name/ticker search, mutually exclusive with the other two) when the exact symbol is unknown; its top matches feed the same pipeline in search relevance order. Returns per instrument: market identity (symbol, name, logos), a live quote (ask = the price you buy at, bid = the price you sell at, spread, asOf), recent performance (previousClose plus daily/weekly/monthly change % computed from official closing prices against the live rate) and the user's trading eligibility summary (allowOpenPosition, min position exposure, max units per order, allowed long/short leverages, MIT/entry-order/trailing-stop-loss support, W-8BEN requirement, fractional/whole units). Eligibility reflects the CONNECTION's account — there is no account argument. Unknown symbols/ids are reported in notFoundSymbols/notFoundInstrumentIds, never as an error while at least one instrument resolved. 'warnings' names sections that degraded (live quote, performance, eligibility, metadata) — the matching fields are null and everything else stays authoritative. Read-only and idempotent; quotes move, so re-call rather than cache. Authentication travels on the MCP connection, never as an argument. On a 429 wait retryAfterSeconds before retrying. On THIS server the connection authenticates with OAuth only: your MCP client sends `Authorization: Bearer <token>` after the user signs in; `x-user-key` / `x-api-key` headers are not accepted. There is no write tool on this server. | Read-only |
| get-my-balances | Returns EVERY account the connected eToro user holds — Trading (including its sub-accounts), Cash, Crypto, Options, MoneyFarm, Spaceship and Plaee — in ONE call. Reach for this on 'how much money do I have', 'what is my balance', 'how much can I spend' and any question about funds outside the Trading account; get-my-portfolio-summary covers Trading holdings and P&L only. The aggregator's response is relayed VERBATIM under 'balances': this tool converts nothing, sums nothing and subtotals nothing. READ 'fieldGuide' BEFORE reading any number. It carries one entry per account type present and names the field holding that type's SPENDABLE figure, because it is a DIFFERENT field per type: 'equityDetails.available' for Trading, Cash, Options, MoneyFarm and Plaee; 'equityDetails.spendableBalanceInFiat' for Crypto; and NOTHING for Spaceship, which carries no equityDetails object at all. Never assume 'available' exists. 'totalBalance' and each row's 'balance'/'displayBalance' are PORTFOLIO VALUE, not spendable cash — the single exception is a Cash account, where balance equals available. CURRENCY: every equityDetails amount is denominated in that account's OWN native currency (the row's 'currency' field), NEVER in the requested displayCurrency, and the equityDetails object carries no currency marker of its own — a GBP cash account reports available in GBP right next to a displayBalance in USD. Convert using the row's 'exchangeRate' before comparing figures or quoting one number; this tool will not do it for you, and it never sums spendable figures across accounts (Crypto spendable cannot fund an equity trade). SUB-ACCOUNTS arrive as accountType 'Trading' with subType 'subAccount', named by 'equityDetails.username'. Only APPROVED Trading sub-accounts appear, so the set may be smaller than the user's own list — 'notes' says so; present what came back, never as a complete list of their sub-accounts. Authentication is NOT a tool argument: credentials travel on the MCP connection itself — an OAuth 'Authorization: Bearer' header, or an 'x-user-key' + 'x-api-key' header pair configured on the MCP server entry. Nothing to pass here; if the call reports missing credentials, the CONNECTION needs configuring. This route requires the 'etoro-public:money.balance:read' scope, a SEPARATE grant NOT implied by 'etoro-public:real:read' or any account umbrella. 'error' is set only for tool-level failures; statusCode relays the upstream status faithfully (0 = timeout/unreachable — safe to retry). On a 429 always wait retryAfterSeconds before retrying. A 502 or a statusCode 0 means the balance COULD NOT BE READ: it is never a zero balance and must never be reported as one. On THIS server the connection authenticates with OAuth only: your MCP client sends `Authorization: Bearer <token>` after the user signs in; `x-user-key` / `x-api-key` headers are not accepted. There is no write tool on this server. | Read-only |
| get-my-portfolio-summary | The connected user's portfolio in one call. KEEP THE ANSWER SMALL: instrumentIds or symbols for specific assets; sortBy with a small limit for a ranked list (for example '-acctCcyReturn' for winners, 'acctCcyReturn' for losers); limit 0 for only the totals and the holding count (page.instrumentCount: instruments, not positions), with no rows (pendingOrders still come back unless includeOrders=false); includeOrders=false, includeLogos=false or includeCopiedTraders=false to drop those parts. Totals cover the WHOLE account: totalValue is the holdings' values plus balance (cash, including frozenCash); availableCash is the part you can spend. Every holding comes back unless you pass limit or cursor. To read on, pass page.next as cursor and nothing else. Each holding row has market.symbol and market.instrumentId. ordersExist marks a holding with pending orders; pendingOrders (with includeOrders) also lists orders on instruments you do not hold, with their status; get-my-positions-and-orders has the full order detail. Values move while you page, so do not present numbers from different pages as one moment. On 429 wait retryAfterSeconds. Check warnings for degraded parts, and error for a failed call. On THIS server the connection authenticates with OAuth only: your MCP client sends `Authorization: Bearer <token>` after the user signs in; `x-user-key` / `x-api-key` headers are not accepted. There is no write tool on this server. | Read-only |
| get-my-positions-and-orders | Returns the connected user's open positions and pending orders, direct and copy-trading mirrors kept apart. Every position comes back in one answer, largest invested first, unless you set limit: then it pages and accounts over 25 positions get compact rows (page.detail, page.detailNote; detail='full' for rates, leverage, stop/take-profit). Read 'page' first: total, returned, omitted, 'other', 'complete'. omitted is total minus the rows on THIS page, not what is left to read; complete=true with no page.next means you have everything. Narrow with symbols (tickers), instrumentIds or scope ('all', 'direct' or a mirrorId); continue with page.next as cursor, nothing else. A null 'direct' or 'mirrors' means outside the requested scope, not empty. Pending orders come with the first page only; a missing field means 'not included'. Order status is one of: received, placed, pendingTriggerRate, filled, rejected, partiallyFilled, pendingCancel, canceled, expired, canceledPartiallyFilled, rejectedPartiallyFilled, waitingForMarket. pnl and pnlPercent are UNREALIZED and live; realized profit is in get-my-trading-history. Amounts are in accountCurrency. A stopLossRate or takeProfitRate near zero (for example 0.0001) is an upstream placeholder, not a real stop. Prices move while you page: P&L and rates can change between calls and pages (page.liveNote), so never present numbers from different pages as one moment. On statusCode 429 wait retryAfterSeconds; 0 is a timeout and is safe to retry. 'warnings' lists degraded parts or ignored arguments; 'error' means the call failed. Credentials travel on the connection, never as arguments. On THIS server the connection authenticates with OAuth only: your MCP client sends `Authorization: Bearer <token>` after the user signs in; `x-user-key` / `x-api-key` headers are not accepted. There is no write tool on this server. | Read-only |
| get-my-profile-and-scopes | Returns WHO is connected on this MCP connection in ONE call — the FIRST tool to reach for on 'who am I', 'which account is this' or 'what is this connection allowed to do'. The connected user's profile comes back under 'profile': 'gcid' (the global user id), 'realCid' and 'demoCid' (the real and demo account ids other routes call 'cid'), 'username', 'firstName', 'middleName', 'lastName', 'playerLevel', 'gender', 'language', 'dateOfBirth', 'avatarUrl', and 'scopes' — the OAuth scopes ACTUALLY GRANTED to this connection's token or key. playerLevel is 1 Bronze, 2 Platinum, 3 Gold, 4 Internal, 5 Silver, 6 PlatinumPlus, 7 Diamond; gender is 0 Unknown, 1 Male, 2 Female. Scope names are self-describing (e.g. 'etoro-public:trade.real:write' = may place real-account trades); two non-obvious rules: 'etoro-public:real:write' / 'etoro-public:real:read' are full-account umbrellas that INCLUDE the matching trade.real permissions, while 'etoro-public:money.balance:read' and 'etoro-public:market-data:read' are separate grants NOT implied by an account umbrella. Scopes reflect what the CONNECTION was granted, not user-level account state (e.g. a trading block still surfaces only when placing). 'authChannel' reports how the connection authenticated: 'bearer' (OAuth) or 'keys' (x-user-key + x-api-key). The profile carries personal data (name, date of birth) — use it to answer the user's question, and do not repeat those fields back unless they asked for them. Authentication is NOT a tool argument: credentials travel on the MCP connection itself — an OAuth 'Authorization: Bearer' header, or an 'x-user-key' + 'x-api-key' header pair configured on the MCP server entry. Nothing to pass here; if the call reports missing credentials, the CONNECTION needs configuring. 'error' is set only for tool-level failures; statusCode relays the upstream status faithfully (0 = timeout/unreachable — safe to retry). On a 429 always wait retryAfterSeconds before retrying. On THIS server the connection authenticates with OAuth only: your MCP client sends `Authorization: Bearer <token>` after the user signs in; `x-user-key` / `x-api-key` headers are not accepted. There is no write tool on this server. | Read-only |
| get-my-trading-history | Returns CLOSED trades (trading history) in ONE call, paginated. Each trade carries symbol/name, direction, leverage, open/close time and rate, units, investment, fees, and netProfit — the REALIZED (final, closed) profit/loss, a different concept from get-my-positions-and-orders' 'pnl' (unrealized, still-open). netProfit does NOT include fees — fees is a separate, additional cost not deducted from netProfit; subtract fees from netProfit yourself for the fully-loaded result. 'parentPositionId', when non-zero, is the position ID of the copied trader's own position that this trade mirrors — confirming the trade was part of a copy-trading (mirror) position, and 'isMirrorTrade' is simply that check as a boolean; 'socialTradeId' (null when not a copy-trading fill) is a corroborating field for the same mirror relationship. 'stopLossRate'/'takeProfitRate' are always present as numbers on this route (confirmed against live data) — never null or omitted, unlike get-my-positions-and-orders' position-level fields. A trade with no stop-loss/take-profit actually set can come back as a near-zero placeholder (e.g. 0.0001) rather than null, so do not treat either field's presence as proof it was active. 'minDate' defaults to 90 days ago when omitted (format YYYY-MM-DD); pass an explicit date for a longer or shorter window. 'page' (default 1) and 'pageSize' (default 50, capped at 200) are passed straight through to the upstream API, which has NO total-count field — 'hasMore' is a heuristic: true when the returned count equals the requested pageSize, false otherwise — if upstream ever serves fewer rows than the requested pageSize even though more trades exist, hasMore would incorrectly read false, so treat it as a useful signal, not a guarantee, in either direction. Amounts are in the account's currency (not included per-trade — the upstream API itself does not carry a currency field on these rows); the account's own currency code is available from get-my-portfolio-summary's or get-my-positions-and-orders' response if you need to label these amounts explicitly. 'account' selects real or demo (default 'real'). Authentication is NOT a tool argument: credentials travel on the MCP connection itself. 'error' is set only for tool-level failures; statusCode relays the upstream status faithfully (0 = timeout/unreachable — safe to retry; note this route answers 404 for a MALFORMED request, not "no trades found" — an empty result set is a 200 with an empty list). A request spanning much more than 90 days from minDate to today is known to be slower upstream and can time out (statusCode 0) on a wide range — this is an upstream characteristic, not something this tool works around, so prefer a more recent minDate and treat a timeout as a signal to narrow the range and retry. On a 429 always wait retryAfterSeconds before retrying. On THIS server the connection authenticates with OAuth only: your MCP client sends `Authorization: Bearer <token>` after the user signs in; `x-user-key` / `x-api-key` headers are not accepted. There is no write tool on this server. | Read-only |
| get-my-watchlists | Returns the connected user's WATCHLISTS in ONE call — the FIRST tool to reach for on 'what is on my watchlist', 'show my watchlists' or 'which instruments am I watching'. The upstream document comes back under 'watchlists', relayed VERBATIM from the Public API's watchlists route (watchlist BFF V2): 'status', 'isSucceeded', 'watchlists' (array of watchlist objects), optional 'exception', and 'meta' (pagination and limits). Each watchlist typically carries 'watchlistId', 'name', 'Gcid', 'watchlistType' (Static / Dynamic / RecentlyInvested / Default), 'totalItems', 'isDefault', 'isUserSelectedDefault', 'watchlistRank', optional 'dynamicUrl', 'items' (each with 'itemId', 'itemType', 'itemRank', optional 'itemAddedReason'/'itemAddedDate'/'market'), and optional 'relatedAssets'. 'meta' may include 'pageNumber', 'itemsPerPage', 'maxItemsInWatchlistLimit' and 'maxWatchlistsLimit'. Required scope is ANY ONE of: etoro-public:watchlist:read, etoro-public:watchlist:write, or a real/demo read/write umbrella. Authentication is NOT a tool argument: credentials travel on the MCP connection itself — an OAuth 'Authorization: Bearer' header, or an 'x-user-key' + 'x-api-key' header pair configured on the MCP server entry. Nothing to pass here; if the call reports missing credentials, the CONNECTION needs configuring. 'authChannel' reports how the connection authenticated: 'bearer' (OAuth) or 'keys' (x-user-key + x-api-key). 'error' is set only for tool-level failures; statusCode relays the upstream status faithfully (0 = timeout/unreachable — safe to retry). On a 429 always wait retryAfterSeconds before retrying. For pagination / related-assets query options beyond the route defaults, use execute-read on the same path. On THIS server the connection authenticates with OAuth only: your MCP client sends `Authorization: Bearer <token>` after the user signs in; `x-user-key` / `x-api-key` headers are not accepted. There is no write tool on this server. | Read-only |
| get-route-spec | Returns the full OpenAPI specification (parameters, request body, responses and all referenced schemas) for one READ route of the eToro Public API, including a Required scopes section (the OAuth scopes that grant access - any one of them) and a Rate limit section (base limit/window and whether the budget is shared across a group of endpoints, so you can pace requests and avoid 429s). Accepts a route id from get-all-routes (e.g. 'getAgentPortfolios'), a '<METHOD> <path>' pair (e.g. 'GET /api/v1/agent-portfolios'), or a partial match on id or path. Only routes listed by get-all-routes resolve; anything else answers 'not available on this server' - this server serves read routes only and cannot execute state-changing ones. After reading the spec, run the route with execute-read passing the route's relative path (and 'body' for a read-semantics POST route). The spec's Authentication section describes the eToro Public API in general; on this server only the connection's OAuth bearer applies. | Read-only |
| get-trader-profile-summary | Public profile of 1 to 100 eToro investors in ONE call — the FIRST tool for ANY question about a trader, popular investor or copy-trading candidate: who they are, performance, risk score, copier statistics and portfolio composition. Prefer it over composing rankings calls via execute-read. BATCH-FIRST: 1 and 100 usernames cost the SAME single call — ALWAYS pass every trader of interest at once, NEVER loop per trader. Returns per trader: profile identity (name, country, AUM tier, industry/sector tags), performance (gain for the requested period, annualized return, drawdowns, win ratio, profitable weeks/months), risk (current and max daily/monthly risk score, 1 lowest to 10 highest), copier statistics (copiers, copiers gain, copy investment share) and portfolio composition (exposure, leverage mix, long/short split, top traded instrument, activity). Gains and percentages are FRACTIONS (0.0432 = 4.32%); AUM is whole USD. This is PUBLIC data about OTHER traders — for the connected user's own holdings use get-my-portfolio-summary. Usernames the rankings surface will not answer for come back in notFoundUsernames — the upstream deliberately does not distinguish nonexistent, private and unranked (a single-username lookup relays that as statusCode 404 with no error). Authentication is NOT a tool argument: credentials travel on the MCP connection itself — an OAuth 'Authorization: Bearer' header, or an 'x-user-key' + 'x-api-key' header pair configured on the MCP server entry. Nothing to pass here; if the call reports missing credentials, the CONNECTION needs configuring. 'error' is set only for tool-level failures; statusCode relays the upstream status faithfully (0 = timeout/unreachable — safe to retry). On a 429 always wait retryAfterSeconds before retrying. Rankings refresh periodically, so brief caching is fine; re-call for a fresh period or roster. On THIS server the connection authenticates with OAuth only: your MCP client sends `Authorization: Bearer <token>` after the user signs in; `x-user-key` / `x-api-key` headers are not accepted. There is no write tool on this server. | Read-only |
Change history
- get-my-positions-and-orders: input schema changed (+cursor, +detail, +includeLogos, +includeOrders, +instrumentIds, +limit, +scope, +symbols)
- get-my-positions-and-orders: description changed (+"connected user's open" +"orders, direct and copy-trading mirrors kept apart. Every position comes back" +"one answer, largest invested first, unless you set limit: then it pages")
- get-my-portfolio-summary: input schema changed (+cursor, +detail, +includeLogos, +instrumentIds, +limit, +sortBy, +symbols)
- get-my-portfolio-summary: description changed (+"The" +"one call. KEEP THE ANSWER SMALL: instrumentIds or symbols for specific assets; sortBy with a small limit for a ranked list (for example '-acctCcyReturn' for winners, 'acctCcyReturn' for losers); limit 0" +"only")
- MCP URL changed from "https://mcp.public-api.etoro.com/" to "https://mcp-readonly.public-api.etoro.com/" (claude.com)
- execute-read: description changed (+"The body comes back whole (bodyTruncated false); should bodyTruncated ever be true, the body was cut and is not complete JSON — narrow the request instead of reasoning over it.")
- execute-read: description changed (+"A response body over 16 MB is not returned at all, not even in part: 'error' says so next to the upstream statusCode — narrow the request (a smaller page size, the route's filter parameters, or a dedicated tool such as get-instruments-overview) instead of repeating it.")
- Listed (directory snapshot)
- Listed (claude.com)
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| claude.com listing page | b173ac5f-4342-42f5-b3a6-b0750f4565d3 | 10 Oct 2026 | 16 Nov 2026 | 2 |
| MCPTop directory snapshot | anthropic:b173ac5f-4342-42f5-b3a6-b0750f4565d3 | 10 Oct 2026 | 16 Nov 2026 | 1 |