Rugcheck should triage new tokens; Solscan or a direct RPC read should verify the field that decides the trade, especially when a risk flag and an explorer disagree.
Which Check Wins on Speed, Signals, Verification, and Freshness?
A token scam risk check wins on throughput and derived signals. Manual Solscan work lets you trace a particular claim to its source.
For speed, a risk check combines authority, liquidity, and holder signals across a stream of new launches. Manual Solscan checks take longer because each wallet cluster and liquidity position needs separate tracing.
For derived signals, insider grouping connects wallets that may share control despite appearing as separate holders. Holder concentration is therefore more than the largest wallet’s percentage. LP lock status summarizes whether liquidity provider ownership appears restricted. Solscan’s holder list and authority display come from its own index; wallet relationships and LP custody take manual tracing.
For verification, Mint authority permits more supply, while Freeze authority can freeze token accounts. Both are fields in the mint account readable through RPC getAccountInfo. Say a risk flag reports revoked Freeze authority, but Solscan lists an address. Request getAccountInfo for the mint address, decode the data with the correct token program, and read freeze_authority. None means revoked; a public key means the authority remains. That account value settles the dispute at the returned slot. For Token-2022, inspect extensions for separate controls too.
For freshness, authority changes and transfers can outrun both indexes. Compare observation slots where available. A direct RPC read gives mint state at its returned slot; it cannot settle insider grouping or prove an LP lock. Inspect the relevant wallets and lock accounts for those claims.
Use a risk check to screen many new tokens and prioritize investigation. Use Solscan when one token or one claim matters. When the tools disagree on a mint authority, the decoded RPC account is the tiebreaker.
What Should You Verify Next?
Traders should verify the automation route and the custody behind any LP lock claim.
Can Token Risk Checks Be Automated Through an API?
API automation requires a published, supported endpoint from the provider. Confirm that capability before building a scanner; direct RPC reads can automate mint authority checks independently.
How Do I Verify an LP Lock On-Chain?
An LP lock is verifiable by tracing the pool’s liquidity provider token or position to its owner. Read the locking contract’s release condition and withdrawal authority. A lock label alone cannot prove that it holds the trading pool’s liquidity position.
Match the locked position to the actual trading pool before trusting the flag. To go further with a token scam risk check covering LP lock status, authority control, and holder concentration, use rugcheck.