cabal-hunter
com.cabal-hunter.api/cabal-hunterVersion 1.2.0Solana pre-trade safety for AI agents: cabal, bundle, dump, deployer & honeypot in one verdict.
Status
Responds265 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:50 UTC
- Latency
- 265 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://api.cabal-hunter.com/mcpResponds265 msNo sign-in
Claude Code
claude mcp add --transport http cabal-hunter https://api.cabal-hunter.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: cabal-hunter
Remote MCP server URL: https://api.cabal-hunter.com/mcpCursor
{
"mcpServers": {
"cabal-hunter": {
"url": "https://api.cabal-hunter.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"cabal-hunter","type":"http","url":"https://api.cabal-hunter.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
2 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
check_cabal_riskPre-trade safety check for any Solana token mint: is a buyer about to be
someone's exit liquidity? Every wallet cluster carries its evidence_txs.
AFTER YOU BUY: POST /api/watch {mint} with an X-API-Key (any key; add
webhook_url on the Pro plan) and we alert you the moment a coordinated dump
or liquidity drain starts on that token — carrying the same on-chain
evidence. This scan is a BUY check; a watch is a HOLD check, and a holder
needs the second one continuously. GET/DELETE /api/watch manage your own.
Paid plans: the watch also follows the token's insiders (dev, first-seconds
buyers) for 7 days and pushes insider_* events when they sell or move
together, each with the transaction.
Layers, ordered by STRENGTH OF EVIDENCE (not marketing):
1. HOLDER CONCENTRATION — what share one wallet actually controls
(`top_holder_pct`). A single wallet that can crater the price is the
most basic rug vector, and it needs no coordination at all.
IMPORTANT: we count only REAL wallets. LP pools, locked/vesting supply
and other program-owned accounts are excluded and labelled, never scored
as a whale — and supply comes from getTokenSupply, not an estimate. Tools
that skip this report a locked-supply token as '65% one wallet'. Our
numbers reconcile with GMGN's circulating top-10.
2. SAME-BLOCK BUNDLES — holders whose token accounts were created in the
EXACT same block: a multi-wallet launch bought in one slot. A Jito bundle is
one way to do that, not the only one - we read the slot, not the bundle.
`time_sync: true`.
3. COORDINATED DUMP — ≥2 holders each selling ≥25% of their bag in the same
block: a cabal exiting in real time. `coordinated_exit: true`, sold_pct.
4. HONEYPOT / AUTHORITY TRAPS (Solana-native) — live freeze authority,
un-revoked mint authority, Token-2022 transfer-fee / transfer-hook /
permanent-delegate traps. Answers: CAN you actually sell this token?
5. DEV TRACK RECORD — the creator resolved on-chain plus their full launch
| Not declared | Not declared | Not declared | Not declared |
check_wallet_in_tokenIs 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. | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Jul 7, 2026
- Updated
- Jul 7, 2026
- Categories (suggested)
- Finance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared