Who Deployed This Solana Token, and Have They Rugged Before?

How do you find who deployed a Solana token?

Start with the mint address, not the ticker. Tickers are copied constantly, and the wrong mint gives you a clean-looking history for a different token.

A deployer lookup resolves the wallet that created the mint, then lists the other tokens that wallet launched, with each one's current liquidity, market cap and LP burn. The "who" matters less than the "what pattern".

Here is the plain-English prompt, as you would type it into Claude or ChatGPT with the StalkChain MCP connected:

Who deployed 3xrw3JKyaSYjzksYc8nrZE1kReQAxoHT3epi3P1mpZVf on Solana,
and what else have they launched?

And the tool call it makes:

stalkchain_token_deployer
  token: "3xrw3JKyaSYjzksYc8nrZE1kReQAxoHT3epi3P1mpZVf"

Pulled Oct 8, 2026, 07:15 UTC via StalkChain's MCP (stalkchain_token_deployer). StalkChain's deployer checks cover Solana only.

What does the real response look like?

This is the trimmed response. The real one lists 50 tokens, so I kept the header and the first four rows.

{
  "deployer": "dtrzJPj7yDdvm6eRqBAgxsK2sMJeD9HhBEBB3XMedXy",
  "launchedToken": "CAPYBARA",
  "tokensLaunched": 494,
  "graduated": 157,
  "stillLiquid": 491,
  "tokens": [
    { "symbol": "CAPYBARA", "liquidityUsd": 76013.17, "marketCapUsd": 579064.1, "lpBurnedPercent": 100, "hasSocials": true },
    { "symbol": "FTR",      "liquidityUsd": 27374.5,  "marketCapUsd": 59125.24,  "lpBurnedPercent": 100, "hasSocials": true },
    { "symbol": "DARK",     "liquidityUsd": 21448.81, "marketCapUsd": 9999.93,   "lpBurnedPercent": 100, "hasSocials": false },
    { "symbol": "SMART",    "liquidityUsd": 11581.39, "marketCapUsd": 5397.72,   "lpBurnedPercent": 100, "hasSocials": true }
    // ...46 more rows, the list is capped at 50
  ]
}

Same call over REST:

curl -G https://data.stalkchain.com/api/v1/tools/stalkchain_token_deployer \
  -H "Authorization: Bearer sc_YOUR_API_KEY" \
  -d token=3xrw3JKyaSYjzksYc8nrZE1kReQAxoHT3epi3P1mpZVf

Live numbers move. An earlier pull the same morning showed 493 launches and a CAPYBARA market cap of $312k. By this pull it was 494 launches and $579k. Treat any figure here as a snapshot, which is why every block on this page carries a timestamp.

What do the fields mean?

Read the response field by field before you form an opinion.

• deployer: the wallet that created the mint. Truncated, this is dtrz…edXy.
• tokensLaunched (494): every token this wallet has launched, not just the ones in the list.
• graduated (157): launches that moved off the bonding curve to a full pool. That is 31.8% of 494.
• stillLiquid (491): tokens that still have a pool. Almost meaningless here, because a $4k-market-cap token with $8k of liquidity counts as "liquid".
• lpBurnedPercent: share of liquidity-provider tokens burned. All 50 listed rows show 100%.
• hasSocials: a link exists. 46 of the 50 rows have one, which says little because socials are free to attach.

Two things to notice. First, the list holds 50 tokens out of 494, and there is no page parameter, so you see roughly the top tenth. Second, there is no per-token outcome field. The response does not say "rugged" or "dead". You infer outcomes from market cap and liquidity.

Is 494 launches a serial rugger?

No, not by itself. A person rarely hand-crafts 494 coins. A wallet with that count is almost always a launchpad, a bot, or an app that creates tokens on behalf of many users.

Look at the rows. Six tokens show a market cap of exactly $4,048.30 and liquidity of exactly $8,687.65. Six more share $4,038.06 and $8,665.67. Several symbols repeat, with KOTH twice and WAKGTMI three times. Real, independent launches do not land on identical numbers to the cent.

That pattern points to templated launches from one automated source. Compare it with the wallet you are actually worried about, a human who launches a coin, pulls the liquidity and tries again next week. That wallet usually has a handful of launches, not hundreds, and the dead ones are dead because the liquidity was removed.

How do you tell a factory wallet from a serial rugger?

Run these five checks in order. Each one is cheap.

A high launch count with 100% LP burn on all 50 listed rows argues against the classic liquidity-pull rug. The pool cannot be drained by burning what is already burned. That does not make the token safe. It means the deployer-led rug is only one of the ways to lose money here.

Be careful in the other direction too. A low count is not clean. A fresh wallet with one launch has no history because it is new, and new wallets are exactly what a careful rugger uses.

Does the deployer still hold the supply?

History is one half. The other half is what the deployer holds in the token you are looking at right now. For that, pair the lookup with the on-chain read.

stalkchain_token_onchain
  mint: "3xrw3JKyaSYjzksYc8nrZE1kReQAxoHT3epi3P1mpZVf"

Trimmed response from the same morning:

{
  "symbol": "CAPYBARA",
  "mintAuthorityActive": false,
  "freezeAuthorityActive": false,
  "lpBurnedPercent": 100,
  "deployer": "dtrzJPj7yDdvm6eRqBAgxsK2sMJeD9HhBEBB3XMedXy",
  "createdAt": "2026-10-08T03:47:18.000Z",
  "holdersTotal": 3795,
  "concentration": { "top10Percent": 11.38, "devPercent": 0 }
}

Here the picture is consistent with a factory that launches and walks away. Mint authority is off, so no new supply can be minted. Freeze authority is off, so holders cannot be frozen. The dev holds 0% and LP is fully burned.

Skip launch.sniperCount and insiderCount for now. They read 0 for this mint, while a separate early-buyers read for the same token found a large bundled cluster. The two tools disagree, so do not lean on either number until you have checked the early buyers directly. The first-buyers guide shows how.

What if the dev tools come back empty?

For this mint, the FOMO-sourced dev tools (stalkchain_fomo_token_devs and stalkchain_fomo_token_launch_research) returned nothing. The first gave count: 0, devs: []. The second gave deployer: null.

Empty does not mean safe. The tool's own note says an empty list means FOMO knows of no dev holding, not that the token is clean. Those tools only see devs that FOMO users flagged. The on-chain deployer lookup above found a deployer and a creation time for the same mint.

So use the deployer lookup and the on-chain read as your source of truth for who created the token. Use the FOMO dev tools only as an extra layer when a tracked dev exists. The Solana data page describes the same rule: an empty result is a gap in coverage, never a green light.

What should you not conclude?

Keep these limits in mind:

• Do not call a wallet a rugger because of the count. Factory wallets look like serial deployers.
• Do not trust the 50-row list as complete. It is capped, so the other 444 launches are invisible here.
• Do not read stillLiquid as health. It counts any token with a pool, however tiny.
• Do not treat 100% LP burn as safe. It rules out one rug route. Concentration, bundlers and exit liquidity still matter.
• Do not name or accuse a person from a wallet. A deployer address is a technical fact, not an identity.

For the rest of the safety picture, follow the Solana token due diligence checklist, check holder distribution, and read the exit risk guide before you size a position.

How do other tools handle deployer history?

Few publish a lookup guide with a real payload. Nansen defines a "Token Deployer" label in its academy (labels and watchlists 101), which is a label definition rather than a how-to.

Birdeye's rug checker use case includes token creation info as one input among several. GMGN's meme coin safety guide lists "dev has rugged before" as one item in a checklist.

All three are useful. None shows the raw response or warns that a high launch count can mean a factory wallet, which is the part that changes your read.

Run it yourself

Connect the StalkChain MCP server to Claude or ChatGPT, paste a mint, and ask for the deployer, the launch pattern and the authorities together. New accounts get $5 of free credit, no card, and the API exposes the same data. See pricing for plans.

Data, not financial advice. A deployer history narrows the questions you should ask. It does not tell you whether to buy.

FAQ

How do I find the deployer wallet of a Solana token?

Pass the token mint to a deployer lookup such as stalkchain_token_deployer. It returns the creating wallet, the number of tokens that wallet launched, and a list of its other launches with liquidity, market cap and LP burn. You can also pass a wallet directly to inspect it.

Has this memecoin dev rugged before?

The lookup shows launch history, not verdicts. It has no "rugged" field, so you infer outcomes from market cap, liquidity and LP burn per token. Check whether the wallet is a factory first, because a launch count in the hundreds usually is.

What is a serial deployer on Solana?

A wallet that launches many tokens. That can be a person repeating a rug, or a launchpad, bot or app creating tokens for many users. Cadence, identical values across rows, graduation rate and the deployer's own holdings separate the two.

Why is the deployer list limited to 50 tokens?

The response caps at 50 rows with no pagination. For CAPYBARA's deployer that meant 50 of 494 launches were visible. Use the header totals for the full count and treat the rows as a sample.

Is an empty dev list a good sign?

No. For this mint the FOMO dev tools returned zero devs, but they only cover devs that FOMO users flagged. Check the on-chain deployer, mint and freeze authorities, and dev holding percent instead.