Rugcheck Bot is live.
Mint authority left on. Top wallets funded by the deployer. A dev with a trail of dead launches. The evidence is on chain, but almost nobody has time to read it before they buy.
Most rug pulls are not sophisticated. The signals are almost always public
→ mint or freeze authority still active
→ liquidity that isn't burned or locked
→ supply concentrated in wallets funded by the deployer
→ a deployer with a history of abandoned launches
It's that pulling it together takes 20+ minutes across explorers, holder maps and dev wallet histories, and most buyers decide in 20 seconds.
Two independent scores, weighted equally:
→ Contract safety: can the deployer rug it through code or liquidity?
→ Holder health: is the distribution organic, or engineered?
Why two? A perfectly clean contract can still have 60% of supply in a few linked wallets. A clean holder list can sit on a contract with mint authority on. Either one alone gives you a false sense of safety.
TRY Rugcheck Bot $RC/bot
→ https://t.co/UOtxPGR14D : 5 free checks a day, every verdict free to read
→ https://t.co/PxrY4Reth9 : /check <CA> in any group
→ Discord : slash command for your server
→ X : reply "@RugcheckBot check" under any post
→ Builders : API docs at https://t.co/rPmxKlGlLr
Read the contract. Or let the agent read it for you.
Most rugs start with one transaction from the dev wallet.
Pro is adding alerts that fire when the dev wallet moves, so you're not the last to know.
Paid plans open soon → https://t.co/wkqU2Eu28g
LP locked ≠ LP burned.
Locked liquidity has an unlock date. After that, it can be pulled.
Burned liquidity is gone for good.
Rugcheck Bot checks which one a token actually has. Read the fine print before you read the chart.
What's inside Rugcheck Bot?
→ Sandbox: fresh machine + real browser per check
→ Sim engine: test buy & sell from a fresh wallet
→ Holder graph: funding traced, clusters grouped
→ Deployer index: every past launch
→ Evidence log: every finding linked, all public
Building a trading bot, dashboard or alert channel?
Rugcheck Bot has an API. Bring verdicts straight into your own tools.
Webhooks and unlimited checks come with Max.
Docs → https://t.co/TvKXk9ckg3
"Download our game client." "Install the wallet tool."
Rugcheck Bot inspects downloads inside a disposable sandbox. It never runs them, and the sandbox never touches your wallet.
Check the link before it checks you.
Before you buy the token, check the wallet that made it.
Paste a deployer address into Rugcheck Bot and see every coin it has launched, and how each one ended.
New ticker. Same wallet. Same ending?
https://t.co/3LR8Qz36E4
Rugcheck Bot is migrating.
First, thank you. To every holder who backed $RC/bot, and every user who ran a check, reported a bug or shared a verdict.
Our focus are to keep building the tech, fixing bugs and making every check sharper. The agent, the sandbox, the verdicts and the evidence all stay.
Stay safe:
→ We will never DM you first or ask you to connect your wallet to a link not posted here
→ Only trust the CA and links from this account and https://t.co/UOtxPGQtf5
→ Not sure about a link? Run it through Rugcheck Bot.
More updates soon.
Not every token is SAFE or a RUG.
RISKY (40–59) means real red flags, but not a confirmed rug.
It's not a "don't buy." It's a "size your bet accordingly, and read why."
The five verdicts, explained → https://t.co/f3PyHqZTRo
Rugcheck Bot is live.
Mint authority left on. Top wallets funded by the deployer. A dev with a trail of dead launches. The evidence is on chain, but almost nobody has time to read it before they buy.
Most rug pulls are not sophisticated. The signals are almost always public
→ mint or freeze authority still active
→ liquidity that isn't burned or locked
→ supply concentrated in wallets funded by the deployer
→ a deployer with a history of abandoned launches
It's that pulling it together takes 20+ minutes across explorers, holder maps and dev wallet histories, and most buyers decide in 20 seconds.
Two independent scores, weighted equally:
→ Contract safety: can the deployer rug it through code or liquidity?
→ Holder health: is the distribution organic, or engineered?
Why two? A perfectly clean contract can still have 60% of supply in a few linked wallets. A clean holder list can sit on a contract with mint authority on. Either one alone gives you a false sense of safety.
TRY Rugcheck Bot $RC/bot
→ https://t.co/UOtxPGR14D : 5 free checks a day, every verdict free to read
→ https://t.co/PxrY4Reth9 : /check <CA> in any group
→ Discord : slash command for your server
→ X : reply "@RugcheckBot check" under any post
→ Builders : API docs at https://t.co/rPmxKlGlLr
Read the contract. Or let the agent read it for you.
Clean contract. Mint revoked. LP burned.
60% of supply in five wallets funded by the same address.
That's why every Rugcheck Bot verdict has two scores: contract safety and holder health, weighted equally. One without the other is half a check.
The most dangerous click in crypto is "Claim airdrop."
Paste a mint page or claim link into Rugcheck Bot. It opens the site in a disposable sandbox, decodes the wallet requests, and shows you what you'd actually be signing.
https://t.co/hKVxifkegV
Pro and Max are coming.
Pro ($19/mo): 100 checks a day, wallet clusters, dev wallet alerts, chat with the agent
Max ($79/mo): unlimited checks, API + webhooks, priority sandbox
Holding $RC/bot already gets you extra free checks.
Get notified → https://t.co/wkqU2Eu28g
Ten holders at 4% each looks healthy.
Ten holders funded by the same wallet is one holder at 40%.
Rugcheck Bot traces top holders to their funding source and clusters deployer funded wallets, launch slot buyers and first second snipers.
Check without leaving the chat:
→ Telegram: /check <CA> in any group
→ Discord: slash command for your server
→ X: reply "@RugcheckBot check" under any post
5 free checks a day. Every verdict free to read, with the agent's full log public. $RC/bot
https://t.co/hKVxifjGrn