INDIVIDUAL MCP TOOL
compare_holder_overlap
Compare two or more tokens and return the wallets that hold several of them.
LIVE ENDPOINT
https://api.defade.org/mcp
Connect to this endpoint to inspect the live schema for compare_holder_overlap and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
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.
Related tools
scan_token— Run a full DeFade scan on one token contract: token metadata, holder distribution, creator info and the headline risk verdict.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.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.get_whales— Wallets large enough to move this token's price, and what they have been doing.get_liquidity— Liquidity pool analysis for one token, including burn and lock verification and pool depth.get_bundles— Coordinated buys bundled into the launch of one token — wallets that acquired supply together before the public could.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.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.