ZendIQ — Claude Code MCP server: Solana token screening
Lets an agent screen a Solana token and get a swap verdict before signing. Useful when a bot trades on mainnet and has to filter risky mints.
claude mcp add --env ZENDIQ_AGENT_NETWORK=<ZENDIQ_AGENT_NETWORK> --env AGENT_STATE_DIR=<AGENT_STATE_DIR> --env ZENDIQ_AGENT_BUDGET_FILE=<ZENDIQ_AGENT_BUDGET_FILE> --env ZENDIQ_AGENT_KEYPAIR=<ZENDIQ_AGENT_KEYPAIR> --transport stdio zendiq -- npx -y @zendiq/mcpWhat ZendIQ does
The server exposes three tools: zendiq_screen_token for a free mint screen, zendiq_triage_swap for a $0.01 swap verdict, and zendiq_optimize_swap for a $0.02 unsigned swap build. Scoring runs on ZendIQ's hosted API at https://api.zendiq.ai — there is no local mode, every score comes over the network.
Node.js 22.5 or newer is required. Paid calls need a Solana keypair you control, funded with mainnet USDC; SOL is not needed because the x402 facilitator covers the payment's network fee. The key sits at runtime/payer-mainnet.key.json, and npm run budget:init writes a spend ledger capped at $1.00. On mainnet nothing is paid without that ceiling, so keep the wallet dedicated — the ledger only bounds what goes through this code.
Payments go over x402, and settlement delays can hold a response for up to 90 seconds. Set your agent's timeout to at least 120 seconds; plenty of MCP hosts cut a tool call off sooner. A 402 with settlement_pending means you can retry once with the same payment header.
What it helps with
- filter out a mint flagged as a serial deployer before signing
- read individual risk signals instead of just the headline score
- build an unsigned swap transaction for a given taker
- cap an agent's USDC spending with a local ledger
- run swap triage straight from an MCP host
Example prompts for the agent
- Screen the mint
JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCNand list the risk signals - Triage this swap and tell me whether it is safe to sign
- Build a 0.003 SOL swap for the taker address via
zendiq_optimize_swap
How to install ZendIQ
Platform CLI
claude mcp add --env ZENDIQ_AGENT_NETWORK=<ZENDIQ_AGENT_NETWORK> --env AGENT_STATE_DIR=<AGENT_STATE_DIR> --env ZENDIQ_AGENT_BUDGET_FILE=<ZENDIQ_AGENT_BUDGET_FILE> --env ZENDIQ_AGENT_KEYPAIR=<ZENDIQ_AGENT_KEYPAIR> --transport stdio zendiq -- npx -y @zendiq/mcpReplace <…> with your own values
Platform CLI
codex mcp add zendiq --env ZENDIQ_AGENT_NETWORK=<ZENDIQ_AGENT_NETWORK> --env AGENT_STATE_DIR=<AGENT_STATE_DIR> --env ZENDIQ_AGENT_BUDGET_FILE=<ZENDIQ_AGENT_BUDGET_FILE> --env ZENDIQ_AGENT_KEYPAIR=<ZENDIQ_AGENT_KEYPAIR> -- npx -y @zendiq/mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"zendiq": {
"command": "npx",
"args": [
"-y",
"@zendiq/mcp"
],
"env": {
"ZENDIQ_AGENT_NETWORK": "<ZENDIQ_AGENT_NETWORK>",
"AGENT_STATE_DIR": "<AGENT_STATE_DIR>",
"ZENDIQ_AGENT_BUDGET_FILE": "<ZENDIQ_AGENT_BUDGET_FILE>",
"ZENDIQ_AGENT_KEYPAIR": "<ZENDIQ_AGENT_KEYPAIR>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"zendiq": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@zendiq/mcp"
],
"env": {
"ZENDIQ_AGENT_NETWORK": "<ZENDIQ_AGENT_NETWORK>",
"AGENT_STATE_DIR": "<AGENT_STATE_DIR>",
"ZENDIQ_AGENT_BUDGET_FILE": "<ZENDIQ_AGENT_BUDGET_FILE>",
"ZENDIQ_AGENT_KEYPAIR": "<ZENDIQ_AGENT_KEYPAIR>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e ZENDIQ_AGENT_NETWORK=<ZENDIQ_AGENT_NETWORK> -e AGENT_STATE_DIR=<AGENT_STATE_DIR> -e ZENDIQ_AGENT_BUDGET_FILE=<ZENDIQ_AGENT_BUDGET_FILE> -e ZENDIQ_AGENT_KEYPAIR=<ZENDIQ_AGENT_KEYPAIR> zendiq npx -y @zendiq/mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about ZendIQ
How do I install ZendIQ in Claude Code?
Add the server with claude mcp add mcp -e ZENDIQ_AGENT_KEYPAIR=<ZENDIQ_AGENT_KEYPAIR> -- npx -y @zendiq/mcp. The longer form with network, state dir and budget file: `claude mcp add --env ZENDIQ_AGENT_NETWORK=<ZENDIQ_AGENT_NETWORK> --env AGENT_STATE_DIR=<AGENT_STATE_DIR> --env ZENDIQ_AGENT_BUDGET_FILE=<ZENDIQ_AGENT_BUDGET_FILE> --env ZENDIQ_AGENT_KEYPAIR=<ZENDIQ_AGENT_KEYPAIR> --transport stdio zendiq -- npx -y @zendiq/mcp`.
What does ZendIQ do?
It hands your agent a verdict on a Solana token or swap before anything gets signed: the mint screen is free, swap triage costs $0.01, and a swap build costs $0.02. Each response carries the individual signals, their values and their point contribution.
Do I need SOL for paid calls?
No — mainnet USDC in your keypair is enough. The x402 facilitator pays the network fee for the payment.
