# xyz.cabalspy/wallet-tracker

KOL, smart money & whale wallets API on Solana, BNB, Base, ETH: Wallet tracker, Leaderboard

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.0
- **Author:** xyz.cabalspy
- **License:** Unknown
- **Endpoints:** streamable-http https://mcp.cabalspy.xyz/mcp
- **Source:** https://mcp.cabalspy.xyz/mcp
- **Endpoint health:** reachable (last checked 2026-10-02T08:27:11.623Z, 6 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 31 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-04T21:02:53.888Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

21 declared. Observed from a live `tools/list` probe.
- `get_started` — How to use CabalSpy: 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 
- `get_api_status` — 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 i
- `lookup_wallet` — 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 he
- `get_wallet_tracker` — 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 d
- `get_leaderboard` — 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
- `list_wallets` — 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; th
- `get_wallet_history` — 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 ho
- `get_wallet_holdings` — 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 'load
- `get_pnl_calendar` — 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. blockcha
- `get_wallet_connections` — 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 
- `compare_wallets` — 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 fo
- `get_token_stats` — 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 individua
- `get_token_holders` — 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
- `get_token_transactions` — 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 
- `compare_tokens` — 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 o
- `detect_bundles` — 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. Retur
- `get_recent_trades` — 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". block
- `get_activity_metrics` — 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 
- `get_signals` — Tokens where several tracked wallets acted within the same window. 'cluster' means multiple wallets bought the same token, which is the strongest signal. 'entry
- `get_signal_history` — 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: k
- `get_analytics` — 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 th

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"wallet-tracker\": {\n      \"type\": \"http\",\n      \"url\": \"https://mcp.cabalspy.xyz/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/xyz.cabalspy%2Fwallet-tracker
- Install plan: https://forgeregistry.com/api/v1/packages/xyz.cabalspy%2Fwallet-tracker/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/xyz.cabalspy%2Fwallet-tracker
- HTML page: https://forgeregistry.com/registry/xyz.cabalspy%2Fwallet-tracker
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.
