DeFade — Multi-Chain Memecoin Analyzer

Smart money

get_smart_money

Read-onlyIdempotent

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. Computed live from the current holder set and cached for about five minutes. Use it for the bullish side of a scan: who informed is in, and when they got in. Not for risk assessment — informed wallets present never offsets a rug signal, and a clean result is not a buy signal — and not for wallet size (get_whales). 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
`token`	No	The address that was scanned (on get_token_scan, the full token metadata object instead).
`summary`	No	analyzed, smartMoneyCount, verifiedCount, experiencedCount, activeTraderCount, retailCount, smartMoneyPct, avgWinRate, signal.
`wallets`	No	Profiled holders, each classified smart money, verified, experienced, active trader or retail, with win rate.
`poweredBy`	No	Always "DeFade.org".
`timestamp`	No	ISO time the response was assembled.
`activeBuys`	No	Other tokens the smart wallets are currently buying.

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"
+]

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"
+]

Changed5 schema fields changedSep 5, 2026

changedOutput schema / properties / activeBuys / type

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

changedOutput schema / properties / poweredBy / type

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

changedOutput schema / properties / summary / type

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

changedOutput schema / properties / timestamp / type

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

changedOutput schema / properties / wallets / type

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

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "activeBuys": {
+      "description": "Other tokens the smart wallets are currently buying.",
+      "type": "array"
+    },
+    "poweredBy": {
+      "description": "Always \"DeFade.org\".",
+      "type": "string"
+    },
+    "summary": {
+      "additionalProperties": true,
+      "description": "analyzed, smartMoneyCount, verifiedCount, experiencedCount, activeTraderCount, retailCount, smartMoneyPct, avgWinRate, signal.",
+      "type": "object"
+    },
+    "timestamp": {
+      "description": "ISO time the response was assembled.",
+      "type": "string"
+    },
+    "token": {
+      "description": "The address that was scanned (on get_token_scan, the full token metadata object instead)."
+    },
+    "wallets": {
+      "description": "Profiled holders, each classified smart money, verified, experienced, active trader or retail, with win rate.",
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedSep 3, 2026

changedInput schema / properties / address / description

Previous value: -"Token contract address. A base58 mint for Solana, or 0x-prefixed for EVM chains. Set `chain` to match — a 0x address alone cannot say which EVM chain it lives on."New value: +"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."

changedInput schema / properties / chain / description

Previous value: -"Which chain the address lives on. Defaults to solana."New 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."

First observedSep 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: discloses that results are computed live from the current holder set, cached for about five minutes, and cost one API unit on any chain. It also pre-empts the most likely misreading by stating that informed wallets present never offsets a rug signal — behavioral context the annotations cannot carry.

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 and the bullish-scan use case are front-loaded, then exclusions, then arguments and cost — a sensible order with no filler sentences. Slightly dense with em-dash parentheticals, and the "Arguments: address and chain" clause is redundant with the schema.

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, so return values need not be explained; what remains — what the tag means, how fresh the data is, what it costs, and how not to interpret it — is all covered. For a two-parameter read tool, an agent has everything needed to call it and interpret it correctly.

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 description coverage is 100%, so both parameters (address, chain) are already fully documented including formats, enum values and EVM/Solana mismatch rejection. The description only adds "Arguments: address and chain; one API unit on any chain," which is a cost note rather than new parameter semantics.

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?

States a specific verb+resource (wallets holding or trading this token) and defines the classification rule precisely — historical trade win rate, with a "verified" tag requiring 50%+. It explicitly names the sibling it is not (get_whales) for wallet size, so an agent can distinguish it without opening a schema.

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?

Gives an explicit positive case ("the bullish side of a scan: who informed is in, and when they got in") plus two explicit exclusions with rationale — not for risk assessment, and a clean result is not a buy signal. It also routes the size question to get_whales by name.

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?