Provides on-chain forensics tools for the Solana blockchain, including funding source tracing, wash trading detection, holder distribution analysis, MEV/bundle detection, and token creation investigation.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@solana-forensics trace the funding sources for wallet 9xQeWvG816bUx9EPjHmaT23yvVM2ZWbrrpZb9PusVFin"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
On-chain investigation and analysis tools for Solana blockchain. Detects wash trading, traces funding sources, analyzes holder concentration, and identifies MEV/bundle activity.
Sign up at dashboard.helius.dev and create an API key.
cd solana-forensics-mcp
uv venv && source .venv/bin/activate
uv pip install -e .Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"solana-forensics": {
"command": "uv",
"args": ["--directory", "/path/to/solana-forensics-mcp", "run", "python", "-m", "src.server"],
"env": {
"HELIUS_API_KEY": "your_api_key_here"
}
}
}
}Restart Claude Desktop. The server will appear as solana-forensics with 4 tools.
Add to ~/.claude/settings.json:
{
"mcpServers": {
"solana-forensics": {
"command": "uv",
"args": ["--directory", "/path/to/solana-forensics-mcp", "run", "python", "-m", "src.server"],
"env": {
"HELIUS_API_KEY": "your_api_key_here"
}
}
}
}Or add to your project's .mcp.json for project-specific access:
{
"mcpServers": {
"solana-forensics": {
"command": "uv",
"args": ["--directory", "/path/to/solana-forensics-mcp", "run", "python", "-m", "src.server"],
"env": {
"HELIUS_API_KEY": "your_api_key_here"
}
}
}
}Restart Claude Code. Tools will be available as mcp__solana-forensics__*.
Related MCP server: Solana DeFi Analytics MCP Server
Operation | Description |
| BFS traversal of SOL transfer history to trace funding sources |
| Identify shared funding sources across multiple wallets |
| DFS cycle detection in token trade graphs |
| Gini coefficient, top-10 concentration, tier breakdown |
| Find transaction clusters in same slot (MEV/bundle detection) |
| Trace back to token mint creation transaction |
Category | Operations |
wallets |
|
trading |
|
tokens |
|
transactions |
|
balances |
|
accounts |
|
assets |
|
fees |
|
webhooks |
|
programs |
|
The server exposes 4 meta-tools:
solana_forensics_discover() # Browse all operations
solana_forensics_get_schema(op) # Get parameter details
solana_forensics_execute(op, {}) # Execute operation
solana_forensics_continue() # Continue paginated resultssolana_forensics_execute("forensics.trace_sol_funding", {
"address": "TARGET_WALLET",
"max_hops": 3
})solana_forensics_execute("forensics.detect_wash_trading", {
"mint": "TOKEN_MINT_ADDRESS",
"limit": 100
})solana_forensics_execute("forensics.find_common_funding", {
"addresses": ["WALLET_1", "WALLET_2", "WALLET_3"],
"max_hops": 2
})solana_forensics_execute("forensics.analyze_holder_distribution", {
"mint": "TOKEN_MINT_ADDRESS"
})Python 3.10+
uv package manager
Helius API key (free tier works)
Powered by Helius API for Solana blockchain data access.
Continue retrieving paginated results from a previous operation.
Args: session_id: Session ID from the paginated response. If not provided, uses the last paginated operation.
Inputs: session_id. Returns: result
Browse all available Solana forensics operations organized by category.
Returns a tree of operations with descriptions. Use this to explore what operations are available before executing them.
Inputs: no named parameters. Returns: result
Execute a Solana forensics operation with the specified parameters.
Use solana_forensics_get_schema first to understand required parameters.
Args: operation: Operation identifier (e.g., 'forensics.trace_sol_funding') params: Operation parameters as defined in the schema
Returns the operation result. Large results are automatically paginated - use solana_forensics_continue to get next pages.
Inputs: operation (required), params. Returns: result
Get detailed parameter schema for a specific operation.
Args: operation: Operation identifier in format 'category.action' (e.g., 'forensics.trace_sol_funding', 'forensics.detect_wash_trading')
Returns parameter requirements, types, and descriptions.
Inputs: operation (required). Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 4 tools
Each tool has a distinct, non-overlapping purpose: discover lists operations, get_schema returns parameter details, execute runs an operation, and continue handles pagination. There is no ambiguity about which tool to use for a given step.
All tools follow a consistent 'solana_forensics_<verb>' pattern (discover, get_schema, execute, continue). The naming convention is uniform and predictable, making the API easy to navigate.
Four tools is well-scoped for a meta-interface. Each tool is necessary for the operation lifecycle (explore, inspect, execute, paginate), and there is no bloat or redundancy.
The tool set covers the full workflow: discovering available operations, fetching schemas, executing them, and continuing through paginated results. No obvious gaps exist for the stated purpose of a forensics operation interface.
On-chain investigations: wallet analysis and fund tracing on Solana, EVM chains, Bitcoin and Tron.
Solana on-chain intelligence — token scans, wallet profiling, bundle detection, 19 MCP tools.
Full Solana DeFi coverage: launchpads, tokens, trades, and wallets, decoded at scale.
Blockchain intelligence for tracing funds, screening addresses, and investigating on-chain activity.
