DeFade — Multi-Chain Memecoin Analyzer

Liquidity analysis

get_liquidity

Read-onlyIdempotent

Liquidity pool analysis for one token: which DEX holds the deepest pool, its depth in USD, and whether the LP tokens are burned, locked or still in someone's hands. lpStatus is the verdict — LP BURNED, LP LOCKED, LP UNLOCKED, PARTIALLY BURNED, LP NOT LOCKABLE, BONDING CURVE (still on a launchpad curve, no pool yet) or NO LP FOUND, with combinations spelled out — and lpBurnPct, lpLockPct and poolLocks carry the evidence. Use it to answer whether liquidity is locked, how deep it is, and whether the position could be pulled: LP UNLOCKED means it can be pulled at any time. Cached for about two minutes. A token with no pool returns empty liquidity data, which is itself a warning on a token that is trading. Not for price or volume (get_token_price), market cap (get_token_scan) or holder concentration (get_holders). Arguments: address and chain — pools live per chain, so a 0x address needs the chain it trades on, and a Base pool is not found under ethereum; 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
`dex`	No	Which DEX holds the deepest pool.
`risk`	No	Liquidity risk label; lpEvidence carries the on-chain evidence behind it.
`token`	No	The address that was scanned (on get_token_scan, the full token metadata object instead).
`lpStatus`	No	Headline pool verdict: LP BURNED, LP LOCKED, LP UNLOCKED, PARTIALLY BURNED, LP NOT LOCKABLE, LP HELD BY DAO (a MetaDAO token: the vault of its DAO holds the liquidity), BONDING CURVE, NO LP FOUND, or a spelled-out combination.
`lpBurnPct`	No	Percent of LP tokens burned; lpLockPct is the percent locked.
`poolLocks`	No	Per-pool lock detail with lpLockable and an lpNote in words.
`poweredBy`	No	Always "DeFade.org".
`timestamp`	No	ISO time the response was assembled.
`totalLiquidityUsd`	No	Combined USD depth across pools; pools lists them and poolCount counts them. On an EVM chain, null when the pair feed gives no pool a liquidity figure, or the reserve of a bonding curve could not be priced: unknown, not zero.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedOutput schema / properties / totalLiquidityUsd / description

Previous value: -"Combined USD depth across pools; pools lists them and poolCount counts them."New value: +"Combined USD depth across pools; pools lists them and poolCount counts them. On an EVM chain, null when the pair feed gives no pool a liquidity figure, or the reserve of a bonding curve could not be priced: unknown, not zero."

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 22, 2026

changedOutput schema / properties / lpStatus / description

Previous value: -"Headline pool verdict: LP BURNED, LP LOCKED, LP UNLOCKED, PARTIALLY BURNED, LP NOT LOCKABLE, BONDING CURVE, NO LP FOUND, or a spelled-out combination."New value: +"Headline pool verdict: LP BURNED, LP LOCKED, LP UNLOCKED, PARTIALLY BURNED, LP NOT LOCKABLE, LP HELD BY DAO (a MetaDAO token: the vault of its DAO holds the liquidity), BONDING CURVE, NO LP FOUND, or a spelled-out combination."

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

Changed1 schema field changedSep 6, 2026

changedOutput schema / properties / lpStatus / description

Previous value: -"Headline pool verdict: BURNED, LOCKED, UNLOCKED, NO LP FOUND."New value: +"Headline pool verdict: LP BURNED, LP LOCKED, LP UNLOCKED, PARTIALLY BURNED, LP NOT LOCKABLE, BONDING CURVE, NO LP FOUND, or a spelled-out combination."

Changed8 schema fields changedSep 5, 2026

changedOutput schema / properties / dex / type

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

changedOutput schema / properties / lpBurnPct / type

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

changedOutput schema / properties / lpStatus / type

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

changedOutput schema / properties / poolLocks / type

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

changedOutput schema / properties / poweredBy / type

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

changedOutput schema / properties / risk / type

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

changedOutput schema / properties / timestamp / type

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

changedOutput schema / properties / totalLiquidityUsd / type

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

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "dex": {
+      "description": "Which DEX holds the deepest pool.",
+      "type": "string"
+    },
+    "lpBurnPct": {
+      "description": "Percent of LP tokens burned; lpLockPct is the percent locked.",
+      "type": "number"
+    },
+    "lpStatus": {
+      "description": "Headline pool verdict: BURNED, LOCKED, UNLOCKED, NO LP FOUND.",
+      "type": "string"
+    },
+    "poolLocks": {
+      "description": "Per-pool lock detail with lpLockable and an lpNote in words.",
+      "type": "array"
+    },
+    "poweredBy": {
+      "description": "Always \"DeFade.org\".",
+      "type": "string"
+    },
+    "risk": {
+      "description": "Liquidity risk label; lpEvidence carries the on-chain evidence behind it.",
+      "type": "string"
+    },
+    "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)."
+    },
+    "totalLiquidityUsd": {
+      "description": "Combined USD depth across pools; pools lists them and poolCount counts them.",
+      "type": "number"
+    }
+  },
+  "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.8/5.0

Behavior5/5

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

Annotations already cover readOnly/idempotent safety, and the description adds real operational context: ~2-minute caching, one API unit cost, and the semantic meaning of 'LP UNLOCKED means it can be pulled at any time'. It also discloses the edge case that a token with no pool returns empty liquidity data, which is a warning signal, not an error.

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?

It is dense but front-loaded: purpose first, then the lpStatus verdict vocabulary, then usage, then exclusions, then arguments. The lpStatus enumeration is long but earns its place by defining the return codes. A single long paragraph rather than structured lists slightly reduces scannability.

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?

With an output schema present, the description need not explain return shape, yet it still defines every lpStatus verdict and names the evidence fields (lpBurnPct, lpLockPct, poolLocks) that support them. Combined with caching, cost and the no-pool edge case, an agent has everything needed to call and interpret it.

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 coverage is 100%, so baseline is 3; the description still adds the cross-chain reasoning that a 0x address needs its chain and that a Base pool is not found under ethereum, which is a concrete failure mode worth restating. It does not add more than that, and the parameter names themselves are only enumerated briefly ('Arguments: address and chain').

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 opening sentence states a specific verb and resource ('Liquidity pool analysis for one token') plus the exact scope: deepest pool, depth in USD, LP burn/lock status. This is clearly distinguishable from get_token_price, get_token_scan and get_holders, which are named in the exclusions.

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?

Usage is stated positively ('Use it to answer whether liquidity is locked, how deep it is, and whether the position could be pulled') and negatively with named alternatives ('Not for price or volume (get_token_price), market cap (get_token_scan) or holder concentration (get_holders)'). The routing decision is fully determined.

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?