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 only 10 minutes instead of 2 hours. 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

TableJSON Schema

Name	Required	Description	Default
`chain`	No	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.	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

TableJSON Schema

Name	Required	Description
`stats`	No	Cohort totals for the window.
`token`	No	The address that was scanned (on get_token_scan, the full token metadata object instead).
`snipers`	No	Wallets that bought inside the launch window, capped at 30 rows.
`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.

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.8/5.0

Behavior5/5

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

Annotations already declare read-only, non-destructive behavior, and the description adds meaningful behavioral details: row limits, totalEarlyBuyers field, partial results on unreached genesis, cache duration, and API unit cost. No contradiction with annotations.

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?

Purpose is front-loaded and details are logically ordered, but some redundancy exists (first block/first seconds vs. 120-second window). Overall it is still appropriately sized for the complexity.

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?

Given an output schema is present, return values need not be explained. The description covers use cases, exclusions, caching behavior, limits, and parameter constraints, leaving nothing ambiguous for an agent to invoke it correctly.

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

Parameters4/5

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

Schema descriptions are already comprehensive (100% coverage), so the baseline is 3. The description adds extra value by mentioning API unit cost and reinforcing the address/chain pairing requirement, pushing it above baseline.

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?

Clearly identifies the resource (first-block snipers) and action (get), and explicitly differentiates from sibling tools by stating this is not for coordinated multi-wallet buying or deployer funding. The title and first sentence align perfectly.

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?

States when to use it ('to tell an organic launch from a pre-arranged one') and when not to use it, naming the alternatives. Also provides concrete parameter guidance for address and chain, including pitfalls like using pool addresses and EVM chain disambiguation.

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?