MAD Synapse

Token risk score

token_risk

Read-onlyIdempotent

0-100 rug-risk score for any Solana token: mint/freeze authority, Token-2022 traps, holder concentration, liquidity depth — plus pump.fun curve flags. Contract state is read live from Solana (authorities, Token-2022 extensions such as transfer fees, hooks, permanent delegate, pausable), holders from the largest accounts, market from DexScreener. For pump.fun mints the curve forensics flags are merged in. When to use: For any Solana token, pump.fun or not. For pump.fun curve-stage detail use pump_token (callable here by name); for EVM tokens use evm_token_security (callable here by name). Price: $0.005 per call (10 free/day; after that a payment-required result lists x402 options). Errors: returns isError with a message for invalid input or an upstream failure (not charged).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mint`	Yes	token mint. Base58 Solana address, 32-44 chars.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`dex`	No
`mint`	No
`name`	No
`flags`	No
`found`	No
`grade`	No
`score`	No
`symbol`	No
`fdv_usd`	No
`onchain`	No
`pair_url`	No
`swap_url`	No
`txns_24h`	No
`price_usd`	No
`disclaimer`	No
`known_asset`	No
`solana_pairs`	No
`generated_utc`	No
`liquidity_usd`	No
`onchain_error`	No
`pair_age_hours`	No
`volume_24h_usd`	No
`liquidity_total_usd`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 27, 2026

changedInput schema / properties / mint / description

Previous value: -"token mint"New value: +"token mint. Base58 Solana address, 32-44 chars."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "dex": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "disclaimer": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "fdv_usd": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "flags": {
+      "items": {
+        "properties": {
+          "msg": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "severity": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "type": "array"
+    },
+    "found": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "generated_utc": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "grade": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "known_asset": {
+      "properties": {
+        "kind": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "symbol": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "liquidity_total_usd": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "liquidity_usd": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "mint": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "onchain": {
+      "properties": {
+        "decimals": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "freeze_authority": {},
+        "holders": {},
+        "metadata_mutable": {
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "mint_authority": {},
+        "program": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "pump_fun": {},
+        "supply": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "token2022_extensions": {
+          "type": "array"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "onchain_error": {},
+    "pair_age_hours": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "pair_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price_usd": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "score": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "solana_pairs": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "swap_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "symbol": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "txns_24h": {
+      "properties": {
+        "buys": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "sells": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "volume_24h_usd": {
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 25, 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/non-destructive annotations by disclosing data provenance (live Solana contract state, largest-account holders, DexScreener market), pricing ($0.005/call, 10 free/day, x402 options on payment-required), and error semantics (isError for invalid input or upstream failure, not charged). This is exactly the extra context 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?

Front-loads the score and its inputs, then usage, then pricing/errors in a logical order. It is longer than most definitions, but nearly every clause carries distinct information; only the enumeration of Token-2022 extensions is slightly padded.

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?

Output schema exists so return values need not be described, and the description covers data sources, pump.fun merging, sibling routing, cost, and error behavior. An agent has everything needed to select and invoke 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 coverage is 100% and the single mint parameter is fully documented in the schema (Base58, 32-44 chars, pattern). The description adds no syntax or format detail beyond that, so the baseline 3 for a schema-documented parameter is appropriate.

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 (0-100 rug-risk score) and enumerates the exact risk dimensions scored: mint/freeze authority, Token-2022 traps, holder concentration, liquidity depth, pump.fun curve flags. It explicitly distinguishes itself from siblings pump_token and evm_token_security, so an agent can route 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 'When to use' clause covering any Solana token (pump.fun or not), names pump_token for curve-stage detail and evm_token_security for EVM, and even notes those siblings are callable by name. Both the selection condition and the alternatives are spelled out.

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

All MAD Synapse 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?