coin-scout
Use coin-scout as a read-only Solana forensics lab for AI agents: trace fund flows, analyze wallets/tokens, identify linked actors, detect manipulation, and save/export investigations.
Trace stolen or laundered funds forward/backward up to 5 hops, with USD-at-time values and bridge/EVM continuation.
Resolve cross-chain movements through Wormhole, deBridge, Mayan, Circle CCTP, and trace EVM destinations.
Profile wallets and tokens: balances, holdings, activity, funders/counterparties, rug-risk checks, holder concentration, and PnL.
Identify addresses via exchange labels, program labels, case labels, and inferred deposit-address behavior.
Detect wash trading and discover likely co-controlled wallet clusters with evidence signatures.
Investigate individual transactions with parsed details, balance deltas, mint screening, and fee-payer profiling.
Access Solana/DAS data via dedicated tools or a restricted read-only raw RPC escape hatch.
Save findings to local case files, label addresses with confidence/evidence, search prior cases, and export Markdown reports with SVG/ Mermaid fund-flow diagrams.
Check chain status and server transport/cache/rate-limit metrics.
Stay safe: no signing, no transactions, no airdrops; only read methods are forwarded.
Provides read-only access to Solana on-chain data via Helius, enabling wallet and token analysis, fund-flow tracing, bridge tracking, wallet clustering, PnL calculation, transaction investigation, and raw Solana RPC/DAS queries.
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., "@coin-scout screen this Solana wallet for risk: 7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsU"
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.
What it can do
Follow the money.
trace_fundswalks transfers forward or backward up to 5 hops, values every edge in USD at the moment it moved, and stops at Wormhole, deBridge, Mayan and Circle CCTP crossings to tell you which chain and address the funds landed on. WithfollowEvmit keeps going on the EVM side.Know who is on the other end. 16,050 OKX wallets ship built in, each one proven by OKX's own signed proof-of-reserves message. Traces stop at exchange wallets and mark the address before them as a likely deposit address, so you know which exchange to ask.
Catch fake volume.
detect_wash_tradingreads trades straight from a token's pools and flags wallets trading with themselves, same-slot round trips and bot farms funded from one wallet.Find the operator.
find_clustermines fee payers, co-signers, rent destinations, shared funders and same-slot activity to surface wallets one actor controls, with the signatures behind every link.Screen before you buy.
analyze_tokenchecks mint and freeze authority, metadata mutability and holder concentration, and tells pools and other program-controlled holders apart from real whales.See who profited.
wallet_pnlprices every swap at the time it happened and flags sales of tokens the wallet never bought.Build a case. Save traces and clusters to case files, label addresses with confidence and evidence, and export a Markdown report with SVG fund-flow diagrams.
Can't touch your money. No keys, no signing. The raw RPC tool forwards only read methods, so
sendTransaction,requestAirdropand friends never reach the network. The only thing it writes is your local case files.
Try asking:
"Profile wallet
<address>: who funded it, where did its money go, anything suspicious?""Is
<mint>a rug risk? Who actually holds the supply?""Trace funds out of
<address>for 3 hops, save it to caseexchange-hack, then export the report.""Are these four wallets the same person?"
"Did
<wallet>profit from<mint>, and who sent it tokens for free?""Is the volume on
<mint>real, or bots trading with themselves?"
Related MCP server: helius-forensics-mcp
Install
You need a Helius API key (the free tier works) and Node.js 22.19 or newer. coin-scout speaks the 2026-07-28 MCP revision over stdio and Streamable HTTP, still serves 2025-era clients, and is listed in the official MCP Registry as io.github.dennisyilmaz/coin-scout.
Claude Desktop and other MCPB clients
Open the downloaded coin-scout.mcpb with your client and paste your Helius API key when asked. The key is stored by the client, not in the bundle.
Claude Code
curl -LO https://github.com/dennisyilmaz/coin-scout/releases/latest/download/coin-scout.mjs
node coin-scout.mjsThe single file is the whole server. Run interactively, it asks for your Helius key, copies itself to ~/.coin-scout/ and registers itself with claude mcp add at user scope. Restart Claude Code and the tools are there.
Any MCP client, from source
git clone https://github.com/dennisyilmaz/coin-scout.git && cd coin-scout
npm ci && npm run build{
"mcpServers": {
"coin-scout": {
"command": "node",
"args": ["/absolute/path/to/coin-scout/build/index.js"],
"env": { "HELIUS_API_KEY": "your-key" }
}
}
}For Streamable HTTP instead of stdio, run node build/http.js. It binds 127.0.0.1:8787 only, rejects foreign Host headers, and serves GET /health with transport metrics.
Verify a download
Every release is built in GitHub Actions with signed build provenance, and ships a SHA256SUMS file and a CycloneDX SBOM (coin-scout.cdx.json).
gh attestation verify coin-scout.mjs --repo dennisyilmaz/coin-scoutHow it works
Helius bills and rate-limits per RPC call, not per HTTP request, so raw parallelism just buys you 429s. The transport layer is built around that:
JSON-RPC micro-batching. Calls issued within a 4 ms window are coalesced into one HTTP request. Measured on a 50-call
getTransactionfan-out: 8 HTTP requests instead of 50, 2.2x faster wall clock.Adaptive batch sizing. A batch that gets 429'd is halved and the un-answered calls are requeued rather than failed; the size grows back on sustained success. Empirically the API accepts batches of 20 but rejects 50.
Cost-aware adaptive rate limiting. Request spacing scales with the number of calls in a request, so a 20-call batch is spaced like 20 calls. Concurrency halves and spacing doubles on each 429, then decay back.
server_metricsreports the converged rate.HTTP/2 + keep-alive over an
undicipool, so there is no TLS handshake per call.Two-tier TTL cache with in-flight coalescing. Finalized transactions and blocks cache for hours; balances for seconds. Concurrent identical calls share one promise.
Narrow payloads. Tools return one compact JSON document rather than raw node responses. The biggest lever on agent latency is tokens, not milliseconds.
Tools
Analysis (composite, start here)
Tool | What it answers |
| Portfolio value, holdings, wallet age, in/out flow shape, top counterparties, earliest funders, risk flags |
| Rug screen: live mint/freeze authority, metadata mutability, supply, FDV, holder concentration (top1 / top10 / HHI) with pools and other program-controlled holders flagged, 0-100 risk score |
| BFS fund-flow graph, forward or backward, up to 5 hops: nodes, weighted edges valued in USD at the time of each transfer, terminal sinks with exchange and deposit-address labels, circular flows. Stops at bridges and reports where the funds went; |
| Funds that left or entered Solana via Wormhole, deBridge, Mayan or Circle CCTP: other chain, recipient, amounts, destination-chain tx. Takes signatures, or an address to scan |
| Fund flow on Ethereum, Base, Arbitrum, BNB Chain and 9 other EVM chains: native and ERC-20 transfers valued in USD at the time, stopping at contracts and labelled addresses |
| Who is behind an address: built-in exchange wallets, Helius identity when your plan includes it, case and program labels, and a deposit-address check. Every label carries its source and confidence |
| Wash-trading score for a token from its highest-volume pools: self-cancelling wallets, same-slot and quick round trips, volume concentration, traders funded by one wallet. Suspicious traders come with a sample signature |
| From one wallet, discovers likely co-controlled wallets: fee payers, co-signers, rent destinations, shared or sole funders, same-slot activity, creation time. Scored, with signature evidence |
| Realized and unrealized PnL per token from swaps, priced at swap time. Flags sales of tokens never bought and, for one mint, who sent the tokens for free |
| Every address a wallet transacted with, ranked, split by direction and per-mint volume |
| Sybil / co-ownership test across 2-10 wallets: direct links, shared funders, counterparty Jaccard overlap, 0-100 link strength |
| One signature: enhanced parse, per-account balance deltas with USD at the time, rug screen on every mint involved, fee-payer profile |
Case files
Tool | What it does |
| Create a case or add a summary, address labels (with confidence and evidence signatures) and dated notes |
| List cases, read one, or search every case for an address before starting on it |
| Write |
Pass case: "<name>" to trace_funds, find_cluster or follow_bridge to save the result into that case. Labels from any case show up in every tool's label field, so later investigations build on earlier ones. Cases live in ~/.coin-scout/cases/<name>/ as plain JSON.
Data access
Tool | Backed by |
|
|
| DAS |
|
|
| Helius Enhanced Transactions: human-readable type, source, transfers, swap events |
|
|
|
|
|
|
| Enhanced history filtered to |
| DAS |
| Full DAS surface (NFTs, cNFTs, fungibles, Token-2022) |
| Escape hatch for read-only RPC and DAS methods: |
| Batch compression, cache hit rate, adaptive rate-limit state |
Prompts
investigate_address, screen_token, trace_stolen_funds: each encodes an investigation order of operations.
Configuration
All optional except the API key. See .env.example.
Variable | Default | Purpose |
| — | Required |
| — | Optional. Lets |
|
|
|
|
| Override the RPC host |
| 24 | Ceiling on in-flight HTTP requests |
| 64 |
|
| 20 | Upper bound for JSON-RPC batching |
| 4 | Coalescing window |
| true | Disable to force HTTP/1.1 |
| 30000 | Per-request timeout |
| 6 | Retries for single (non-batched) requests |
| 20000 | LRU capacity |
| 400 | Hard cap on |
| 20 | Hard cap on pagination loops |
|
| Where case files are stored |
|
| Explicit |
| 8787 | HTTP entry point only |
Data and privacy
Everything runs on your machine. What leaves it:
Helius receives the addresses, signatures and mints you query, and your API key.
DefiLlama receives mint addresses and timestamps for
usdAtTimeprices.WormholeScan, deBridge, Mayan and Circle receive transaction signatures when a bridge crossing is resolved.
DexScreener receives the mint address when
detect_wash_tradinglooks up a token's pools.Blockscout, or Etherscan when
ETHERSCAN_API_KEYis set, receives EVM addresses when funds are traced on an EVM chain.
Only Helius and Etherscan get an API key, each only its own. Case files stay in your cases directory.
Accuracy notes
Analysis tools sample recent history. When a result carries
truncatedorsampleTruncated, its counts are lower bounds; raisetransferSamplefor more coverage.Current USD values come from Helius pricing and
usdAtTimevalues from DefiLlama historical prices; both cover actively traded tokens only. A missing price means unknown, not zero.wallet_pnlonly knows what the swaps in its sample show. Tokens that arrived by transfer or before the sample have no cost basis; their sales are reported asunmatchedProceedsUsdrather than realized PnL.find_clusterlooks one funder up from the seed. Run it again on a strong member to go further.Bridge resolution covers Wormhole, deBridge, Mayan and Circle CCTP. deBridge and CCTP can only be followed outbound; chains the server does not recognise are shown by raw chain id.
Built-in exchange labels come from OKX's proof-of-reserves snapshot of 1 November 2026, regenerated with
scripts/okx-labels.ts. Deposit-address and hot-wallet labels are inferred from sweep patterns and say so in theirconfidenceandsource.detect_wash_tradingreads token transfers in and out of pools, so liquidity adds and removals count as trades, and volume routed through other program accounts is reported separately asroutedVolume. Same-slot buy and sell is also what sandwich and arbitrage bots look like.analyze_tokenscans up to 1000 token accounts.holderAccountsExacttells you whether the holder count is the real total or a floor. Holders whose owner is a program or a program-derived address are flaggedisProgramOwned; concentration figures still include them, andprogramControlledPctsays how much of the supply they hold.Risk flags and scores are heuristics for triage. They point an investigation at the right transactions; they are not a verdict.
Contributing and security
See CONTRIBUTING.md for development setup and the checks CI runs. Report vulnerabilities privately as described in SECURITY.md.
License
Available Tools
29 toolsanalyze_tokenAnalyze token riskARead-onlyIdempotent
Rug-pull and manipulation screen for an SPL mint: live mint/freeze authority, metadata mutability, supply, FDV, holder count, top-holder concentration (top1/top10/HHI) with program-owned pools separated from real holders, plus a 0-100 risk score and explicit flags.
Inputs: mint (required), holders.
analyze_walletAnalyze walletARead-onlyIdempotent
One-call wallet profile: portfolio value, holdings, first/last activity, in/out flow shape, top counterparties, earliest funders and heuristic risk flags (fresh wallet, single funder, fan-in/fan-out, frozen assets). Start every wallet investigation here.
Inputs: address (required), holdings, counterparties, transferSample.
case_exportExport case reportAIdempotent
Write the case to disk as report.md (labels, notes, tables, Mermaid diagrams) plus one standalone SVG fund-flow diagram per saved trace or cluster, ready to drop into a report. Returns the file paths.
Inputs: case (required), artifactId.
case_readRead case filesARead-onlyIdempotent
With no arguments, list every case. With address, search all cases for prior labels, notes and saved traces mentioning it — do this before starting on any address. With case, return that case's labels, notes and an index of saved artifacts; add artifactId to get one saved trace, cluster or bridge result in full.
Inputs: case, address, artifactId.
case_updateUpdate case fileA
Create a case or add to it: summary, address labels with confidence and evidence signatures, and dated notes (findings, leads, retractions). Labels are shown by every other tool from then on, across sessions and cases.
Inputs: case (required), note, labels, summary, +3 more.
chain_statusChain statusARead-onlyIdempotent
Current Solana slot, epoch, block height and recommended priority fee. Cheap orientation call — use it to anchor timestamps and confirm the RPC is healthy.
Inputs: no named parameters.
compare_walletsCompare wallets for linkageARead-onlyIdempotent
Sybil / co-ownership check across 2-10 wallets: direct transfers between them, shared funders, counterparty-set Jaccard overlap and a 0-100 link strength per pair. Use to test whether separate addresses are the same actor.
Inputs: addresses (required), transferSample.
detect_wash_tradingDetect wash tradingARead-onlyIdempotent
Read a token's recent trades straight from its highest-volume AMM pools or bonding curve (found through DexScreener and the top holders, each checked on-chain) and score them for wash trading: wallets whose buys and sells cancel out, same-slot buy+sell, quick round trips of the same size, volume concentration, and traders funded by a common wallet. Returns a 0-100 score, flags, the suspicious traders with a sample signature each, and funder groups.
Inputs: mint (required), pools, maxPools, sinceUnix, +1 more.
find_clusterFind wallet clusterARead-onlyIdempotent
Start from one wallet and discover the other wallets likely controlled by the same actor: who pays its fees, who co-signs with it, where its token-account rent goes, which wallets share its funder, plus same-slot activity, creation time and timing similarity. Returns scored members with the signature evidence for each signal. Use compare_wallets instead when you already have the candidate list.
Inputs: address (required), case, txSample, maxCandidates.
find_counterpartiesFind counterpartiesARead-onlyIdempotent
Rank every address a wallet transacted with over a transfer sample, split by inbound/outbound count and per-mint volume, with first/last contact. Use to spot the funder, the sink, or the one address a wallet keeps cycling with.
Inputs: address (required), top, mint, direction, +2 more.
follow_bridgeFollow funds across a bridgeARead-onlyIdempotent
Resolve where funds went when they left Solana (or where they came from when they arrived) through Wormhole, deBridge, Mayan or Circle CCTP: other chain, recipient address, amounts and the transaction hash on the other chain. Pass signatures, or an address to scan its recent history for bridge transactions. trace_funds already resolves the crossings it meets.
Inputs: case, address, scanLimit, signatures.
get_accountGet accountBRead-onlyIdempotent
Raw + parsed on-chain account state for any address: lamports, owning program, executable flag and parsed data (mint config, token account, stake, etc). Use this to tell a wallet from a PDA, a mint or a program.
Inputs: addresses (required), encoding, commitment.
get_asset_activityGet asset activityARead-onlyIdempotent
Every transaction signature that touched a COMPRESSED NFT (Bubblegum tree asset), oldest to newest. Use to reconstruct a cNFT's mint-and-sale chain of custody. Fungible mints and standard NFTs are not indexed here — use get_transaction_history or get_transfers for those.
Inputs: assetId (required), page, limit.
get_assetsGet assets (DAS)BRead-onlyIdempotent
Digital Asset Standard lookup: one asset by mint, or every asset held by an owner. Covers NFTs, compressed NFTs, fungible tokens and Token-2022, with metadata, authorities, creators, royalties and price.
Inputs: mode (required), value (required), page, limit, +1 more.
get_balancesGet balancesARead-onlyIdempotent
SOL and SPL token balances for one or more wallets, with USD value where Helius prices the token. Use this before any transfer or portfolio question.
Inputs: addresses (required), limit, includeZero.
get_swapsGet swapsARead-onlyIdempotent
Normalized DEX swap history for a wallet: what was sold, what was bought, venue and fee per trade, plus a per-mint net-position summary. Use for trading behaviour, wash-trading and PnL groundwork.
Inputs: address (required), limit, source, includeTrades, +1 more.
get_token_holdersGet token holdersARead-onlyIdempotent
Paginated list of every token account for a mint with owner and balance. Use for holder-distribution work beyond the top-20 that analyze_token returns.
Inputs: mint (required), limit, cursor, minAmountRaw.
get_transaction_historyGet transaction historyARead-onlyIdempotent
Signature-level history for an address with slot/time/status filters and cursor pagination. Use when you need coverage of every transaction touching an address, not just transfers.
Inputs: address (required), full, limit, status, +4 more.
get_transaction_rawGet raw transactionARead-onlyIdempotent
Full raw jsonParsed transaction including logMessages, inner instructions, compute units and pre/post balances. Use only when the enhanced parse in get_transactions is not enough (custom programs, failure debugging).
Inputs: signature (required), commitment, includeLogs.
get_transactionsGet parsed transactionsARead-onlyIdempotent
Helius enhanced (human-readable) parse of up to 100 signatures: type, source protocol, description, native + token transfers, swap events and per-account balance deltas. This is the primary way to understand what a transaction actually did.
Inputs: signatures (required), commitment, includeInstructions.
get_transfersGet transfersARead-onlyIdempotent
Parsed SOL + SPL transfer feed for a wallet with server-side filters: counterparty, direction, mint, time and slot range. The fastest primitive for fund-movement questions — prefer it over walking signatures.
Inputs: address (required), mint, limit, solMode, +6 more.
identify_addressesIdentify addressesBRead-onlyIdempotent
Who is behind these Solana addresses: built-in exchange wallets (OKX proof-of-reserves addresses, ownership signature verified), Helius wallet identity when the API key has access, case labels, program labels, and a deposit-address check that flags addresses sweeping their funds to an exchange or a high fan-in hot wallet. Each label says its source and confidence.
Inputs: addresses (required), checkDeposits.
investigate_transactionInvestigate transactionARead-onlyIdempotent
Deep dive on one signature: enhanced parse, net SOL/token delta per account, every mint involved screened for rug risk, and a profile of the fee payer. Use when a single transaction is the starting point of an investigation.
Inputs: signature (required), screenMints, profileFeePayer.
search_assetsSearch assets (DAS)ARead-onlyIdempotent
Flexible DAS query across owner, creator, collection, compression state and token type. Use to enumerate a scammer's mints, a collection's supply, or every token a wallet ever created.
Inputs: page, burnt, limit, frozen, +7 more.
server_metricsServer metricsARead-onlyIdempotent
coin-scout transport stats: HTTP requests issued, JSON-RPC batch compression, retries, cache hit rate and adaptive rate-limit state. Use to explain slow responses or confirm caching is working.
Inputs: no named parameters.
solana_rpcRaw Solana RPC (read-only)ARead-onlyIdempotent
Escape hatch: call any read-only Solana JSON-RPC or Helius DAS method directly when no dedicated tool fits. Only get*, is*, search*, minimumLedgerSlot and simulateTransaction are forwarded; anything that could submit or sign (sendTransaction, requestAirdrop, sendBundle) is rejected.
Inputs: method (required), params.
trace_evmTrace funds on an EVM chainARead-onlyIdempotent
Follow funds forward from an address on an EVM chain, usually the destination of a bridge crossing that trace_funds or follow_bridge found. Reads native and ERC-20 transfers, values them in USD at the time, expands the largest recipients and stops at contracts and labelled addresses. Chains: Ethereum, BNB Chain, Polygon, Avalanche, Arbitrum, Optimism, Base, Fantom, Celo, Moonbeam, Scroll, Mantle, Linea. Ethereum works without a key through Blockscout; the rest need ETHERSCAN_API_KEY.
Inputs: chain (required), address (required), hops, sinceUnix, +1 more.
trace_fundsTrace fund flowARead-onlyIdempotent
Breadth-first fund-flow graph from a wallet, forwards (where money went) or backwards (where money came from), up to N hops. Returns nodes, weighted edges, terminal sinks and detected circular flows. The core tool for following stolen or laundered funds.
Inputs: address (required), case, hops, mint, +10 more.
wallet_pnlWallet profit and lossARead-onlyIdempotent
Realized and unrealized PnL per token from a wallet's DEX swaps, valued in USD at the time of each swap (average-cost basis). Answers "did this wallet profit from the rug" (pass mint), sniper/insider profit, and overall trading results. Sales of tokens never bought in the sample (airdropped, sent by a dev wallet, bought before the sample) are reported as unmatchedProceedsUsd and realizedPnlIfUnboughtFreeUsd instead of realized PnL — check those for insiders. With mint set, receivedWithoutSwap lists who sent the wallet that token for free.
Inputs: address (required), top, mint, swapLimit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 29 tools
Most tools have distinct forensic purposes, and the descriptions clearly separate wallet profiling, token screening, tracing, clustering, asset lookup, and case management. Residual overlap exists among transaction-level tools such as get_transactions, get_transaction_history, get_transfers, and investigate_transaction, and solana_rpc is a deliberate catch-all, but the boundaries are usually explained.
Names are consistently snake_case and mostly follow verb_noun patterns such as get_*, analyze_*, find_*, trace_*, and identify_*. However, several topic-first names such as wallet_pnl, chain_status, case_update, case_read, and case_export break the strict verb-first convention, though the set remains readable.
At 29 tools, the surface is heavy for an agent to select from reliably, even if each tool maps to a real forensic capability. The rubric treats 25+ tools as too many for practical scoping, and this set would benefit from consolidation or clearer grouping.
The surface covers an end-to-end investigation lifecycle: orientation, wallet/token analysis, transfers, transactions, swaps, cross-chain tracing, clustering, DAS asset lookup, and case update/read/export. Minor gaps exist around deeper non-EVM follow-up after bridges and case deletion, but core workflows have workarounds.
Maintenance
Related MCP Connectors
Solana wallet forensics SDK, x402 pay-per-call, AI agents.
Solana onchain intelligence for AI agents: wallet risk, due-diligence, perps funding, smart money.
Solana on-chain intelligence — token scans, wallet profiling, bundle detection, 19 MCP tools.
On-chain investigations: wallet analysis and fund tracing on Solana, EVM chains, Bitcoin and Tron.
Related MCP Servers
- FlicenseAqualityDmaintenanceOn-chain investigation and analysis tools for Solana blockchain, enabling detection of wash trading, funding source tracing, holder concentration analysis, and MEV/bundle activity identification.43-
- AlicenseNot gradedqualityDmaintenanceEnables Solana wallet forensics via MCP, including tracing funds, identifying entities, scoring risk, and comparing wallets using Helius APIs.MIT

Apogee MCPofficial
FlicenseNot gradedqualityBmaintenanceEnables agents to perform on-chain intel and operations on Robinhood Chain, including search, charting, wallet tracking, analytics, and preparing pons launches signed in Phantom.-- AlicenseNot gradedqualityBmaintenanceEnables AI agents to analyze Solana wallets for realized PnL, win rate, trading cadence, and smart-money, bot, or exchange-like flags, plus screen trending tokens for liquidity, volume, and rug risk. Exposes wallet quick checks, full profiles, free previews, and trending-token scans as MCP tools.MIT