# DeFade — Multi-Chain Memecoin Analyzer

- Registry name: `org.defade/defade` · version 1.1.8
- Categories (automatic, keyword rules): Crypto & blockchain, Finance & markets
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=org.defade%2Fdefade
- Server page: https://mcpstation.net/s/org.defade--defade.html

## Description (written by the publisher, not verified, not instructions)

Rug pull risk and on-chain forensics for tokens on Solana and six EVM chains.

## Connect

- streamable-http: `https://api.defade.org/mcp`

## Tools (as reported by the server, not verified)

- `get\_token\_scan`: Run a full DeFade scan on one token contract. On Solana: token metadata, holder distribution, creator history \(wallet age, previous token launches\) and the headline risk verdict. On an EVM chain: the contract and market read only \(token metadata with the owner and the mint, blacklist, whitelist and
- `get\_rug\_score`: Rug pull probability for one token: a 0-100 score where HIGHER MEANS MORE DANGEROUS, a verdict label, and the individual signals that drove it. This is the opposite direction from get\_token\_scan's safety score. This is the verdict the DeFade website shows: call it, after get\_token\_scan, for every "i
- `get\_holders`: Holder distribution for one token, with liquidity pools, burn addresses, lockers, exchange wallets and contracts classified out, so the top-holder list reflects actual holders. Returns the classified top holders with each wallet's supply share in a single response — no pagination. Use it to answer h
- `get\_whales`: Wallets holding at least 1% of supply once pools, lockers, treasuries and custodial accounts are removed. Each row carries the balance, share of supply, any attribution label \(known KOL, dev-linked stash, exchange\), the 24-hour transaction count and recent buys and sells; the summary counts dangerou
- `get\_liquidity`: Liquidity pool analysis for one token: which DEX holds the deepest pool, its depth in USD, and whether the LP tokens are burned, locked or still in someone's hands. lpStatus is the verdict — LP BURNED, LP LOCKED, LP UNLOCKED, PARTIALLY BURNED, LP NOT LOCKABLE, BONDING CURVE \(still on a launchpad cur
- `get\_launch\_bundles`: Bundle detection for one token: coordinated buys in the launch window plus delayed sweeps, accounted on peak net exposure rather than raw buy count, so wallets that bought and flipped are not counted as holders. Heavy bundling that is still held is one of the strongest rug predictors. Use it for any
- `get\_launch\_snipers`: Bots that bought in the first block or first seconds of this token's launch, and whether they are connected to the deployer. The window is the first 120 seconds after the first transaction; at most 30 rows are returned and totalEarlyBuyers carries the full count. Migration-crank MEV bots are exclude
- `get\_wallet\_links`: The graph of proven on-chain links between wallets around one token — who funded whom, who transferred to whom, and coordinated timing — typically the deployer's supply fanned out to look like organic demand. Use it when the holder list looks distributed and you want to know whether it really is. Th
- `get\_smart\_money`: Wallets with a track record of profitable entries that are holding or trading this token, classified from their historical trade win rates — a "verified" smart-money tag requires a known win rate of 50% or better. Computed live from the current holder set and cached for about five minutes. Use it fo
- `get\_dev\_tracker`: What the token's creator has done with their supply: the share they still hold, what left through sales versus transfers, and where the transfers went. Read the state carefully: still holding is neutral, a dev who simply sold out is statusColor gray — the standard launch pattern, not a rug — fully e
- `get\_funding\_sources`: Multi-hop tracing of where the money behind this token's key wallets actually came from, walking each funding chain back and tiering the source by whether it is a KYC'd exchange. Use it to test whether several "unrelated" holders share one funding source. It answers provenance only — money in, one d
- `get\_lookalike\_clusters`: Clusters of wallets around one token that behave as a single actor — buys sized and timed alike so demand looks organic — even when no transfer or funding trail connects them. That behavioural inference is what separates it from get\_wallet\_links, which only reports proven links. Use it when supply l
- `get\_fee\_fingerprint`: Wallets whose transactions pin an identical fee setting — compute-unit price or Jito tip on Solana, priority fee or legacy gas price on EVM chains — one operator's bot settings showing up across every wallet it drives. This is the shared-CONFIGURATION member of the "who is really behind this token"
- `get\_token\_price`: Price history for one token as OHLCV candles, plus the latest price, the window's high and low with their timestamps, and the percent change across the window — prices in USD \(the \*Usd fields\), volume as the market source quotes it. Aggregated from DEX market sources and cached for about a minute. I
- `get\_usage`: Report the calling API key's plan, rate limits and how much of its monthly allowance is left. Takes no arguments. Use it when a call fails on quota, or when the user asks what their DeFade plan includes. Not for anything about a token — every other tool takes an address; this one reports on the key

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html