Security & Testing

defade.org

Provides token risk analysis and security scanning for cryptocurrency, including rug pull detection, holder distribution, liquidity analysis, and whale tracking.

1 endpoint15 known toolsFirst detected August 29, 2026Last detected September 11, 2026

ENDPOINT 1

https://api.defade.org/mcp

No auth detected

MCP server metadata

Name: defade
Version: 1.1.7

Capabilities

tools

Server instructions

DeFade analyses memecoin contracts on solana, ethereum, base, robinhood and returns on-chain forensic evidence: rug pull risk, holder distribution, launch bundles, snipers, insider networks, funding origins, dev wallet behaviour and liquidity. Two scores point in OPPOSITE directions — do not mix them up: • get_token_scan returns risk.score, a SAFETY score: 100 is clean, low is dangerous. • get_rug_score returns rugScore, a rug pull PROBABILITY: 0 is clean, high is dangerous. Every tool needs a DeFade key (x-api-key header, or ?api_key= on the connector URL). An API-plan key is metered in units: one per call, five for the two heavy traces on EVM chains. The connector key that comes with a DeFade Pro web subscription (df_mcp_…, from https://defade.org/dashboard) instead spends the plan's monthly scan allowance, one scan per distinct token per day, shared with the website. Rate limits are per minute and per day by plan; get_usage reports the remaining allowance. API keys: https://defade.org/developers Start with get_token_scan for any "is this a rug / is this safe" question, then call the specific module tools for the evidence behind the verdict. Always report which token you scanned, and never present a low-risk result as a guarantee: DeFade measures known rug patterns, it does not predict price, and none of it is financial advice.

Known tools 15

get_token_scan

Run a full DeFade scan on one token contract: token metadata, holder distribution, creator history (wallet age, previous token launches) and the headline risk verdict.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

get_whales

Wallets holding at least 1% of supply once pools, lockers, treasuries and custodial accounts are removed.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

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.

Potential side effects

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.

Inferred read-only

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.

Inferred read-only

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.

Potential side effects

get_fee_fingerprint

Wallets whose transactions pin an identical compute-unit price or Jito tip — one operator's bot settings showing up across every wallet it drives.

Inferred read-only

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.

Inferred read-only

get_usage

Report the calling API key's plan, rate limits and how much of its monthly allowance is left.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.defade]
url = "https://api.defade.org/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "defade": {
      "type": "http",
      "url": "https://api.defade.org/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: defade
Remote MCP URL: https://api.defade.org/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "defade": {
      "url": "https://api.defade.org/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "defade": {
      "type": "http",
      "url": "https://api.defade.org/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "defade",
  "transport": "streamable-http",
  "url": "https://api.defade.org/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.