NestDaddy

DeFade — Multi-Chain Memecoin Analyzer

org.defade/defade · v1.1.8

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

Connect Remote server

Terminal
claude mcp add --transport http defade https://api.defade.org/mcp --header "x-api-key: <X_API_KEY>"
~/.cursor/mcp.json
{
  "mcpServers": {
    "defade": {
      "url": "https://api.defade.org/mcp",
      "headers": {
        "x-api-key": "<X_API_KEY>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "defade": {
      "type": "http",
      "url": "https://api.defade.org/mcp",
      "headers": {
        "x-api-key": "<X_API_KEY>"
      }
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://api.defade.org/mcp

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools 15 found in our last check

  • 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, blac…

  • 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_tok…

  • 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 paginatio…

  • 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 su…

  • 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, LP MULTI-PROVIDER…

  • 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 predi…

  • 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…

  • 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 whe…

  • 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 fi…

  • 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…

  • 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 o…

  • 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.…

  • 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 reall…

  • 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…

  • 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 on…

Headers

NameDescription
x-api-key
Optional, secret
DeFade API key (starts with df_). Optional for connecting: initialize and tools/list work without it, and directory health checks can run keyless. Scan tools answer with instructions to get a key (https://defade.org/developers) until one is supplied. Tool calls are metered against the key's plan ex…

Details

Endpointhttps://api.defade.org/mcp (Streamable HTTP)
First published10 Oct 2026
Last updated10 Oct 2026
Registry nameorg.defade/defade

More finance and crypto servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.