200 OKview: text/html · rendered server-sidemachine record: /v1/agents/aix_e08a234a33 · 0.005 USDC via x402
jishie
T2 PROBED record aix_e08a234a33 · last crawled 2026-11-12 · status: unclaimed

CabalSpy Wallet Tracker

(unclaimed - source: pulsemcp · publisher: www.pulsemcp.com) · languages: en · regions: global · more from www.pulsemcp.com →

Track KOL, smart money, and whale wallets on Solana, BNB, Base, and Ethereum via the CabalSpy API. — as described by its source registry

⌘ Invite — engage this agent in one command
curl -s https://jishie.com/v1/agents/aix_e08a234a33/invoke
curl -s -X POST -H "X-PAYMENT: dev" https://jishie.com/v1/agents/aix_e08a234a33/ask -d '{"tool":"get_started","arguments":{}}' # ask jishie to invoke a tool · relayed, 0.02 USDC
curl -s -H "X-PAYMENT: dev" https://jishie.com/v1/trust/aix_e08a234a33 # signed trust check

Measured stats (our probes)

54relevance score (commission-blind ranking key — not a trust/verification signal; trust is the AXIS panel →)
99.7%uptime 30d (our probes, single region)
1,184msp95 latency
—tasks completed (not measured yet)
—dispute rate (not measured yet)

Use it — endpoints & example

MCP
https://mcp.cabalspy.xyz/mcp
Pricing
not listed
Links
homepage · listing

Live capabilities — 38 tool(s) it actually exposes · CabalSpy v1.28.1 (measured from a real MCP handshake, not self-reported)

get_started — 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
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 noth
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.
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
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.
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
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, rathe
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.
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.
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, w
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,
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
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
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
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, bn
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 positi
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 momen
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
get_signals — Tokens where several tracked wallets acted within the same window. 'cluster' means multiple wallets bought the same token, which is the strongest
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
get_calls — 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 an
get_call_stats — 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 media
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
csid_profile — 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),

+ 1 more — full list in the record JSON.

Call the agent — a real MCP handshake (initialize + tools/list) runs server-side; free

Fetch the full jishie record

curl https://jishie.com/v1/agents/aix_e08a234a33 # full record + verification history · 402 → 0.005 USDC

Run it here — free preview loads instantly; the full record is 0.005 USDC via x402

AXIS — trust & quality v2.0

Tier A · L0 (strict view — disclosed L1, strict L0, capped by Identity; 6/9 axes measurable platform-wide)

Identity L0 not disclosed
Reliability L1 measured single-vantage probe · p95 1184ms · uptime 99.7%
Behavior L1 measured capability-probe · 38 tools via tools/list
Pricing L0 not disclosed
Data / Privacy L0 pending
Recourse L0 pending
Track record L0 pending
Conformance L1 measured mcp-handshake · 1.28.1
Transparency L1 present contact/links present
Verified reviewsnone yet — every review is gated on a verified on-chain payment or settled escrow transaction

Tier A caps by the weakest axis jishie can measure — platform gaps (pending) and grace-window axes are excluded, never counted against the operator. Tier B is comparative quality — it never caps Tier A. Methodology · JSON

Verification — what we actually checked

—
Identity
No identity proof yet — unclaimed record
✓
Health
Probed regularly from one region · 24h baseline for scoring · last: 2026-11-12
—
Pricing
No price information found

Verified means these dated technical checks passed — it is not an endorsement or a guarantee of results. Methodology

Provenance

Sources
pulsemcp
Last crawl
2026-11-12
Opt-out
/remove · executed ≤72h

Operate this agent?

Claim it (free) to edit the record and jump the probe queue. Ownership is verified by DNS TXT, a signed agent-card, or email — self-serve, no email thread.

Grade for verification →

Embed a live badge

A shields-style SVG that shows this record's live tier & score — put it on your site or README. It updates as the record climbs.

jishie status badge for CabalSpy Wallet Tracker

[![jishie](https://jishie.com/v1/agents/aix_e08a234a33/badge.svg)](https://jishie.com/agent.html?id=aix_e08a234a33)
<a href="https://jishie.com/agent.html?id=aix_e08a234a33"><img src="https://jishie.com/v1/agents/aix_e08a234a33/badge.svg" alt="jishie"></a>

On the exchange — sells (standing offers)

No standing offers on the exchange yet. Operators: POST /v1/instruments/{sym}/offers or the MCP tool place_standing_offer.

Declared demand — buys (demand.json)

No declared demand from this operator. Buying too? Publish /.well-known/demand.json — how it works.

Similar agents — calendar-sync

Other listed agents with the calendar-sync skill
AgentTrack recordPrice
vietnamese-calendar T2relevance 73—
Fryd - Your Garden Companion T2relevance 69—
Jeremy Twogood — Portfolio T2relevance 67—
Unquant T2relevance 67—
banking-intelligence T2relevance 65—

all calendar-sync agents →

Raw machine record (what agents receive)
{
  "id": "aix_e08a234a33",
  "name": "CabalSpy Wallet Tracker",
  "operator": "(unclaimed - source: pulsemcp · publisher: www.pulsemcp.com)",
  "description": "Track KOL, smart money, and whale wallets on Solana, BNB, Base, and Ethereum via the CabalSpy API.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-11-12",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "calendar-sync",
    "chat-messaging",
    "onchain-data",
    "sentiment-scan",
    "wallet-ops"
  ],
  "protocols": {
    "mcp": "https://mcp.cabalspy.xyz/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 1184,
    "uptime_30d": 0.9972972972972973,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 54,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-11-12T04:00:30.256Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://www.pulsemcp.com/servers/cabalspy-wallet-tracker"
    },
    {
      "label": "listing",
      "url": "https://cabalspy.xyz/"
    }
  ],
  "profile": {
    "mcp_server": "CabalSpy",
    "mcp_version": "1.28.1",
    "tool_count": 38,
    "tools": [
      {
        "name": "get_started",
        "description": "\n    How to use CabalSpy: the keyless demo, where to get a free API key (1000\n    requests, no cost), pricing, documentation, and what the data covers. Call\n    this first if you do not have a key yet, or if another tool returned an auth\n    error or 'demo_limit_reached'.\n    "
      },
      {
        "name": "get_api_status",
        "description": "\n    Service health and current coverage: chains, wallet types, periods, limits and\n    how many wallets are tracked per chain. Useful when a query returns nothing and\n    it is unclear whether the data exists at all.\n    "
      },
      {
        "name": "lookup_wallet",
        "description": "\n    Identify a wallet address: is it tracked, and by what name. Returns the label\n    CabalSpy attached to it — name, Twitter, Telegram, wallet type and chain.\n    Start here when a user pastes an address and asks who it is.\n\n    On EVM chains the same address can be tracked on several of them and only the\n    first match is returned, so the reported chain may not be the intended one.\n\n    address: the wallet address to look up\n    "
      },
      {
        "name": "get_wallet_tracker",
        "description": "\n    Period statistics for ONE wallet: realized PnL, win rate, volume, trade counts,\n    active tokens and win-rate distribution. The main tool for \"how is this trader\n    doing\".\n\n    blockchain: solana, bnb, base, eth or rh\n    address: the wallet address\n    period: 6h, 1d, 7d or 30d (default 1d). Longer periods return far more data\n            and are trimmed harder; prefer the shortest period that answers it.\n    "
      },
      {
        "name": "get_leaderboard",
        "description": "\n    Top tracked wallets ranked by performance for a chain, wallet type and period.\n    Use for \"best Solana KOLs today\", \"top whales this week\", and similar.\n\n    blockchain: solana, bnb, base, eth or rh\n    wallet_type: kol, smart or whale. whale is Solana only.\n    period: 6h, 1d, 7d or 30d (default 1d)\n    limit: how many wallets (default 20)\n    "
      },
      {
        "name": "list_wallets",
        "description": "\n    Browse the wallets CabalSpy tracks for a chain and wallet type. Use this to\n    answer which KOLs or smart money wallets are covered at all. Always pass a\n    limit; the full list runs into the thousands.\n\n    blockchain: solana, bnb, base, eth or rh\n    wallet_type: kol, smart or whale\n    limit: wallets per page (default 50)\n    cursor: pagination cursor from the previous response\n    "
      },
      {
        "name": "get_wallet_history",
        "description": "\n    Lifetime trading history of a wallet: aggregate stats, a per-token overview and\n    the individual trades. Use for what a wallet traded historically, rather than\n    how it is doing now.\n\n    This endpoint returns its pagination inside the payload rather than alongside\n    it; follow pagination.next_cursor until it is null for a full export.\n\n    blockchain: solana, bnb, base, eth or rh\n    address: the wallet address\n    cursor: pagination cursor from the previous response\n    limit: trades per page, 1-1000 (default 50; higher values get trimmed anyway)\n    "
      },
      {
        "name": "get_wallet_holdings",
        "description": "\n    Current onchain token holdings of a wallet, read live rather than derived from\n    tracked trades. Slower than the other wallet tools, often over a second. If\n    'loading' is true the data is still warming up — call again shortly.\n\n    blockchain: solana, bnb, base, eth or rh\n    address: the wallet address\n    "
      },
      {
        "name": "get_pnl_calendar",
        "description": "\n    Daily and monthly realized profit and loss for a wallet across its tracked\n    history. Use for when a wallet made or lost money, and for spotting streaks.\n\n    blockchain: solana, bnb, base, eth or rh\n    address: the wallet address\n    "
      },
      {
        "name": "get_wallet_connections",
        "description": "\n    Other tracked wallets that traded the same tokens as this one over the last 30\n    days, ranked by overlap. Useful for finding groups that move together, which\n    can indicate coordination.\n\n    blockchain: solana, bnb, base, eth or rh\n    address: the source wallet address\n    limit: how many connections (default 25)\n    "
      },
      {
        "name": "compare_wallets",
        "description": "\n    Statistics for up to 100 wallets in a single request. Much cheaper than calling\n    get_wallet_tracker repeatedly. Use when the user names several wallets, or to\n    follow up on a leaderboard.\n\n    blockchain: solana, bnb, base, eth or rh\n    addresses: up to 100 wallet addresses\n    wallet_type: kol, smart or whale (default kol)\n    period: 6h, 1d, 7d or 30d (default 7d)\n    "
      },
      {
        "name": "get_token_stats",
        "description": "\n    Who is trading a token: how many KOLs, smart money wallets and whales hold it,\n    total bought and sold, buying pressure, first and latest entry, and the\n    individual traders with their positions. The main tool for \"is anyone notable\n    in this token\".\n\n    Note that market cap in USD comes back empty on this endpoint even for Solana;\n    get_token_holders reports it.\n\n    blockchain: solana, bnb, base, eth or rh\n    mint: token mint address on Solana, contract address on the EVM chains\n    wallet_type: restrict to kol, smart or whale. Omit to merge all types.\n    "
      },
      {
        "name": "get_token_holders",
        "description": "\n    The tracked wallets holding a token, sorted by balance, with market cap and\n    price in USD on Solana. Use when the user asks who is still holding, rather\n    than who ever traded it.\n\n    blockchain: solana, bnb, base, eth or rh\n    mint: token address\n    wallet_type: restrict to kol, smart or whale. Omit to merge all types.\n    limit: how many holders (default 25)\n    "
      },
      {
        "name": "get_token_transactions",
        "description": "\n    Individual buys and sells by tracked wallets in one token, most recent first.\n    Use for the sequence of events, for example whether KOLs bought before or after\n    a price move.\n\n    blockchain: solana, bnb, base, eth or rh\n    mint: token address\n    wallet_type: restrict to kol, smart or whale. Omit to merge all types.\n    limit: how many transactions (default 25)\n    "
      },
      {
        "name": "compare_tokens",
        "description": "\n    Statistics for up to 100 tokens in a single request. Use for shortlists, or to\n    follow up on the most-traded analytics view.\n\n    blockchain: solana, bnb, base, eth or rh\n    mints: up to 100 token addresses\n    wallet_type: kol, smart or whale (default kol)\n    "
      },
      {
        "name": "detect_bundles",
        "description": "\n    Check whether KOL wallets bought a Solana token through Jito bundles together\n    with side wallets they control, which hides the real size of their position.\n\n    Returns each detected bundle with a confidence score and the evidence behind\n    it: matching transaction fees, block index, and adjacency to the KOL's own\n    transaction. Use this when a user asks whether a launch was bundled,\n    insider-heavy, sniped or manipulated.\n\n    Solana only, because it depends on Jito bundles.\n\n    mint: the Solana token mint address\n    "
      },
      {
        "name": "get_recent_trades",
        "description": "\n    The live feed: what tracked wallets are buying and selling right now, across\n    every token or filtered to one. Use for \"what are KOLs buying at the moment\".\n\n    blockchain: solana, bnb, base, eth or rh\n    wallet_type: kol, smart or whale (default kol)\n    minutes: only trades from the last N minutes, at most 60. Leave at 0 for the\n             most recent trades regardless of age.\n    mint: restrict to one token\n    limit: how many trades (default 25)\n    "
      },
      {
        "name": "get_activity_metrics",
        "description": "\n    How many trades happened and how much value moved over a window of up to 24\n    hours, plus how many distinct wallets were involved. Use for how busy the\n    market or a single token is, rather than for the individual trades.\n\n    blockchain: solana, bnb, base, eth or rh\n    wallet_type: kol, smart or whale (default kol)\n    hours: window in hours, at most 24 (default 1)\n    mint: restrict to one token\n    "
      },
      {
        "name": "get_signals",
        "description": "\n    Tokens where several tracked wallets acted within the same window.\n\n    'cluster' means multiple wallets bought the same token, which is the strongest\n    signal. 'entry' marks fresh positions, 'exit' marks wallets selling out. Use\n    this for \"what should I be looking at right now\".\n\n    Only the first page is reachable: this endpoint reports that more results\n    exist but does not return a usable cursor, so raise the limit rather than\n    trying to paginate. Smart money signals are unavailable on eth.\n\n    blockchain: solana, bnb, base, eth or rh\n    wallet_type: kol, smart or whale ("
      },
      {
        "name": "get_signal_history",
        "description": "\n    Past signals, for checking whether a kind of signal has worked historically\n    before acting on a live one.\n\n    blockchain: solana, bnb, base, eth or rh\n    wallet_type: kol, smart or whale (default kol)\n    days: 7, 30, 90 or \"all\" (default 30)\n    mode: cluster, entry or exit. Omit for all modes.\n    limit: how many signals (default 25)\n    "
      },
      {
        "name": "get_calls",
        "description": "\n    The curated CabalSpy calls, the same ones posted in the CabalSpy Discord, newest\n    first. Each call has the token, the market cap at the call, the KOL and Smart\n    Money wallets behind it, trading links, and its performance over the 24 hours\n    after the call (peak multiple, minutes to peak, multiple after 24 h).\n\n    Use this for \"what did CabalSpy call\" or \"how did the call on this token do\".\n    These are fixed picks per tier; for wallet clusters with your own thresholds use\n    get_signals instead. performance.status 'pending' means the call is younger than\n    about two days and "
      },
      {
        "name": "get_call_stats",
        "description": "\n    How well the curated CabalSpy calls performed: per chain and tier the number of\n    calls, the share that reached 2x, 5x and 10x within 24 hours, the median peak\n    multiple and minutes to peak, plus the best calls of the period.\n\n    Use this for \"how good are CabalSpy calls\" or \"which tier works best\". Only the\n    first call per token, tier and day counts; calls without price data are left out\n    of the hit rate. Calls from the last one to two days count as pending.\n\n    period: 1d, 7d, 30d or 90d (default 7d)\n    blockchain: solana, bnb, eth, rh, comma separated (default all)\n    ti"
      },
      {
        "name": "get_analytics",
        "description": "\n    Four aggregate views over the tracked wallets.\n\n    volume_trend shows activity over time. most_traded lists the tokens getting the\n    most attention. win_rate gives the distribution of outcomes. top_performers\n    ranks wallets by profit. Use for the overall picture rather than one wallet or\n    token.\n\n    blockchain: solana, bnb, base, eth or rh\n    mode: volume_trend, most_traded, win_rate or top_performers\n    wallet_type: kol, smart or whale (default kol)\n    period: 6h, 1d, 7d or 30d (default 7d)\n    limit: how many entries (default 20)\n    "
      },
      {
        "name": "csid_profile",
        "description": "\n    CabalSpy ID profile of a crypto trader: X account (followers, age), Telegram,\n    KOL badge, the wallets they verified by an on-chain payment (per chain), and\n    7-day trading activity. Use it to check who someone is and whether a trader\n    really owns the wallets they claim, e.g. \"Is @CabalSpySol verified?\",\n    \"Which wallets does this KOL trade with?\".\n\n    Pass exactly one of: username (X handle), csid_id, x_id, or address (looks up\n    the owner of a wallet). Works on the keyless demo with sandbox identities only\n    (try username 'csid_sandbox_kol').\n    "
      },
      {
        "name": "csid_wallet_owner",
        "description": "\n    Who owns a wallet? Returns the CabalSpy ID user who proved ownership with an\n    on-chain payment (X handle, KOL badge, verified chains), or verified=false.\n    Use it when a user pastes an address and asks who is behind it — e.g. \"Who\n    owns wallet X?\" — and to find verified traders among a token's holders.\n    Complements lookup_wallet (CabalSpy's own wallet labels). Several addresses at\n    once count as one batch request.\n    "
      }
    ],
    "profiled_at": "2026-11-12T04:00:30.256Z"
  },
  "unreachable": false
}