Skip to main content
Glama

DeFade — Multi-Chain Memecoin Analyzer

Rug pull probability

get_rug_score
Read-onlyIdempotent

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. This is the opposite direction from get_token_scan's safety score. This is the verdict the DeFade website shows: call it, after get_token_scan, for every "is this safe", "is this a rug" or "should I buy" question, on every chain (on an EVM chain get_token_scan carries no score at all). When complete is false the score is partial: say so, and call again for the rest. Not for the evidence behind the number — it names the signals but does not list the wallets; for who is behind the risk call get_wallet_links, get_dev_tracker or get_launch_bundles. Arguments: address and chain; five API units on Solana and on an EVM chain, because the score reads the scan's modules first — check get_usage before scoring many tokens.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "get_rug_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm, monad, elysium. 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
addressYesThe 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

NameRequiredDescriptionDefault
tokenNoThe address that was scanned (on get_token_scan, the full token metadata object instead).
fusionNoCross-signal wallet correlation; wallets list is empty on non-Pro keys.
pendingNoModules still running when the score was taken, and price-history while the token's price history is still being read; empty when it is complete. Call the tool again for the score with them in.
signalsNoEach contributing signal: what fired, its weight and its explanation.
verdictNoPROBABLY SAFE (0-20), SOME RISK (21+), ELEVATED RISK (45+), HIGH RISK (60+), EXTREME RISK (75+); or a state that overrides the bands: RUGGED / DEAD, ABANDONED / DEAD (failed after its market cap had once passed $5,000, or with no candles to say it never did), NEVER BONDED (a launchpad coin that never left its bonding curve — no pool ever existed), NEVER TOOK OFF (off any curve, its market cap never passed $5,000); rugScore is still returned as a number.
completeNoTrue when nothing is pending: every module the score reads is in it.
coverageNo"full" when the Pro signal set contributed, "free" when only the free signals did — a "free" score has seen less evidence. "partial" when a module was still running after the 25 s this tool waits (Bundle Detection on a token nobody has scanned can take a minute or more): the modules are named in pending and keep running, so call the tool again for the complete score.
rugScoreNoRug probability 0 (safe) to 100 (critical). HIGHER IS MORE DANGEROUS.
poweredByNoAlways "DeFade.org".
timestampNoISO time the response was assembled.
scoreLabelNoNull normally. "NEVER BONDED" or "NEVER TOOK OFF" when the human surfaces print that state instead of the percentage; rugScore is still the number.
bundleSubScoreNoThe bundle component of the score.
proChecksLockedNoHow many Pro-only checks were withheld.
candleReadPendingNoPresent and true when the token's price history was still being read when the score was taken (the call waits for it within its budget): a peak it finds can still make a small token RUGGED / DEAD. pending then names price-history and complete is false; call again a few seconds later for the score with it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / candleReadPending / description
      Previous value: -"Present and true when the token's price history was still being read when the score was taken: a peak it finds can still make a small token RUGGED / DEAD. Call again a few seconds later for the score with it."New value: +"Present and true when the token's price history was still being read when the score was taken (the call waits for it within its budget): a peak it finds can still make a small token RUGGED / DEAD. pending then names price-history and complete is false; call again a few seconds later for the score with it."
    • changedOutput schema / properties / pending / description
      Previous value: -"Modules still running when the score was taken; empty when it is complete. Call the tool again for the score with them in."New value: +"Modules still running when the score was taken, and price-history while the token's price history is still being read; empty when it is complete. Call the tool again for the score with them in."
  2. Changed1 schema field changed
    • addedOutput schema / properties / candleReadPending
      Added value: +{
      +  "description": "Present and true when the token's price history was still being read when the score was taken: a peak it finds can still make a small token RUGGED / DEAD. Call again a few seconds later for the score with it.",
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
  3. Changed2 schema fields changed
    • changedInput schema / properties / chain / description
      Previous 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."New value: +"Chain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm, monad, elysium. 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",
      -  "monad"
      -]New value: +[
      +  "solana",
      +  "ethereum",
      +  "base",
      +  "bsc",
      +  "robinhood",
      +  "arc",
      +  "hyperevm",
      +  "monad",
      +  "elysium"
      +]
  4. Changed1 schema field changed
    • changedOutput schema / properties / verdict / description
      Previous value: -"PROBABLY SAFE (<25), SOME RISK (25+), ELEVATED RISK (45+), HIGH RISK (60+), EXTREME RISK (75+); or a state that overrides the bands: RUGGED / DEAD, ABANDONED / DEAD (failed after its market cap had once passed $5,000, or with no candles to say it never did), NEVER BONDED (a launchpad coin that never left its bonding curve — no pool ever existed), NEVER TOOK OFF (off any curve, its market cap never passed $5,000); rugScore is still returned as a number."New value: +"PROBABLY SAFE (0-20), SOME RISK (21+), ELEVATED RISK (45+), HIGH RISK (60+), EXTREME RISK (75+); or a state that overrides the bands: RUGGED / DEAD, ABANDONED / DEAD (failed after its market cap had once passed $5,000, or with no candles to say it never did), NEVER BONDED (a launchpad coin that never left its bonding curve — no pool ever existed), NEVER TOOK OFF (off any curve, its market cap never passed $5,000); rugScore is still returned as a number."
  5. Changed2 schema fields changed
    • changedOutput schema / properties / scoreLabel / description
      Previous value: -"Null normally. \"NEVER BONDED\" when the human surfaces print that state instead of the percentage; rugScore is still the number."New value: +"Null normally. \"NEVER BONDED\" or \"NEVER TOOK OFF\" when the human surfaces print that state instead of the percentage; rugScore is still the number."
    • changedOutput schema / properties / verdict / description
      Previous value: -"PROBABLY SAFE (<25), SOME RISK (25+), ELEVATED RISK (45+), HIGH RISK (60+), EXTREME RISK (75+); or a state that overrides the bands: RUGGED / DEAD, ABANDONED / DEAD, NEVER BONDED (a launchpad coin that never left its bonding curve — no pool ever existed; rugScore is still returned as a number)."New value: +"PROBABLY SAFE (<25), SOME RISK (25+), ELEVATED RISK (45+), HIGH RISK (60+), EXTREME RISK (75+); or a state that overrides the bands: RUGGED / DEAD, ABANDONED / DEAD (failed after its market cap had once passed $5,000, or with no candles to say it never did), NEVER BONDED (a launchpad coin that never left its bonding curve — no pool ever existed), NEVER TOOK OFF (off any curve, its market cap never passed $5,000); rugScore is still returned as a number."
  6. Changed2 schema fields changed
    • 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"
      +]
  7. Changed3 schema fields changed
    • addedOutput schema / properties / complete
      Added value: +{
      +  "description": "True when nothing is pending: every module the score reads is in it.",
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / coverage / description
      Previous value: -"\"full\" when the Pro signal set contributed, \"free\" when only the free signals did — a \"free\" score has seen less evidence. (\"partial\" only appears on the raw API when a caller declines to wait; this tool always waits for the complete answer.)"New value: +"\"full\" when the Pro signal set contributed, \"free\" when only the free signals did — a \"free\" score has seen less evidence. \"partial\" when a module was still running after the 25 s this tool waits (Bundle Detection on a token nobody has scanned can take a minute or more): the modules are named in pending and keep running, so call the tool again for the complete score."
    • addedOutput schema / properties / pending
      Added value: +{
      +  "description": "Modules still running when the score was taken; empty when it is complete. Call the tool again for the score with them in.",
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
  8. Changed2 schema fields changed
    • 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"
      +]
  9. Changed1 schema field changed
    • changedOutput schema / properties / coverage / description
      Previous value: -"\"full\" when the Pro signal set contributed, \"free\" when only the free signals did — a \"free\" score has seen less evidence."New value: +"\"full\" when the Pro signal set contributed, \"free\" when only the free signals did — a \"free\" score has seen less evidence. (\"partial\" only appears on the raw API when a caller declines to wait; this tool always waits for the complete answer.)"
  10. Changed2 schema fields changed
    • addedOutput schema / properties / scoreLabel
      Added value: +{
      +  "description": "Null normally. \"NEVER BONDED\" when the human surfaces print that state instead of the percentage; rugScore is still the number.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / verdict / description
      Previous value: -"PROBABLY SAFE (<25), SOME RISK (25+), ELEVATED RISK (45+), HIGH RISK (60+), EXTREME RISK (75+), or RUGGED."New value: +"PROBABLY SAFE (<25), SOME RISK (25+), ELEVATED RISK (45+), HIGH RISK (60+), EXTREME RISK (75+); or a state that overrides the bands: RUGGED / DEAD, ABANDONED / DEAD, NEVER BONDED (a launchpad coin that never left its bonding curve — no pool ever existed; rugScore is still returned as a number)."
  11. Changed3 schema fields changed
    • removedOutput schema / properties / coverage / additionalProperties
      Removed value: -true
    • changedOutput schema / properties / coverage / description
      Previous value: -"Which inputs were available; a score without liquidity or holder data is weaker and says so."New value: +"\"full\" when the Pro signal set contributed, \"free\" when only the free signals did — a \"free\" score has seen less evidence."
    • changedOutput schema / properties / coverage / type
      Previous value: -[
      -  "object",
      -  "null"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  12. Changed9 schema fields changed
    • changedOutput schema / properties / bundleSubScore / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / coverage / type
      Previous value: -"object"New value: +[
      +  "object",
      +  "null"
      +]
    • changedOutput schema / properties / fusion / type
      Previous value: -"object"New value: +[
      +  "object",
      +  "null"
      +]
    • changedOutput schema / properties / poweredBy / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / proChecksLocked / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / rugScore / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / signals / type
      Previous value: -"array"New value: +[
      +  "array",
      +  "null"
      +]
    • changedOutput schema / properties / timestamp / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / verdict / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
  13. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "bundleSubScore": {
      +      "description": "The bundle component of the score.",
      +      "type": "number"
      +    },
      +    "coverage": {
      +      "additionalProperties": true,
      +      "description": "Which inputs were available; a score without liquidity or holder data is weaker and says so.",
      +      "type": "object"
      +    },
      +    "fusion": {
      +      "additionalProperties": true,
      +      "description": "Cross-signal wallet correlation; wallets list is empty on non-Pro keys.",
      +      "type": "object"
      +    },
      +    "poweredBy": {
      +      "description": "Always \"DeFade.org\".",
      +      "type": "string"
      +    },
      +    "proChecksLocked": {
      +      "description": "How many Pro-only checks were withheld.",
      +      "type": "number"
      +    },
      +    "rugScore": {
      +      "description": "Rug probability 0 (safe) to 100 (critical). HIGHER IS MORE DANGEROUS.",
      +      "type": "number"
      +    },
      +    "signals": {
      +      "description": "Each contributing signal: what fired, its weight and its explanation.",
      +      "type": "array"
      +    },
      +    "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)."
      +    },
      +    "verdict": {
      +      "description": "PROBABLY SAFE (<25), SOME RISK (25+), ELEVATED RISK (45+), HIGH RISK (60+), EXTREME RISK (75+), or RUGGED.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  14. Changed2 schema fields changed
    • 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."
  15. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses cost ("five API units on Solana and on an EVM chain"), a pre-call caution ("check get_usage before scoring many tokens"), and a partial-result state ("When complete is false the score is partial: say so, and call again for the rest"). It also explains why the cost exists — the score reads the scan's modules first — which is exactly the kind of context annotations cannot convey.

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-loads the most decision-relevant fact — higher means more dangerous — before routing and cost notes. It is dense and multi-clause, with some run-on sentences (the usage sentence is long), but nearly every clause carries operational information about direction, cost, or alternatives.

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 the description needn't enumerate return fields, yet it still explains the non-obvious semantics of the returned score (direction, verdict, partiality). Combined with cost, chain handling, and sibling routing, nothing an agent needs to call this correctly 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 description coverage is 100%, so address and chain are already fully documented, including the 0x/EVM rule and address formats. The description only restates the two argument names and notes the chain requirement for EVM scoring, adding little beyond what the schema says; baseline 3 applies when the schema carries the detail.

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 resource and output ("Rug pull probability for one token: a 0-100 score... a verdict label, and the individual signals") and immediately disambiguates direction against a named sibling: "This is the opposite direction from get_token_scan's safety score." An agent can distinguish this from get_token_scan without opening either 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 call condition ("after get_token_scan, for every 'is this safe', 'is this a rug' or 'should I buy' question, on every chain") plus a caveat that on EVM chains get_token_scan carries no score. It also states when NOT to use it, routing to get_wallet_links, get_dev_tracker and get_launch_bundles for wallet-level evidence.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources