Meet Cookd
Tag @cookdbot with a Solana mint or paste it on the website and get a clear breakdown of holders, rug risks, and project claims.
Completely free. No subscription, no “Pro” plan, and no features locked behind a paywall.
Less hype. Show receipts.
cookdbot.fun
Once turbo mode is live Pump callouts and fomo theses will be taken into consideration when scanning the tokens
Scanned callouts and theses will be made available on the token scan page
We are able to keep Cookd usable free of charge by using creator rewards for:
• AI compute for token investigations
• A dedicated server for sandbox testing
• X API credits for research and replies
• RPC access for on-chain checks
• Database, storage, hosting, and monitoring
The goal is simple: keep it free, keep it faste, better research, and full access for everyone. No Pro subscription required.
Here we go
Replying to @velvetpanics
Cookd investigation
Cookd Bot (COOKD): launch-stage token, identity conflict and unverified scan execution
Token: Cookd Bot
Observed risk: HIGH
Model confidence (self-assessed): 84%
Retrieval coverage: 61%
Report time: 2026-11-07T04:22:35.479+00:00
SUMMARY
The exact mint has revoked mint/freeze controls and an identifiable reserve, but its market history is only launch-stage. Its AI-research narrative is explicit, while official affiliation conflicts with operator configuration and the representative website scan could not complete under sandbox restrictions. [E002] [E006] [E024] [E033]
AI ASSESSMENT
The strongest evidence supports limited token-control protections and a genuine rendered research interface, not a complete safety verdict or proven research engine. [E002] [E028] High risk is driven by the official-identity conflict, launch-stage market, concentrated non-protocol holdings and unverified core output. [E024] [E010] [E001] [E033] The sandbox failure is a coverage gap, not evidence that the service is fraudulent. Confidence measures confidence in this bounded assessment, not the probability of rugging.
LIMITATIONS
- The report covers evidence retrieved on November 7, 2026, approximately one minute after mint creation; it is not a lifetime wallet audit or safety certification.
- GeckoTerminal had no matching indexed pool for candles; Birdeye was unavailable. DEXScreener's chart returned HTTP 403 under Cloudflare protection. No trend, drawdown or volume-fading analysis from actual candles was possible. [E008]
- The attempted market refresh reused the original checkpoint rather than supplying a new snapshot. DEXScreener and RugCheck holder, price and reserve figures are not synchronized. [E001] [E007] [E010]
- Top-holder profiles cover at most 12 recent address signatures each; creator follow-up covers 50 transactions. Address sampling can miss token-account activity, and oldest sampled activity is not wallet age. [E010] [E030]
- Streamflow coverage applies only to the supported program and fixed schedules. Other lockers and program upgrades were not certified. [E003]
- At 04:20:29 UTC, the browser blocked Supabase POSTs for get_scan_availability, list_recent_scans and request_scan. The recorded wait/result ended with a fetch error, not a completed output; this does not establish backend fraud or general service failure. [E033]
- On November 7, a direct public HTTP attempt to the discovered Supabase app_config endpoint returned HTTP 401 with no saved evidence ID. The in-page browser response was available, but direct unauthenticated output access was not; no credentials or access controls were bypassed. [E039]
- The replies-specific X query returned HTTP 400 on November 7 with no saved evidence ID. A broader from:cookdbot search succeeded and returned three posts; deleted, private and historical edits remain outside coverage. [E036]
- No project GitHub repository was linked in the inspected public pages/posts. The JavaScript-resource retrieval did not inspect implementation content; source originality and backend functionality remain unverified. [E029] [E037] [E041]
- Operator configuration has no evidence ID: it states that COOKD has not launched and no official mint is set. External launch claims were preserved as conflicting evidence, not accepted as official authorization.
TOKEN CONTROLS, HOLDERS, DEVELOPER AND MARKET
The exact mint [identifier in report] was initialized on November 7, 2026 at 04:19:21 UTC. Its decoded controls do not expose minting, freezing or additional transfer-control extensions. [E004] [E002] RugCheck reports deploy_platform as "unknown" and launchpad as ; deployment tooling is not a verified creator identity or trust signal. [E007] The incomplete canonical curve has no conventional LP lock. Its reserve counters and RugCheck's approximately 4,228.78 liquidity estimate are not executable exit quotes. Holder-vault balances, curve counters and third-party balances differ across this rapidly changing launch sample and should not be treated as one synchronized snapshot. [E006] [E007] [E010] DEXScreener reports 0.000003611, 3,611.06 market capitalization, three buys, zero sells and 535.88 volume, with a 35.55% increase repeated across all available intervals. This shows indexed early buying, not a durable trend, drawdown history or proven sellability. [E001] A receipt independently verifies one near-launch purchase: 3axMAee… received 27,331,959.316883 tokens against a 1.936678152 SOL transfer to the exact curve. [E031]
NARRATIVE CHECK
Metadata claims a free Solana AI research service covering holders, rug risks and project claims, with website scans and X mentions. [E009] Original X posts expand this to live checks, creator history, liquidity, Streamflow locks, source-backed reports and GPT-6.1sol. [E022] [E026] The account and website explicitly associate the exact mint; this is stronger than a matching symbol but remains publisher-controlled evidence. [E024] [E039] The operator configuration says COOKD has not launched and no official mint is set, so official affiliation remains contradicted by that configuration rather than established by these pages. The retrieved account was created November 6 at 23:25:13 UTC and had three posts and zero followers in the sample; independent adoption or endorsement was not demonstrated. [E023] This is a technology/service narrative, not a substantiated news or person-endorsement story.
Narrative types: technology
WEBSITE AND TECHNOLOGY
The public site renders a mint-search form, research categories, recent-investigation controls and readable terms/privacy documentation. Network observations show Supabase integration; privacy documentation names CometAPI for AI processing. [E028] [E041] The scanner accepted a public wrapped-SOL mint input and attempted request_scan, but sandbox policy blocked that POST and related RPCs; no new report or matching expected Sources output appeared. [E033] No backend implementation or project repository was verified. The delivered JavaScript resource returned successfully but was not substantively inspected, so originality, forks, templates and shipped research logic cannot be assessed from it. [E029] No verified token-required access, revenue share, payment route or other economic utility was established from the reviewed claims. [E026] [E039]
RED FLAGS
- Official launch status conflicts with operator configuration (high): The account announces this exact mint as live and the website calls it cookd's token, while operator configuration says no official mint or launch exists. The external claims cannot override that identity boundary. [E024] [E039] [E024, E039]
- Most non-protocol holdings sit in a small launch-stage group (moderate): The top 20 non-protocol wallets hold approximately 77.3% of the non-protocol supply. Top-holder increases occurred between 04:19:21 and 04:19:56 UTC; this creates potential selling pressure but does not prove bundling or common ownership. [E010] [E012] [E017] [E018] [E010, E012, E017, E018]
- Market evidence is too immature to demonstrate resilience (moderate): Only a tiny launch snapshot with three indexed buys and no indexed sells was available. The initial price rise does not establish sustained demand or reliable exits. [E001] [E001]
POSITIVE SIGNALS
- Inspected mint-level control powers are revoked (moderate): No mint or freeze authority remains, and the two decoded metadata extensions have null control authorities. No additional transfer-control extension was observed. [E002] [E002]
- Largest balance is a verified protocol reserve (moderate): The apparent 54.02% largest holder is the canonical curve reserve, not an ordinary independently controlled whale. Excluding it materially changes the concentration assessment. [E010] [E006] [E010, E006]
- Public documentation states meaningful research limitations (low): Terms explicitly acknowledge AI errors, incomplete sources, uncertain holder links and the limited scope of sandbox checks. These are useful disclosures, although not proof that completed reports apply them correctly. [E037] [E037]
CLAIM CHECKS
- The website and cookdbot explicitly associate this exact mint with their Cookd branding. [identity; supported]
The original announcement includes the exact CA; the website panel and recorded configuration response display the same mint. This verifies their claim of association, not official operator authorization. [E024] [E039] [E024, E039]
- This is the officially launched COOKD token of the investigator operator. [identity; contradicted]
External sources claim a launch, but operator configuration states COOKD has not launched and no official mint is set. The contradiction must remain explicit; the external account's authorization was not independently established. [E024] [E039] [E024, E039]
- The token has revoked mint and freeze authorities. [onchain; supported]
Direct decoded mint state shows both authorities null. [E002] [E002]
- Liquidity is secured by a verified conventional 100% LP lock. [onchain; contradicted]
RugCheck presents a 100% LP-locked field, but the inspected market is an incomplete curve with no conventional LP token. The label does not verify an escrow-backed AMM lock. [E007] [E006] [E007, E006]
- The observed top-holder timing proves coordinated or commonly owned wallets. [holders; unverified]
The profiles show clustered launch-time increases but no verified common-funding cluster. The largest holder's incoming SOL amounts are only 0.00001 and 0.000001 SOL and do not establish purchase funding or beneficial ownership. [E010] [E011] [E010, E011]
- Website scans produce live source-backed investigations without sign-up. [website; unverified]
The interface exists, but the representative attempt was blocked before report creation; neither research output nor live checks were verified. [E026] [E033] [E026, E033]
- Tagging cookdbot returns analysis and a full-report link. [social; unverified]
The account promises replies, while terms/privacy qualify sharing as enabled or conditional. The bounded recent search returned three promotional posts and no completed reply artifact; no message was sent to test it. This is not a demonstrated operational contradiction. [E026] [E036] [E037] [E041] [E026, E036, E037, E041]
- All features are completely free with no subscription or paywall. [website; unverified]
The X promise and ungated public form are visible, but blocked execution prevented verification of all feature access and ongoing availability. [E022] [E033] [E022, E033]
- GPT-6.1 Sol exists as an OpenAI model. [website; supported]
The retrieved primary OpenAI catalog lists GPT-6.1 Sol with model ID gpt-6.1-sol. This supports model existence only. [E040] [E040]
- Cookd's investigations are powered by GPT-6.1sol. [website; unverified]
X makes the model claim and privacy documentation names CometAPI, but no backend configuration, model receipt or completed output establishes actual model use. [E026] [E041] [E026, E041]
TIMELINE
- 2026-11-06T23:25:13Z | Claimed project X account created [social]
Retrieved account metadata records this creation time; it is account age, not proof of project-development age. [E023] [E023]
- 2026-11-07T04:19:00Z | Research workflow published [social]
Original post describes website investigations, X replies, source checks, Streamflow coverage and GPT-6.1sol. [E026] [E026]
- 2026-11-07T04:19:03Z | Free-service promise published [social]
Original introductory post promises no subscription, Pro plan or paywall. [E022] [E022]
- 2026-11-07T04:19:21Z | Exact mint initialized [onchain]
Successful initialization identifies the payer/account funder and creation-time mint authority; the payer also receives tokens from the curve in that transaction. [E004] [E004]
- 2026-11-07T04:19:32Z | Exact-mint launch claim published [social]
cookdbot announces COOKD as live with this CA. Temporal proximity to creation does not independently establish official authorization. [E024] [E024]
- 2026-11-07T04:19:33Z | Near-launch top-holder purchase verified [market]
A successful receipt shows the exact mint moving from the curve to 3axMAee… against SOL supplied to that curve. [E031] [E031]
- 2026-11-07T04:20:29.583Z | Representative scan test recorded [website]
Retrieval/test time: wrapped-SOL input and submit actions were recorded, but sandbox POST restrictions prevented the expected source-backed report. [E033] [E033]
CHECK COVERAGE
- identity: ok. Read mint controls and 2 token extensions at slot 466375572.
- onchain: ok. Bonding-curve reserve counters are program state, not proof of executable exit depth. A curve has no conventional LP lock; completion alone does not verify migration, program upgrade controls, or future withdrawal rights. LP ownership, burning and time-locking are distinct. This tool does not certify lock-contract withdrawal conditions, upgradeability, or future liquidity safety. Verify program IDs, token mints, account roles and instruction outcomes. A successful receipt alone does not establish the app caused it, a wallet identity, repeated automation or net profit.
- holders: ok. Wallet identities, exchange custody, vesting and unrecognized protocol escrows are not fully labeled. Raw holder concentration can overstate individual control. Profiles cover up to 10 largest observed non-protocol owners and their latest 12 address signatures. Address-signature sampling may miss token-account-only activity. Oldest observed activity is not wallet age. Token movements are not automatically buys or sells. This checks the supported Streamflow mainnet program and fixed schedules. Other lockers, legacy layouts, dynamic price-based unlocks, program upgrades and future token-control changes are not certified.
- developer: ok. A transaction signer, payer, mint authority or fee recipient identifies an on-chain role, not a verified human developer. Recent wallet history is bounded. A common funder does not establish common beneficial ownership. Recent history is bounded and is not a complete lifetime wallet audit. Funding relationships do not prove common wallet ownership. Token decreases are not called sales without transaction evidence.
- market: partial. A current market snapshot does not contain historical candles or establish wash trading. A separate chart/history investigation is required. Project links and token labels in market metadata are publisher claims; they do not prove affiliation. No real candles were available. Use the market snapshot for a clearly bounded analysis. Page returned HTTP 403. Browser observations establish visible behavior for the recorded inputs only; inaccessible backend implementation, training, ownership, and performance claims are not verified. Some network requests were blocked or failed. This can limit observed functionality and is not by itself evidence of fraud. HTTP 403 from Sandbox blocked POST /cdn-cgi/challenge-platform/h/b/fo/2671310112:1794021012:TKYeTRQrOsEo6pCUjnBibzjg7eS0nI8BZLG4Wtj_SCc/a5698b132a5e36eb/VaEXR.. 8ShsNKhZD6n774tIedv7hhiTRDsS2bnqd3NC6mJ1LzUbRw28S.
- social: partial. An authentic post or verified account does not establish endorsement of this Solana mint. Explicit mint association must be checked. Deleted, private, historical edits, and all prior account-name changes may be inaccessible. Post ordering is not evidence that the earliest-ever mention was found. This is a bounded sample of latest posts, not a complete account history. Use search_x with time ranges for historical checks. Identity, biography links, and verification badges do not independently establish that this account issued or endorsed the exact mint. Historical handles, deleted posts, and all edit versions are not reconstructed. Recent search only covers the last seven days. The provider returned HTTP 400.
- news: not_run. This category was not checked.
- website: partial. Website text, links, canonical URLs, and publication metadata are claims by the page author. Corroborate identity and important assertions independently. Static retrieval does not prove an app works. JavaScript-only or gated content may be missing; use browser inspection for observable behavior. Very little readable page content was returned. This may be an empty page, access wall, or JavaScript shell; its claims have not been substantively inspected. Browser observations establish visible behavior for the recorded inputs only; inaccessible backend implementation, training, ownership, and performance claims are not verified. Some network requests were blocked or failed. This can limit observed functionality and is not by itself evidence of fraud. Sandbox blocked POST /rest/v1/rpc/get_scan_availability. Sandbox blocked POST /rest/v1/rpc/list_recent_scans. Sandbox blocked POST /rest/v1/rpc/request_scan. The resource content was not inspected. Use an appropriate document or browser tool before verifying its claims. Authentication, account credit, or access entitlement is unavailable.
- github: not_run. This category was not checked.
FOLLOW-UP CHECKS
- Resolve official authorization through an independently authoritative operator announcement naming the exact mint; do not rely solely on the current namesake account or site.
- Obtain a public completed investigation with stable source links and compare its holder, authority, lock and liquidity findings against independent chain data.
- Verify an existing public X bot reply and its full-report link without sending a request or activating automation.
- Revisit actual candles and two-sided trades after indexing, and inspect any migration transaction and resulting AMM withdrawal rights.
- Expand wallet and token-account history around launch to investigate funding provenance and meaningful holder links without equating timing or shared services with ownership.
- Inspect disclosed backend source and model execution evidence if published; verify caching, error handling and feature access within permitted sandbox policy.
EVIDENCE REFERENCES
[E001, E002, E003, E004, E006, E007, E009, E010, E023, E024, E026, E028, E029, E030, E031, E033, E037, E039, E040, E041]
Open the full report for source links and collection timestamps.
Full report and sources: cookdbot.fun/#/r/c29eca2c-72…
AI assessment; not a guarantee.
Stop: @cookdbot stop.
X is blocking us from posting CA in the replies
Removing CA's and pushing update now
Scans are live and Cookd is scanning live:
cookdbot.fun/#/scanning
We're getting huge volumes of inquiries on X, all requests are being processed and will be replied to in order.
You can check the progress of X token scan requests live on the app:
cookdbot.fun/#/scanning
Looking into this asap
Replying to @GhostOfSol_
TRACE: The scan did not produce a validated report. No risk conclusion is available.
Full report and sources: cookdbot.fun/#/r/32b71cde-78…
AI assessment; not a guarantee.
Stop: @cookdbot stop.










