c-viper-work/cabal-radar-mcp

Solana & Base token risk intelligence for MCP assistants and the terminal. Zero external runtime dependencies. Open-source Node.js ESM. Built by c-viper-work.
Inspect Solana mint/freeze authorities, Token-2022 controls, holder-account concentration, early acquisition coordination, Jito tips and mother-wallet funding clusters. Inspect Base ERC20 metadata, dangerous bytecode patterns, earliest observed Transfer concentration and transfer restrictions. Activate local Pro with an on-chain payment receipt; no central license server, private keys or wallet connection.
Landing page · Source · Trust model
> This is heuristic investigation software, not a completed security audit. A high safety score does not establish safety. Tax and honeypot results remain UNKNOWN when the available evidence cannot establish them. Launch coverage is never implied by a bounded historical sample.
## Zero-clone MCP setup
sh
npx -y github:c-viper-work/cabal-radar-mcp mcp
For MCP clients, use command: "npx" with args: ["-y", "github:c-viper-work/cabal-radar-mcp", "mcp"]. The globally installed configuration below remains supported.
## Installation
Requires Node.js 22+. No dependency install is needed to run a source checkout:
sh
git clone https://github.com/c-viper-work/cabal-radar-mcp.git
cd cabal-radar-mcp
node bin/cabal-radar.js --help
npm test
npm install -g .
Or install from the public GitHub repository when available:
sh
npm install -g github:c-viper-work/cabal-radar-mcp
After the maintainer publishes version 1.0.0 to npm, npm install -g cabal-radar-mcp@1.0.0 and npx -y cabal-radar-mcp@1.0.0 mcp are equivalent distribution options. This source tree does not imply that npm publication, registry listing or a hosted deployment has occurred.
Both cabal-radar and cabal-radar-mcp are executable aliases. No arguments starts MCP stdio. npm start also starts MCP; clients should use the binary directly to avoid npm's stdout banners.
## CLI
sh
cabal-radar scan DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263 --chain solana --json
cabal-radar scan 0x532f27101965dd16442E59d40670FaF5eBB142E4 --chain base --json
cabal-radar upgrade
cabal-radar activate --tx --chain
cabal-radar status
cabal-radar scan --chain solana --pro --json
cabal-radar mcp
Replace angle-bracket placeholders before running. Single-token scans infer Base for a valid 0x address, otherwise Solana. Explicit --chain values take precedence. --pro returns both basic and deep results after activation; without a valid license it prints upgrade information and exits with status 1. Input/RPC failures also exit 1; successful commands exit 0. CLI activation only reads chain state and writes a local license. No command submits transactions or approves tokens.
## MCP setup: Claude Desktop, Cursor and Windsurf
Install the binary globally first, ensure the client can find it on PATH, then merge this entry into the client's MCP server configuration:
json
"mcpServers": {
"cabal-radar": {
"command": "cabal-radar-mcp",
"args": ["mcp"],
"env": {
"SOLANARPCURL": "https://api.mainnet-beta.solana.com",
"BASERPCURL": "https://mainnet.base.org"
In Claude Desktop, open its developer/MCP configuration. In Cursor or Windsurf, use MCP server settings and add a stdio command, or merge the object above into the JSON editor if provided. Exact settings labels vary by client version. Restart/reconnect the server and confirm six tools appear. Keep RPC credentials in client environment configuration; do not commit them.