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 endpoint19 known toolsFirst detected August 29, 2026Last detected September 6, 2026

ENDPOINT 1

https://api.defade.org/mcp

No auth detected

MCP server metadata

Name: defade
Version: 1.0.0

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: • scan_token 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. Start with scan_token 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 19

scan_token

Run a full DeFade scan on one token contract: token metadata, holder distribution, creator info 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 large enough to move this token's price, and what they have been doing.

Inferred read-only

get_liquidity

Liquidity pool analysis for one token, including burn and lock verification and pool depth.

Inferred read-only

get_bundles

Coordinated buys bundled into the launch of one token — wallets that acquired supply together before the public could.

Inferred read-only

get_bundles_pro

Deep bundle analysis for one token: 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_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_insider_network

The graph of wallets around one token that look independent but are linked by funding, transfers or 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.

Inferred read-only

get_dev_tracker

What the token's creator has done with their supply.

Inferred read-only

get_funding_origin

Multi-hop tracing of where the money behind this token's key wallets actually came from, tiered by whether the origin is a KYC'd exchange.

Inferred read-only

get_sybil_cluster

Clusters of wallets around one token that behave as a single actor — sized and timed to look like organic demand.

Inferred read-only

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_socials

Social presence and links attached to one token contract.

Inferred read-only

get_token_price

Current market data for one token: price, market cap, liquidity and volume.

Inferred read-only

compare_holder_overlap

Compare two or more tokens and return the wallets that hold several of them.

Inferred read-only

get_trending

Tokens currently trending on a given chain.

Inferred read-only

check_api_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.