check_wallet_in_token

shallow

com.cabal-hunter.api/cabal-hunter · Verify this server

Is a SPECIFIC wallet involved in a SPECIFIC Solana token? Use this when a user names a wallet they are worried about, or when your agent keeps its own watchlist of addresses and wants to screen a token against one. Answers from two sources at once: 1. the traced holders of that token — rank, % of supply, buy slot, whether it funded a coordinated cluster, whether it created the token, or whether it is the liquidity pool / a labelled exchange wallet 2. a LIVE on-chain holding lookup, so a wallet too small to appear in the trace is still resolved rather than dismissed HOW TO READ THE RESULT — this matters more than the fields: found_in_scan=false is NOT a clean bill of health. The trace covers the largest holders, so a smaller position sits outside it, and a wallet that sold out and closed its token account leaves nothing to observe. Never tell a user a wallet is 'clean' or 'not involved' on this result. The `note` field states the limit of what was actually checked; relay it. holding.sold_out=true is the strong signal: a token account exists holding none of the token, i.e. this wallet HELD it and has since sold out. track_record, when present, counts earlier tokens the wallet was early in and how many graduated. It is an association measured out-of-sample, NOT a profit signal and not a recommendation to copy or avoid anyone. Absence of a track record means we hold no record, not that the wallet has no history. Free, no API key, rate limited per caller. For screening MANY wallets on every scan automatically, the Screen List add-on stores a private list per key: POST /api/screen-list/checkout.

100.0/100

1 trials · measured 27 days ago

check_wallet_in_token scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against com.cabal-hunter.api/cabal-hunter, measured 11 Sept 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
self-provisionable
Category
Developer infrastructure
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-09-11100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: check_wallet_in_token
[![Vouch score](https://vouch.tools/api/tools/d586e334-6cfd-4776-84f0-9da6ebc38eba/badge.svg)](https://vouch.tools/tools/d586e334-6cfd-4776-84f0-9da6ebc38eba)
check_wallet_in_token — Vouch