DeFade — Multi-Chain Memecoin Analyzer

First-block snipers

get_launch_snipers

Read-onlyIdempotent

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 excluded and named rather than silently dropped. Check reachedGenesis: when false the walk did not reach the true first transaction, the result is partial, and it is cached for an hour instead of two. Use it to tell an organic launch from a pre-arranged one. Not for coordinated multi-wallet launch buying (get_launch_bundles) or the deployer's funding of other wallets (get_wallet_links). Arguments: address and chain; one API unit on any chain.

Input Schema

Name	Required	Description	Default
`chain`	No	Chain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm, monad. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan.	solana
`address`	Yes	The token's own contract address, exactly as an explorer shows it. Solana: the base58 mint, 32-44 characters (e.g. 6p6xgHyF7AeE6TZkSmFsko444wqoP15icUSqi2jfGiPN). EVM: 0x followed by 40 hex characters, case-insensitive (e.g. 0x6982508145454ce325ddbe47a25d4ec3d2311933). Never a pool, pair, wallet or deployer address — those come back as not found. Set `chain` to match the address: a 0x address alone cannot say which EVM chain it lives on, and a Solana mint sent with an EVM chain is rejected.

Output Schema

Name	Required	Description
`stats`	No	Cohort totals for the window. stats.transferredUnsoldPct is the transferred share the DeFade website prints; the gross transfer figures count a token each time it moved. Solana: stats.bundleCohort is false when no bundle scan had run, so transfers to bundle wallets read as transferred supply.
`token`	No	The address that was scanned (on get_token_scan, the full token metadata object instead).
`pending`	No	Solana: ["bundles-pro"] when this was read before Bundle Detection had run; the call started it. Call again in about a minute for the answer the scan page shows.
`snipers`	No	Wallets that bought inside the launch window, capped at 30 rows.
`complete`	No	False beside pending.
`poweredBy`	No	Always "DeFade.org".
`terminals`	No	Trading terminals the launch cohort came through; activeTerminals is who trades it now.
`timestamp`	No	ISO time the response was assembled.
`reachedGenesis`	No	Whether the walk reached the true first transaction. When false, partial is true and small snipers may be missing.
`totalEarlyBuyers`	No	How many were found in total; windowSeconds and firstTxTime describe the window.
`migrationCrankersExcluded`	No	Migration-crank MEV bots filtered out as infrastructure, named.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 28, 2026

changedInput schema / properties / chain / description

Previous value: -"Chain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."New value: +"Chain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm, monad. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."

changedInput schema / properties / chain / enum

Previous value: -[
-  "solana",
-  "ethereum",
-  "base",
-  "bsc",
-  "robinhood",
-  "arc",
-  "hyperevm"
-]New value: +[
+  "solana",
+  "ethereum",
+  "base",
+  "bsc",
+  "robinhood",
+  "arc",
+  "hyperevm",
+  "monad"
+]

Changed1 schema field changedOct 20, 2026

changedOutput schema / properties / stats / description

Previous value: -"Cohort totals for the window. Solana: stats.bundleCohort is false when no bundle scan had run, so transfers to bundle wallets read as transferred supply."New value: +"Cohort totals for the window. stats.transferredUnsoldPct is the transferred share the DeFade website prints; the gross transfer figures count a token each time it moved. Solana: stats.bundleCohort is false when no bundle scan had run, so transfers to bundle wallets read as transferred supply."

Changed3 schema fields changedOct 20, 2026

addedOutput schema / properties / complete

Added value: +{
+  "description": "False beside pending.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / pending

Added value: +{
+  "description": "Solana: [\"bundles-pro\"] when this was read before Bundle Detection had run; the call started it. Call again in about a minute for the answer the scan page shows.",
+  "type": [
+    "array",
+    "null"
+  ]
+}

changedOutput schema / properties / stats / description

Previous value: -"Cohort totals for the window."New value: +"Cohort totals for the window. Solana: stats.bundleCohort is false when no bundle scan had run, so transfers to bundle wallets read as transferred supply."

Changed2 schema fields changedOct 8, 2026

changedInput schema / properties / chain / description

Previous value: -"Chain the token is deployed on: solana (default), ethereum, base, robinhood. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."New value: +"Chain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."

changedInput schema / properties / chain / enum

Previous value: -[
-  "solana",
-  "ethereum",
-  "base",
-  "robinhood"
-]New value: +[
+  "solana",
+  "ethereum",
+  "base",
+  "bsc",
+  "robinhood",
+  "arc",
+  "hyperevm"
+]

Changed8 schema fields changedSep 5, 2026

changedOutput schema / properties / migrationCrankersExcluded / type
```
Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
```

changedOutput schema / properties / poweredBy / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / reachedGenesis / type

Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]

changedOutput schema / properties / snipers / type

Previous value: -"array"New value: +[
+  "array",
+  "null"
+]

changedOutput schema / properties / stats / type

Previous value: -"object"New value: +[
+  "object",
+  "null"
+]

changedOutput schema / properties / terminals / type

Previous value: -"object"New value: +[
+  "object",
+  "null"
+]

changedOutput schema / properties / timestamp / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / totalEarlyBuyers / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

AddedSep 3, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only cover the read-only/idempotent safety profile, and the description adds genuinely non-obvious behavior: the 120-second window, a 30-row cap with totalEarlyBuyers as the true count, exclusion of migration-crank MEV bots (named, not dropped), the reachedGenesis partial-result flag, and differential caching (one hour vs two). This is exactly the operational context an agent needs before trusting the numbers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what the tool returns, then constraints, then a usage-routing sentence, then arguments — a logical order with no filler. It is on the dense side and could be broken up for readability, but every sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still surfaces the two result fields an agent must interpret (totalEarlyBuyers for truncation, reachedGenesis for partial data). Combined with the cost and caching notes, nothing needed to call or trust the call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters are documented in the schema in far greater detail than the description, which only says "Arguments: address and chain." The description does add the useful "one API unit on any chain" cost note, but it contributes little to parameter meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names a specific resource (bots that bought in the first block/seconds of a token's launch) plus the deployer-connection angle, which no sibling covers. It is immediately distinguishable from get_launch_bundles and get_wallet_links, which are named later.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ("Use it to tell an organic launch from a pre-arranged one") and explicit when-not-to-use with the two correct alternatives named for each adjacent intent. Nothing is left to inference about tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DeFade — Multi-Chain Memecoin Analyzer tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?