Cabal Hunter MCP server
{
"mcpServers": {
"cabal-hunter": {
"type": "http",
"url": "https://api.cabal-hunter.com/mcp"
}
}
}{
"mcpServers": {
"cabal-hunter": {
"type": "http",
"url": "https://api.cabal-hunter.com/mcp"
}
}
}{
"mcpServers": {
"cabal-hunter": {
"type": "http",
"url": "https://api.cabal-hunter.com/mcp"
}
}
}{
"servers": {
"cabal-hunter": {
"type": "http",
"url": "https://api.cabal-hunter.com/mcp"
}
}
}{
"mcpServers": {
"cabal-hunter": {
"type": "http",
"url": "https://api.cabal-hunter.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.2.0
What it does
Cabal Hunter exposes Solana token safety risks by detecting coordinated wallet activity, bundle buying, and coordinated dumps. It is for AI trading agents and developers building on Solana who need pre-trade safety checks to avoid exit liquidity setups.
- Check a Solana token for coordinated wallet cabals and same-block bundle buys before executing a trade.
- Analyze holder concentration and funding lineage to identify if insiders are positioned to dump on retail buyers.
- Review a creator's track record of previous token launches and coordinated exits across their deployment history.
Tools this server exposes
| Tool | Does |
|---|---|
| analyze_token | Returns Exit-Liquidity Risk verdict (LOW | ELEVATED | HIGH) for a Solana mint address, synthesizing holder funding lineage, same-block bundles, coordinated dump |
| holder_funding_lineage | Traces current top holders back to their funding sources and identifies shared funders with evidence transactions linked on Solscan. |
| detect_bundles | Identifies token accounts created in the same slot as purchase transactions, detecting coordinated Jito bundle buys. |
| coordinated_dump_detection | Finds holders who sold meaningful portions of their bags (≥25% each) in the same block, with sell transaction links. |
| dev_track_record | Returns the creator wallet's full history of token launches, past coordinated exits, and rug events. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.