chainanalyzer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X402_NETWORK | No | Payment network: base or solana | base |
| X402_PRIVATE_KEY | No | Wallet private key for USDC payments | |
| CHAINANALYZER_API_KEY | No | tfk_ API key (subscription auth) | |
| CHAINANALYZER_BASE_URL | No | API base URL | https://chain-analyzer.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_address_riskA | Get AML risk score for any blockchain address. Returns risk level, score (0-100), detections, and ML anomaly score. Supports BTC, ETH, POL, AVAX, SOL. |
| sanctions_checkB | Screen address against OFAC, FATF, JFSA, and ChainAnalyzer ScamDB sanctions lists. |
| trace_transactionB | Trace fund flows for a transaction with ML anomaly detection. Returns graph of addresses and transfers. |
| detect_coinjoinB | Detect CoinJoin, mixing, and tumbling patterns in a Bitcoin transaction. |
| cluster_walletA | Identify related addresses through Neo4j graph clustering. Returns cluster size and related addresses. |
| batch_screeningA | Batch AML screening for multiple addresses at once (up to 50). Returns risk level and score per address. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct blockchain analysis function: screening (batch vs single address), clustering, mixing detection, sanctions checking, and transaction tracing. No overlap in purpose.
Tools use a consistent verb_noun pattern (e.g., batch_screening, check_address_risk, detect_coinjoin) with one exception: 'cluster_wallet' uses verb_noun but 'wallet' is a bit broader. Overall, naming is clear and predictable.
With 6 tools, the server covers core AML and blockchain analysis functions succinctly without being too sparse or overly numerous.
The tool set covers screening (batch & single), risk scoring, clustering, mixing detection, sanctions, and tracing. A minor gap is the lack of a tool for getting raw transaction data or address history, but the main analysis workflows are complete.