xyz.cabalspy/wallet-tracker
REMOTE · MCP.CABALSPY.XYZ
KOL and smart money tracking on 5 chains, plus CabalSpy ID (SocialFi): verified traders, theses.
Available components
Last scanned (3 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 11553 tokens (~304/item across 38 items; 38 tools + 0 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 38 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 39 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
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.
- 1 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “csid_copy_trading” functional
- 31 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “csid_competitions” rewrote its description, which is the text the model reads security
- Schema quality: 8383 → 10824 ▼ functional
- Schema quality: 8383 → 9306 ▼ functional
- New tool “csid_callout_leaderboard” functional
- New tool “csid_callout_stats” functional
- New tool “csid_callouts” functional
- New tool “csid_competitions” functional
- New tool “csid_platform_leaderboard” functional
- New tool “csid_platform_user” functional
- 27 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “get_call_stats” functional
- New tool “get_calls” functional
- 15 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_leaderboard” rewrote its description, which is the text the model reads security
- Schema quality: 5318 → 7697 ▼ functional
- New tool “csid_kols” functional
- New tool “csid_latest_theses” functional
- New tool “csid_leaderboard” functional
- New tool “csid_profile” functional
- New tool “csid_thesis” functional
- New tool “csid_token_theses” functional
- New tool “csid_user_theses” functional
- New tool “csid_wallet_owner” functional
- “compare_tokens” reworded the description of “blockchain” cosmetic
- “compare_wallets” reworded the description of “blockchain” cosmetic
- “get_activity_metrics” reworded the description of “blockchain” cosmetic
- “get_analytics” reworded the description of “blockchain” cosmetic
- “get_leaderboard” reworded the description of “blockchain” cosmetic
- “get_pnl_calendar” reworded the description of “blockchain” cosmetic
- “get_recent_trades” reworded the description of “blockchain” cosmetic
- “get_signal_history” reworded the description of “blockchain” cosmetic
- “get_signals” reworded the description of “blockchain” cosmetic
- “get_token_holders” reworded the description of “blockchain” cosmetic
- “get_token_stats” reworded the description of “blockchain” cosmetic
- “get_token_transactions” reworded the description of “blockchain” cosmetic
- “get_wallet_connections” reworded the description of “blockchain” cosmetic
- “get_wallet_history” reworded the description of “blockchain” cosmetic
- “get_wallet_holdings” reworded the description of “blockchain” cosmetic
- “get_wallet_tracker” reworded the description of “blockchain” cosmetic
- “list_wallets” reworded the description of “blockchain” cosmetic
- 2 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “compare_tokens” rewrote its description, which is the text the model reads security
- Tool “compare_wallets” rewrote its description, which is the text the model reads security
- Tool “detect_bundles” rewrote its description, which is the text the model reads security
- Tool “get_activity_metrics” rewrote its description, which is the text the model reads security
- Tool “get_analytics” rewrote its description, which is the text the model reads security
- Tool “get_api_status” rewrote its description, which is the text the model reads security
- Tool “get_leaderboard” rewrote its description, which is the text the model reads security
- Tool “get_pnl_calendar” rewrote its description, which is the text the model reads security
- Tool “get_recent_trades” rewrote its description, which is the text the model reads security
- Tool “get_signal_history” rewrote its description, which is the text the model reads security
- Tool “get_signals” rewrote its description, which is the text the model reads security
- Tool “get_started” rewrote its description, which is the text the model reads security
- Tool “get_token_holders” rewrote its description, which is the text the model reads security
- Tool “get_token_stats” rewrote its description, which is the text the model reads security
- Tool “get_token_transactions” rewrote its description, which is the text the model reads security
- Tool “get_wallet_connections” rewrote its description, which is the text the model reads security
- Tool “get_wallet_history” rewrote its description, which is the text the model reads security
- Tool “get_wallet_holdings” rewrote its description, which is the text the model reads security
- Tool “get_wallet_tracker” rewrote its description, which is the text the model reads security
- Tool “list_wallets” rewrote its description, which is the text the model reads security
- Tool “lookup_wallet” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Aug 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 · Probed https://mcp.cabalspy.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.cabalspy.xyz | CN=YE1,O=Let's Encrypt,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5b2b0b13207487b09f94c0cfac90558bf5c |
| SANs: mcp.cabalspy.xyz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.cabalspy.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| cabalspy.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.cabalspy.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.cabalspy.xyz/mcp | HTTPS enforced | 301 | https://mcp.cabalspy.xyz/mcp |
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 →
compare_tokens ~213
Statistics for up to 100 tokens in a single request. Use for shortlists, or to follow up on the most-traded analytics view. blockchain: solana, bnb, base, eth or rh mints: up to 100 token addresses wallet_type: kol, smart or whale (default kol)
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| mints | array | yes | Up to 100 token addresses. Use for shortlists, or to follow up on the most_traded analytics view. |
| wallet_type | string | – | Wallet type. kol is a Key Opinion Leader, an influencer whose calls move markets. smart is a wallet selected for its track record. whale is a large holder, Solana only. |
Structured output declared, but exposes no named fields.
No examples provided.
compare_wallets ~286
Statistics for up to 100 wallets in a single request. Much cheaper than calling get_wallet_tracker repeatedly. Use when the user names several wallets, or to follow up on a leaderboard. blockchain: solana, bnb, base, eth or rh addresses: up to 100 wallet addresses wallet_type: kol, smart or whale (default kol) period: 6h, 1d, 7d or 30d (default 7d)
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | Up to 100 wallet addresses. Far cheaper than calling get_wallet_tracker once per wallet. |
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| period | string | – | Statistics window: 6h, 1d, 7d or 30d. Longer windows return far more data and get trimmed harder, so prefer the shortest window that answers the question. |
| wallet_type | string | – | Wallet type. kol is a Key Opinion Leader, an influencer whose calls move markets. smart is a wallet selected for its track record. whale is a large holder, Solana only. |
Structured output declared, but exposes no named fields.
No examples provided.
csid_callout_leaderboard ~424
The best callers of YOUR CabalSpy ID instance for a period (6h, 1d, 7d, 30d): each user's callouts in the period, scored by their peak multiples (score_x), with average, median, best and summed peak multiple, hits and hit rate (share of callouts that reached hit_x), and their best call. Entries carry your own user id (external_id). Use for "Who are the best callers this week?". Callouts are an extra switched on per instance on request; otherwise this returns feature_not_enabled. Needs your own CabalSpy API key with a CabalSpy ID instance (no demo).
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Restrict to one blockchain: solana, bnb, base, eth or rh. Leave empty for all. |
| cursor | string | – | Pagination cursor taken from the previous response. Leave empty for the first page. |
| hit_x | number | – | The peak multiple that counts as a hit for hits and hit_rate_percent, e.g. 2 for a 2x (default 2, above 1 and at most 1000). |
| instance | string | – | Your CabalSpy ID instance (its client_id, e.g. 'csid_1a2b…'). Only needed when your account has several instances. Leave empty otherwise. |
| limit | integer | – | How many callers (1-50, default 10). |
| min_callouts | integer | – | Only callers with at least this many callouts in the period (1-1000, default 1). Raise it to keep one lucky call from topping the average. |
| period | string | – | Callouts made in the last 6h, 1d, 7d (default) or 30d. |
| sort | string | – | avg_peak_x (default), best_peak_x, sum_peak_x, hit_rate, callouts or median_peak_x. |
Structured output declared, but exposes no named fields.
No examples provided.
csid_callout_stats ~354
The callout track record of ONE user of YOUR CabalSpy ID instance, per period (callouts made in the last 6h, 1d, 7d and 30d): number of callouts, average, median, best and summed peak multiple (score_x), hits and hit rate (share that reached hit_x), the average multiple right now and how many are still being tracked, plus the all-time count. Use for "How good are this user's calls?". Pass external_id (your user id) or csid_id. Callouts are an extra switched on per instance on request; otherwise this returns feature_not_enabled. Needs your own CabalSpy API key with a CabalSpy ID instance (no demo).
| Name | Type | Req | Description |
|---|---|---|---|
| csid_id | string | – | Only this user: their CabalSpy ID user id (UUID), for users who signed in with CabalSpy ID themselves. Pass external_id or csid_id, not both. |
| external_id | string | – | Only this user: their id on YOUR platform (external_id), as passed when the user was created or imported. Pass external_id or csid_id, not both. |
| hit_x | number | – | The peak multiple that counts as a hit for hits and hit_rate_percent, e.g. 2 for a 2x (default 2, above 1 and at most 1000). |
| instance | string | – | Your CabalSpy ID instance (its client_id, e.g. 'csid_1a2b…'). Only needed when your account has several instances. Leave empty otherwise. |
Structured output declared, but exposes no named fields.
No examples provided.
csid_callouts ~482
Callouts on YOUR CabalSpy ID instance, newest first: users call a token and CabalSpy stamps the price and market cap and tracks it. Without filters the latest callouts of your platform; with chain + mint the callouts of one token ("Who called this token and how did it do?"); with external_id or csid_id the callouts of one user. Each entry: token, author (your user id), called_at, market cap at the call, now_x and peak_x (multiples since the call), score_x (the peak multiple the callout is scored by) and the tracking phase (first_day: every minute for 24 h, then scored on candles; extended: every 5 minutes while active; stopped: after 24 h in a row below a $10k market cap). Callouts are an extra switched on per instance on request; otherwise this returns feature_not_enabled. Needs your own CabalSpy API key with a CabalSpy ID instance (no demo).
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Only callouts on this blockchain: solana, bnb, base, eth or rh. Required together with mint. Leave empty for all chains. |
| csid_id | string | – | Only this user: their CabalSpy ID user id (UUID), for users who signed in with CabalSpy ID themselves. Pass external_id or csid_id, not both. |
| cursor | string | – | Pagination cursor taken from the previous response. Leave empty for the first page. |
| external_id | string | – | Only this user: their id on YOUR platform (external_id), as passed when the user was created or imported. Pass external_id or csid_id, not both. |
| instance | string | – | Your CabalSpy ID instance (its client_id, e.g. 'csid_1a2b…'). Only needed when your account has several instances. Leave empty otherwise. |
| limit | integer | – | How many callouts (1-50, default 10). |
| mint | string | – | Only callouts of this token (mint on Solana, contract on EVM); needs chain. Answers 'who called this token and how did it do'. |
Structured output declared, but exposes no named fields.
No examples provided.
csid_competitions ~340
Competitions of YOUR platform (white-label): without competition_id the list (name, kind, chain, metric, status, start and end, participants); with it the rules, every rule change and the current standings with your own user ids (standings are recomputed every 5 minutes, final once ended). Use for "Who is leading the competition?" or "Which competitions are running?". 'kind' is 'trading' (ranked on trades: pnl_usd, pnl, volume, trades, win_rate; min_trades / min_volume_usd) or 'callouts' (ranked on the callouts made during the competition, each scored by its peak multiple: avg_peak_x, best_peak_x, sum_peak_x, hit_rate, callouts; min_callouts to qualify, hit_x = the multiple that counts as a hit). Needs your own CabalSpy API key with a CabalSpy ID instance (no demo).
| Name | Type | Req | Description |
|---|---|---|---|
| competition_id | string | – | A competition id from a previous call. Empty lists your competitions; set it for the rules and the standings. |
| instance | string | – | Your CabalSpy ID instance (its client_id, e.g. 'csid_1a2b…'). Only needed when your account has several instances. Leave empty otherwise. |
| limit | integer | – | How many competitions or standings rows (1-50, default 10). |
| status | string | – | When listing: scheduled, waiting, running, ended or cancelled. Empty lists all. |
Structured output declared, but exposes no named fields.
No examples provided.
csid_copy_trading ~592
Copy trading on YOUR CabalSpy ID instance. Copy trading turns every trade of a trader in a user's Trade Feed into a ready-to-execute instruction: token, chain, side, the amount in USD (buys) or the share of the copied position to sell (sells), and a price limit. Your platform executes it with the user's own wallet and reports it back as executed, failed or skipped. CabalSpy never holds keys and never trades. Instructions are meant to be executed within 120 seconds; a pending one past that reads as 'expired'. view=instructions (default): the latest instructions of your platform, or of one user (external_id or csid_id), optionally by status. Each: id, status, created_at, user, trader, side, token, chain, mint, amount_usd or sell_percent, price_usd and the max/min price limit, plus what your platform reported (executed_amount_usd, tx_signature, note). Use for "Which copy trades failed today?". view=settings: one user's copy settings per trader (enabled, mode fixed_usd or percent, amount_usd, percent, max_usd cap, sides buys or both, slippage_bps, and managed_by_other_platform when another platform copies that trader). Part of every CabalSpy ID instance (no extra needed); users need the 'trade_feed' consent (otherwise consent_required). Read-only: changing settings and reporting status stays in the Data API. Needs your own CabalSpy API key with a CabalSpy ID instance (no demo).
| Name | Type | Req | Description |
|---|---|---|---|
| csid_id | string | – | Only this user: their CabalSpy ID user id (UUID). Pass external_id or csid_id, not both; required for view=settings. |
| cursor | string | – | Pagination cursor taken from the previous response. Leave empty for the first page. |
| external_id | string | – | Only this user: their id on YOUR platform (external_id). Pass external_id or csid_id, not both; required for view=settings. |
| instance | string | – | Your CabalSpy ID instance (its client_id, e.g. 'csid_1a2b…'). Only needed when your account has several instances. Leave empty otherwise. |
| limit | integer | – | How many instructions (1-50, default 10). |
| status | string | – | view=instructions only: pending, executed, failed, skipped or expired. Leave empty for all. |
| view | string | – | 'instructions' (default): the copy instructions sent to your platform, newest first. 'settings': one user's copy settings per trader in their Trade Feed (needs external_id or csid_id). |
Structured output declared, but exposes no named fields.
No examples provided.
csid_kols ~198
KOLs with a verified CabalSpy ID badge (reviewed: real X account with reach, wallets proven on-chain), newest badge first. Each entry has the X handle, followers, verified wallets and 7-day activity. Use for "Which KOLs are verified on Base?" or to get wallets of verified influencers. For performance rankings of tracked KOL wallets use get_leaderboard instead. chain: solana, bnb, base, eth or rh — only KOLs with a wallet verified there.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Restrict to one blockchain: solana, bnb, base, eth or rh. Leave empty for all. |
| cursor | string | – | Pagination cursor taken from the previous response. Leave empty for the first page. |
| limit | integer | – | How many KOLs to return (1-50, default 20). |
Structured output declared, but exposes no named fields.
No examples provided.
csid_latest_theses ~277
The newest theses across all tokens: a live feed of what verified holders are posting, each with token, stance, author and position. Use for "What are verified traders talking about right now?" or to discover tokens with fresh conviction. For one token use csid_token_theses. Needs your own CabalSpy API key with a CabalSpy ID instance (no demo).
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | – | Restrict to one blockchain: solana, bnb, base, eth or rh. Leave empty for all. |
| cursor | string | – | Pagination cursor taken from the previous response. Leave empty for the first page. |
| instance | string | – | Your CabalSpy ID instance (its client_id, e.g. 'csid_1a2b…'). Only needed when your account has several instances. Leave empty otherwise. |
| limit | integer | – | How many theses to return (1-25, default 10). |
| scope | string | – | 'global' (default): theses posted on every platform that uses CabalSpy ID. 'instance': only theses written on your own CabalSpy ID instance. |
| users | string | – | 'all' (default): every author. 'instance': only users of your CabalSpy ID instance. |
Structured output declared, but exposes no named fields.
No examples provided.
csid_leaderboard ~384
Ranking of CabalSpy ID verified traders by their tracked trades: volume, realized PnL, win rate and trade count for a period. Covers the users of YOUR CabalSpy ID instance (the people who signed in on your platform); scope='global' ranks every CabalSpy ID user and needs the Enterprise plan. Use for "Who are the best traders on my platform this week?". For KOLs and smart money tracked by CabalSpy use get_leaderboard. Needs your own CabalSpy API key with a CabalSpy ID instance (no demo).
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| cursor | string | – | Pagination cursor taken from the previous response. Leave empty for the first page. |
| instance | string | – | Your CabalSpy ID instance (its client_id, e.g. 'csid_1a2b…'). Only needed when your account has several instances. Leave empty otherwise. |
| limit | integer | – | How many traders (1-50, default 10). |
| period | string | – | Statistics window: 6h, 1d, 7d or 30d. Longer windows return far more data and get trimmed harder, so prefer the shortest window that answers the question. |
| scope | string | – | 'instance' (default): the users of your CabalSpy ID instance. 'global': every CabalSpy ID user, Enterprise plan only. |
| sort | string | – | volume (default), pnl (native currency), pnl_usd, win_rate or trades. |
Structured output declared, but exposes no named fields.
No examples provided.
csid_platform_leaderboard ~367
Ranking of the users of YOUR platform (white-label) by their trades on one chain: realized PnL, volume, win rate and trade count for a period, each entry with your own user id (external_id). Use for "Who are the top traders on my platform this week?" when your users are imported into a CabalSpy ID instance. For users who sign in with CabalSpy ID themselves use csid_leaderboard. Needs your own CabalSpy API key with a CabalSpy ID instance (no demo).
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| cursor | string | – | Pagination cursor taken from the previous response. Leave empty for the first page. |
| instance | string | – | Your CabalSpy ID instance (its client_id, e.g. 'csid_1a2b…'). Only needed when your account has several instances. Leave empty otherwise. |
| limit | integer | – | How many traders (1-50, default 10). |
| period | string | – | Statistics window: 6h, 1d, 7d or 30d. Longer windows return far more data and get trimmed harder, so prefer the shortest window that answers the question. |
| sort | string | – | pnl_usd (default), pnl (native currency), volume, win_rate or trades. |
| verified_only | boolean | – | True ranks only payment-verified wallets. The instance setting leaderboard_trust can already enforce this. |
Structured output declared, but exposes no named fields.
No examples provided.
csid_platform_user ~282
One user of YOUR platform (white-label), looked up by your own user id: display name, wallets with their trust status, X/Telegram/KOL badge, trading stats per chain for the period (volume, realized PnL, win rate), the latest trades and theses. Use for "How is user 42 on my platform doing this week?". Only for platforms that import their users into a CabalSpy ID instance (white-label). For CabalSpy ID users who signed in themselves use csid_profile. Needs your own CabalSpy API key with a CabalSpy ID instance (no demo).
| Name | Type | Req | Description |
|---|---|---|---|
| external_id | string | yes | The user's id on YOUR platform (external_id), as you passed it when the user was created or imported, e.g. 'did:privy:abc123' or '42'. |
| instance | string | – | Your CabalSpy ID instance (its client_id, e.g. 'csid_1a2b…'). Only needed when your account has several instances. Leave empty otherwise. |
| period | string | – | Statistics window: 6h, 1d, 7d or 30d. Longer windows return far more data and get trimmed harder, so prefer the shortest window that answers the question. |
Structured output declared, but exposes no named fields.
No examples provided.
csid_profile ~313
CabalSpy ID profile of a crypto trader: X account (followers, age), Telegram, KOL badge, the wallets they verified by an on-chain payment (per chain), and 7-day trading activity. Use it to check who someone is and whether a trader really owns the wallets they claim, e.g. "Is @CabalSpySol verified?", "Which wallets does this KOL trade with?". Pass exactly one of: username (X handle), csid_id, x_id, or address (looks up the owner of a wallet). Works on the keyless demo with sandbox identities only (try username 'csid_sandbox_kol').
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | A wallet address (Solana base58 or 0x EVM). Returns the person who verified it. |
| csid_id | string | – | CabalSpy ID user id (a UUID, the 'sub' of a Login with CabalSpy ID token), e.g. '123e4567-e89b-12d3-a456-426614174000'. |
| username | string | – | X (Twitter) handle of the person, with or without @, e.g. 'CabalSpySol'. Pass exactly one of username, csid_id, x_id or address. |
| x_id | string | – | Numeric X user id, e.g. '1234567890123456789'. Survives handle changes. |
Structured output declared, but exposes no named fields.
No examples provided.
csid_thesis ~216
One thesis in full with its discussion: body, stance, author, the author's position, reactions and the replies (oldest first). Use after another csid_ tool when the user wants to read a thread. cursor pages through the replies. Needs your own CabalSpy API key with a CabalSpy ID instance (no demo).
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor taken from the previous response. Leave empty for the first page. |
| instance | string | – | Your CabalSpy ID instance (its client_id, e.g. 'csid_1a2b…'). Only needed when your account has several instances. Leave empty otherwise. |
| replies_limit | integer | – | How many replies to include (0-50, default 20). |
| thesis_id | string | yes | Thesis id (UUID) from another csid_ tool, e.g. '7d4436ac-c0ef-4655-995f-10b06af94f21'. |
Structured output declared, but exposes no named fields.
No examples provided.
csid_token_theses ~430
What do verified holders think about a token? Returns the bull/bear summary and the latest (or top) theses: short posts that only people holding the token in a CabalSpy ID verified wallet can write, each with the author's live position (holding or sold, invested, PnL). Use for "What do holders say about $BONK?" or "Is sentiment on this token bullish?". Needs your own CabalSpy API key with a CabalSpy ID instance (no demo). Example: blockchain='solana', mint='DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263'. Page with the returned next_cursor.
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| cursor | string | – | Pagination cursor taken from the previous response. Leave empty for the first page. |
| instance | string | – | Your CabalSpy ID instance (its client_id, e.g. 'csid_1a2b…'). Only needed when your account has several instances. Leave empty otherwise. |
| limit | integer | – | How many theses to return (1-25, default 10). |
| mint | string | yes | Token address: the mint on Solana, the contract address on the EVM chains. |
| scope | string | – | 'global' (default): theses posted on every platform that uses CabalSpy ID. 'instance': only theses written on your own CabalSpy ID instance. |
| sort | string | – | 'new' (newest first, default) or 'top' (most liked first). |
| stance | string | – | Only bullish ('bull') or bearish ('bear') theses. Leave empty for all, including neutral ones. |
Structured output declared, but exposes no named fields.
No examples provided.
csid_user_theses ~260
All theses one CabalSpy ID user has posted, newest first, with token and the position they hold. Use to judge a caller's track record: "What has @CabalSpySol been bullish on, and did it work out?". Needs your own CabalSpy API key with a CabalSpy ID instance (no demo).
| Name | Type | Req | Description |
|---|---|---|---|
| csid_id | string | – | CabalSpy ID user id (a UUID, the 'sub' of a Login with CabalSpy ID token), e.g. '123e4567-e89b-12d3-a456-426614174000'. |
| cursor | string | – | Pagination cursor taken from the previous response. Leave empty for the first page. |
| instance | string | – | Your CabalSpy ID instance (its client_id, e.g. 'csid_1a2b…'). Only needed when your account has several instances. Leave empty otherwise. |
| limit | integer | – | How many theses to return (1-25, default 10). |
| username | string | – | X handle of the author, with or without @, e.g. 'CabalSpySol'. Pass username or csid_id. |
Structured output declared, but exposes no named fields.
No examples provided.
csid_wallet_owner ~179
Who owns a wallet? Returns the CabalSpy ID user who proved ownership with an on-chain payment (X handle, KOL badge, verified chains), or verified=false. Use it when a user pastes an address and asks who is behind it — e.g. "Who owns wallet X?" — and to find verified traders among a token's holders. Complements lookup_wallet (CabalSpy's own wallet labels). Several addresses at once count as one batch request.
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | string | yes | One wallet address, or up to 100 separated by commas (Solana and EVM mixed), e.g. 'HHTNJXn5zDoVtbnRpYVwr7tKmnMs94cMPsu8gK2aLG9X'. |
Structured output declared, but exposes no named fields.
No examples provided.
detect_bundles ~143
Check whether KOL wallets bought a Solana token through Jito bundles together with side wallets they control, which hides the real size of their position. Returns each detected bundle with a confidence score and the evidence behind it: matching transaction fees, block index, and adjacency to the KOL's own transaction. Use this when a user asks whether a launch was bundled, insider-heavy, sniped or manipulated. Solana only, because it depends on Jito bundles. mint: the Solana token mint address
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | The Solana token mint address to inspect for bundled buys. |
Structured output declared, but exposes no named fields.
No examples provided.
get_activity_metrics ~255
How many trades happened and how much value moved over a window of up to 24 hours, plus how many distinct wallets were involved. Use for how busy the market or a single token is, rather than for the individual trades. blockchain: solana, bnb, base, eth or rh wallet_type: kol, smart or whale (default kol) hours: window in hours, at most 24 (default 1) mint: restrict to one token
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| hours | integer | – | Observation window in hours. The server caps this at 24. |
| mint | string | – | Restrict the result to a single token. Leave empty for all tokens. |
| wallet_type | string | – | Wallet type. kol is a Key Opinion Leader, an influencer whose calls move markets. smart is a wallet selected for its track record. whale is a large holder, Solana only. |
Structured output declared, but exposes no named fields.
No examples provided.
get_analytics ~373
Four aggregate views over the tracked wallets. volume_trend shows activity over time. most_traded lists the tokens getting the most attention. win_rate gives the distribution of outcomes. top_performers ranks wallets by profit. Use for the overall picture rather than one wallet or token. blockchain: solana, bnb, base, eth or rh mode: volume_trend, most_traded, win_rate or top_performers wallet_type: kol, smart or whale (default kol) period: 6h, 1d, 7d or 30d (default 7d) limit: how many entries (default 20)
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| limit | integer | – | How many entries to return. Keep it small: large results are trimmed to fit the context window anyway. |
| mode | string | yes | volume_trend shows activity over time. most_traded lists the tokens getting the most attention. win_rate gives the distribution of outcomes. top_performers ranks wallets by profit. |
| period | string | – | Statistics window: 6h, 1d, 7d or 30d. Longer windows return far more data and get trimmed harder, so prefer the shortest window that answers the question. |
| wallet_type | string | – | Wallet type. kol is a Key Opinion Leader, an influencer whose calls move markets. smart is a wallet selected for its track record. whale is a large holder, Solana only. |
Structured output declared, but exposes no named fields.
No examples provided.
get_api_status ~56
Service health and current coverage: chains, wallet types, periods, limits and how many wallets are tracked per chain. Useful when a query returns nothing and it is unclear whether the data exists at all.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_call_stats ~268
How well the curated CabalSpy calls performed: per chain and tier the number of calls, the share that reached 2x, 5x and 10x within 24 hours, the median peak multiple and minutes to peak, plus the best calls of the period. Use this for "how good are CabalSpy calls" or "which tier works best". Only the first call per token, tier and day counts; calls without price data are left out of the hit rate. Calls from the last one to two days count as pending. period: 1d, 7d, 30d or 90d (default 7d) blockchain: solana, bnb, eth, rh, comma separated (default all) tier: gamble, moderate, good, big, whale, comma separated (default all)
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | – | Comma separated chains: solana, bnb, eth, rh. Empty for all chains. |
| period | string | – | 1d, 7d, 30d or 90d. |
| tier | string | – | Comma separated tiers: gamble, moderate, good, big, whale. Empty for all tiers. |
Structured output declared, but exposes no named fields.
No examples provided.
get_calls ~392
The curated CabalSpy calls, the same ones posted in the CabalSpy Discord, newest first. Each call has the token, the market cap at the call, the KOL and Smart Money wallets behind it, trading links, and its performance over the 24 hours after the call (peak multiple, minutes to peak, multiple after 24 h). Use this for "what did CabalSpy call" or "how did the call on this token do". These are fixed picks per tier; for wallet clusters with your own thresholds use get_signals instead. performance.status 'pending' means the call is younger than about two days and not measured yet, which is not a bad result. blockchain: solana, bnb, eth, rh, comma separated (default all) tier: gamble, moderate, good, big, whale, comma separated (default all) since / until: time window, ISO 8601 or Unix seconds limit: how many calls (default 15) cursor: next_cursor from the previous page
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | – | Comma separated chains: solana, bnb, eth, rh. Empty for all chains. |
| cursor | string | – | Pagination cursor taken from the previous response. Leave empty for the first page. |
| limit | integer | – | How many entries to return. Keep it small: large results are trimmed to fit the context window anyway. |
| since | string | – | Only calls at or after this time, ISO 8601 or Unix seconds. Empty for no limit. |
| tier | string | – | Comma separated tiers: gamble, moderate, good, big, whale. Empty for all tiers. |
| until | string | – | Only calls at or before this time, ISO 8601 or Unix seconds. Empty for no limit. |
Structured output declared, but exposes no named fields.
No examples provided.
get_leaderboard ~289
Top tracked wallets ranked by performance for a chain, wallet type and period. Use for "best Solana KOLs today", "top whales this week", and similar. blockchain: solana, bnb, base, eth or rh wallet_type: kol, smart or whale. whale is Solana only. period: 6h, 1d, 7d or 30d (default 1d) limit: how many wallets (default 20)
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| limit | integer | – | How many entries to return. Keep it small: large results are trimmed to fit the context window anyway. |
| period | string | – | Statistics window: 6h, 1d, 7d or 30d. Longer windows return far more data and get trimmed harder, so prefer the shortest window that answers the question. |
| wallet_type | string | – | Wallet type. kol is a Key Opinion Leader, an influencer whose calls move markets. smart is a wallet selected for its track record. whale is a large holder, Solana only. |
Structured output declared, but exposes no named fields.
No examples provided.
get_pnl_calendar ~152
Daily and monthly realized profit and loss for a wallet across its tracked history. Use for when a wallet made or lost money, and for spotting streaks. blockchain: solana, bnb, base, eth or rh address: the wallet address
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address. Base58 on Solana, 0x-prefixed hex on the EVM chains. |
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
Structured output declared, but exposes no named fields.
No examples provided.
get_recent_trades ~309
The live feed: what tracked wallets are buying and selling right now, across every token or filtered to one. Use for "what are KOLs buying at the moment". blockchain: solana, bnb, base, eth or rh wallet_type: kol, smart or whale (default kol) minutes: only trades from the last N minutes, at most 60. Leave at 0 for the most recent trades regardless of age. mint: restrict to one token limit: how many trades (default 25)
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| limit | integer | – | How many entries to return. Keep it small: large results are trimmed to fit the context window anyway. |
| mint | string | – | Restrict the result to a single token. Leave empty for all tokens. |
| minutes | integer | – | Only trades from the last N minutes, at most 60. Leave at 0 for the most recent trades regardless of age. |
| wallet_type | string | – | Wallet type. kol is a Key Opinion Leader, an influencer whose calls move markets. smart is a wallet selected for its track record. whale is a large holder, Solana only. |
Structured output declared, but exposes no named fields.
No examples provided.
get_signal_history ~280
Past signals, for checking whether a kind of signal has worked historically before acting on a live one. blockchain: solana, bnb, base, eth or rh wallet_type: kol, smart or whale (default kol) days: 7, 30, 90 or "all" (default 30) mode: cluster, entry or exit. Omit for all modes. limit: how many signals (default 25)
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| days | string | – | How far back to look: 7, 30, 90 or all. |
| limit | integer | – | How many entries to return. Keep it small: large results are trimmed to fit the context window anyway. |
| mode | string | – | Restrict to cluster, entry or exit. Leave empty for every mode. |
| wallet_type | string | – | Wallet type. kol is a Key Opinion Leader, an influencer whose calls move markets. smart is a wallet selected for its track record. whale is a large holder, Solana only. |
Structured output declared, but exposes no named fields.
No examples provided.
get_signals ~444
Tokens where several tracked wallets acted within the same window. 'cluster' means multiple wallets bought the same token, which is the strongest signal. 'entry' marks fresh positions, 'exit' marks wallets selling out. Use this for "what should I be looking at right now". Only the first page is reachable: this endpoint reports that more results exist but does not return a usable cursor, so raise the limit rather than trying to paginate. Smart money signals are unavailable on eth. blockchain: solana, bnb, base, eth or rh wallet_type: kol, smart or whale (default kol) mode: cluster, entry or exit (default cluster) hours: observation window (default 6) min_wallets: minimum wallets in a cluster; higher means fewer, stronger signals min_win_rate: only count wallets above this historical win rate, 0-100 limit: how many signals (default 15)
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| hours | integer | – | Observation window in hours. |
| limit | integer | – | How many entries to return. Keep it small: large results are trimmed to fit the context window anyway. |
| min_wallets | integer | – | Minimum wallets in a cluster. Higher means fewer but stronger signals. 0 uses the server default of 3. |
| min_win_rate | number | – | Only count wallets above this historical win rate, 0 to 100. 0 disables it. |
| mode | string | – | cluster means several wallets bought the same token, the strongest signal. entry marks fresh positions. exit marks wallets selling out. |
| wallet_type | string | – | Wallet type. kol is a Key Opinion Leader, an influencer whose calls move markets. smart is a wallet selected for its track record. whale is a large holder, Solana only. |
Structured output declared, but exposes no named fields.
No examples provided.
get_started ~81
How to use CabalSpy: the keyless demo, where to get a free API key (1000 requests, no cost), pricing, documentation, and what the data covers. Call this first if you do not have a key yet, or if another tool returned an auth error or 'demo_limit_reached'.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_token_holders ~245
The tracked wallets holding a token, sorted by balance, with market cap and price in USD on Solana. Use when the user asks who is still holding, rather than who ever traded it. blockchain: solana, bnb, base, eth or rh mint: token address wallet_type: restrict to kol, smart or whale. Omit to merge all types. limit: how many holders (default 25)
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| limit | integer | – | How many entries to return. Keep it small: large results are trimmed to fit the context window anyway. |
| mint | string | yes | Token address: the mint on Solana, the contract address on the EVM chains. |
| wallet_type | string | – | Restrict to one wallet type: kol, smart or whale. Leave empty to merge all types the chain has. |
Structured output declared, but exposes no named fields.
No examples provided.
get_token_stats ~259
Who is trading a token: how many KOLs, smart money wallets and whales hold it, total bought and sold, buying pressure, first and latest entry, and the individual traders with their positions. The main tool for "is anyone notable in this token". Note that market cap in USD comes back empty on this endpoint even for Solana; get_token_holders reports it. blockchain: solana, bnb, base, eth or rh mint: token mint address on Solana, contract address on the EVM chains wallet_type: restrict to kol, smart or whale. Omit to merge all types.
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| mint | string | yes | Token address: the mint on Solana, the contract address on the EVM chains. |
| wallet_type | string | – | Restrict to one wallet type: kol, smart or whale. Leave empty to merge all types the chain has. |
Structured output declared, but exposes no named fields.
No examples provided.
get_token_transactions ~240
Individual buys and sells by tracked wallets in one token, most recent first. Use for the sequence of events, for example whether KOLs bought before or after a price move. blockchain: solana, bnb, base, eth or rh mint: token address wallet_type: restrict to kol, smart or whale. Omit to merge all types. limit: how many transactions (default 25)
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| limit | integer | – | How many entries to return. Keep it small: large results are trimmed to fit the context window anyway. |
| mint | string | yes | Token address: the mint on Solana, the contract address on the EVM chains. |
| wallet_type | string | – | Restrict to one wallet type: kol, smart or whale. Leave empty to merge all types the chain has. |
Structured output declared, but exposes no named fields.
No examples provided.
get_wallet_connections ~196
Other tracked wallets that traded the same tokens as this one over the last 30 days, ranked by overlap. Useful for finding groups that move together, which can indicate coordination. blockchain: solana, bnb, base, eth or rh address: the source wallet address limit: how many connections (default 25)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address. Base58 on Solana, 0x-prefixed hex on the EVM chains. |
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| limit | integer | – | How many entries to return. Keep it small: large results are trimmed to fit the context window anyway. |
Structured output declared, but exposes no named fields.
No examples provided.
get_wallet_history ~267
Lifetime trading history of a wallet: aggregate stats, a per-token overview and the individual trades. Use for what a wallet traded historically, rather than how it is doing now. This endpoint returns its pagination inside the payload rather than alongside it; follow pagination.next_cursor until it is null for a full export. blockchain: solana, bnb, base, eth or rh address: the wallet address cursor: pagination cursor from the previous response limit: trades per page, 1-1000 (default 50; higher values get trimmed anyway)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address. Base58 on Solana, 0x-prefixed hex on the EVM chains. |
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| cursor | string | – | Pagination cursor taken from the previous response. Leave empty for the first page. |
| limit | integer | – | How many entries to return. Keep it small: large results are trimmed to fit the context window anyway. |
Structured output declared, but exposes no named fields.
No examples provided.
get_wallet_holdings ~171
Current onchain token holdings of a wallet, read live rather than derived from tracked trades. Slower than the other wallet tools, often over a second. If 'loading' is true the data is still warming up — call again shortly. blockchain: solana, bnb, base, eth or rh address: the wallet address
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address. Base58 on Solana, 0x-prefixed hex on the EVM chains. |
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
Structured output declared, but exposes no named fields.
No examples provided.
get_wallet_tracker ~249
Period statistics for ONE wallet: realized PnL, win rate, volume, trade counts, active tokens and win-rate distribution. The main tool for "how is this trader doing". blockchain: solana, bnb, base, eth or rh address: the wallet address period: 6h, 1d, 7d or 30d (default 1d). Longer periods return far more data and are trimmed harder; prefer the shortest period that answers it.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address. Base58 on Solana, 0x-prefixed hex on the EVM chains. |
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| period | string | – | Statistics window: 6h, 1d, 7d or 30d. Longer windows return far more data and get trimmed harder, so prefer the shortest window that answers the question. |
Structured output declared, but exposes no named fields.
No examples provided.
list_wallets ~255
Browse the wallets CabalSpy tracks for a chain and wallet type. Use this to answer which KOLs or smart money wallets are covered at all. Always pass a limit; the full list runs into the thousands. blockchain: solana, bnb, base, eth or rh wallet_type: kol, smart or whale limit: wallets per page (default 50) cursor: pagination cursor from the previous response
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | yes | Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2. |
| cursor | string | – | Pagination cursor taken from the previous response. Leave empty for the first page. |
| limit | integer | – | How many entries to return. Keep it small: large results are trimmed to fit the context window anyway. |
| wallet_type | string | yes | Wallet type. kol is a Key Opinion Leader, an influencer whose calls move markets. smart is a wallet selected for its track record. whale is a large holder, Solana only. |
Structured output declared, but exposes no named fields.
No examples provided.
lookup_wallet ~137
Identify a wallet address: is it tracked, and by what name. Returns the label CabalSpy attached to it — name, Twitter, Telegram, wallet type and chain. Start here when a user pastes an address and asks who it is. On EVM chains the same address can be tracked on several of them and only the first match is returned, so the reported chain may not be the intended one. address: the wallet address to look up
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address. Base58 on Solana, 0x-prefixed hex on the EVM chains. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the xyz.cabalspy/wallet-tracker MCP server?
xyz.cabalspy/wallet-tracker is a hosted endpoint at https://mcp.cabalspy.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.cabalspy.xyz
claude mcp add --transport http xyz-cabalspy-wallet-tracker 'https://mcp.cabalspy.xyz/mcp'
What is the xyz.cabalspy/wallet-tracker MCP server?
xyz.cabalspy/wallet-tracker is an MCP server listed in the public MCP registry as xyz.cabalspy/wallet-tracker. KOL and smart money tracking on 5 chains, plus CabalSpy ID (SocialFi): verified traders, theses. This page covers its hosted endpoint (https://mcp.cabalspy.xyz/mcp).
Is the xyz.cabalspy/wallet-tracker MCP server safe to use?
xyz.cabalspy/wallet-tracker scores 83 out of 100 on VerifyMCP. 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 xyz.cabalspy/wallet-tracker MCP server expose?
xyz.cabalspy/wallet-tracker exposes 38 tools: get_started, get_api_status, lookup_wallet, get_wallet_tracker, get_leaderboard, and 33 more. Their descriptions and schemas cost roughly 10,658 tokens of context every time the server is loaded.
Does the xyz.cabalspy/wallet-tracker MCP server require authentication?
No. We connected to xyz.cabalspy/wallet-tracker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the xyz.cabalspy/wallet-tracker MCP server still maintained?
xyz.cabalspy/wallet-tracker 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.