com.cabal-hunter.api/cabal-hunter
REMOTE · API.CABAL-HUNTER.COM · SCANNED SEP 20
Solana pre-trade safety for AI agents: cabal, bundle, dump, deployer & honeypot in one verdict.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1550 tokens (~775/item across 2 items; 2 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
How do I install the com.cabal-hunter.api/cabal-hunter MCP server?
com.cabal-hunter.api/cabal-hunter is a hosted endpoint at https://api.cabal-hunter.com/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 · api.cabal-hunter.com
claude mcp add --transport http com-cabal-hunter-api-cabal-hunter 'https://api.cabal-hunter.com/mcp'
{
"mcpServers": {
"com-cabal-hunter-api-cabal-hunter": {
"url": "https://api.cabal-hunter.com/mcp"
}
}
} {
"servers": {
"com-cabal-hunter-api-cabal-hunter": {
"type": "http",
"url": "https://api.cabal-hunter.com/mcp"
}
}
} [mcp_servers.com-cabal-hunter-api-cabal-hunter] url = "https://api.cabal-hunter.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-cabal-hunter-api-cabal-hunter": {
"type": "remote",
"url": "https://api.cabal-hunter.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-cabal-hunter-api-cabal-hunter --url 'https://api.cabal-hunter.com/mcp' --transport streamable-http
mcp_servers:
com-cabal-hunter-api-cabal-hunter:
url: "https://api.cabal-hunter.com/mcp" {
"McpServers": {
"com-cabal-hunter-api-cabal-hunter": {
"Transport": "http",
"Url": "https://api.cabal-hunter.com/mcp"
}
}
} assistant mcp add com-cabal-hunter-api-cabal-hunter -t streamable-http -u 'https://api.cabal-hunter.com/mcp'
{
"mcpServers": {
"com-cabal-hunter-api-cabal-hunter": {
"type": "http",
"url": "https://api.cabal-hunter.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 16 Sept 26 0
- Tool “check_cabal_risk” rewrote its description, which is the text the model reads security
- 15 Sept 26 0
- Tool “check_cabal_risk” rewrote its description, which is the text the model reads security
- 4 Sept 26 0
- Schema quality: 1097 → 771 ▲ functional
- New tool “check_wallet_in_token” functional
- 31 Aug 26 −1
- Tool “check_cabal_risk” rewrote its description, which is the text the model reads security
- Schema quality: 979 → 1097 ▼ functional
- 28 Aug 26 +1
- Tool “check_cabal_risk” rewrote its description, which is the text the model reads security
- Schema quality: 887 → 979 ▼ functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://api.cabal-hunter.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cabal-hunter.com | CN=WE1,O=Google Trust Services,C=US | 4 Aug 2026 | 2 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 12eae429408af9771332a1fc2c1059a2 |
| SANs: cabal-hunter.com, *.cabal-hunter.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.cabal-hunter.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cabal-hunter.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), usb=(), magnetometer=(), gyroscope=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.cabal-hunter.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.cabal-hunter.com/mcp | HTTPS enforced | 301 | https://api.cabal-hunter.com/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 →
check_cabal_risk ~1,105
Pre-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, webhook_url} with an X-API-Key (a free key is enough) and we push you an alert 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. 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 Jito-bundled multi-wallet launch. `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 history WITH the peak market cap each past token hit, so a dead-count can't hide a pump-and-dump. Covers ANY Solana venue: pump.fun, Raydium, Orca, Meteora, PumpSwap. A launch counts only where the transaction actually CREATED the mint, so re-minting supply of an existing…
| Name | Type | Req | Description |
|---|---|---|---|
| mintAddress | string | yes | The Solana mint address of the token to audit (base58, 32–44 chars) |
| pairCreatedAt | number | – | Optional: DexScreener pairCreatedAt timestamp in milliseconds. Speeds up analysis when provided. |
No output schema declared.
No examples provided.
check_wallet_in_token ~445
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mintAddress | string | yes | The Solana mint address of the token (base58, 32–44 chars) |
| wallet | string | yes | The wallet address to look for in that token (base58, 32–44 chars) |
No output schema declared.
No examples provided.
What is the com.cabal-hunter.api/cabal-hunter MCP server?
com.cabal-hunter.api/cabal-hunter is an MCP server listed in the public MCP registry as com.cabal-hunter.api/cabal-hunter. Solana pre-trade safety for AI agents: cabal, bundle, dump, deployer & honeypot in one verdict. This page covers its hosted endpoint (https://api.cabal-hunter.com/mcp).
Is the com.cabal-hunter.api/cabal-hunter MCP server safe to use?
com.cabal-hunter.api/cabal-hunter scores 78 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 com.cabal-hunter.api/cabal-hunter MCP server expose?
com.cabal-hunter.api/cabal-hunter exposes 2 tools: check_cabal_risk, check_wallet_in_token. Their descriptions and schemas cost roughly 1,550 tokens of context every time the server is loaded.
Does the com.cabal-hunter.api/cabal-hunter MCP server require authentication?
No. We connected to com.cabal-hunter.api/cabal-hunter without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.cabal-hunter.api/cabal-hunter MCP server still maintained?
com.cabal-hunter.api/cabal-hunter is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.