Solana Wallet Intel

token_trending

Read-onlyIdempotent

Use this before you buy, swap, or recommend a Solana memecoin: trending tokens with a rug-check on each one. Every token gets a riskScore (0 to 100), a riskLevel, and a one-line verdict backed by top-10 holder share, mint and freeze authority, LP lock, and sniper or bundle share of early supply, plus liquidity, market cap, 5m/1h/24h price and volume, and pump.fun status. Unreadable checks are marked unknown, never called safe. $0.005 USDC, free preview at /token/trending/preview. The list includes liquidity, market cap, pair age, 5m/1h/24h price and volume, buy/sell ratio, pump.fun bonding or graduation, and links to pump.fun, DexScreener, and Solscan. Each token has a one-line verdict, riskScore (0 clean to 100), riskLevel (low, medium, high, or unknown), and a risk breakdown with evidence and confidence: top-10 share, mint and freeze authority, LP lock percent, and sniper or bundle share of early supply. riskLevel is unknown when the holder, authority, LP, and sniper checks are all unread, and maxRisk leaves those tokens out. Holder percent falls back to the public RugCheck report at medium confidence when the public RPC cannot list the largest accounts. A successful RPC holder read is kept. Holder-concentration change over 5m/1h/24h is filled when this process has seen the mint before. A check that cannot be read says so, uses low confidence, and is not flagged. On-chain safety flags are plain-English sentences that fire when the top 10 holders own 50% or more, mint or freeze authority is still active, LP is unlocked, or snipers and bundled wallets took 20% or more of early supply. Market flags are short codes: low_liquidity, thin_volume, newly_launched, extreme_move, wash_suspect, paid_boost. Thin, new, and wash-like books are ranked down. The summary block counts tokens by risk level and names the top movers. limit is an integer from 1 to 25 and defaults to 15. minLiquidity is an optional USD floor. maxRisk is low, medium, high, or an integer from 0 to 100. Costs $0.005 USDC (5000 base units) via x402. The same price is charged for HTTP GET /token/trending. An unpaid HTTP call returns 402 even when the query is missing or invalid. A signed call with invalid arguments is rejected before settlement and is not charged. A successful result can set cached, stale, and cacheAgeMs. stale true means a previous result was served while a refresh runs or the upstream failed. You are charged only when the tool result is not an error.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "token_trending"
  }
}

Input Schema

Name	Required	Description
`limit`	No	How many tokens to return. Integer from 1 to 25, or a numeric string. Default 15.
`maxRisk`	No	Optional maximum risk. low, medium, high, or an integer from 0 to 100.
`minLiquidity`	No	Optional minimum pool liquidity in USD. Tokens with unknown liquidity are left out.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

addedInput schema / properties / maxRisk

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "low",
+        "medium",
+        "high"
+      ],
+      "type": "string"
+    },
+    {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "string"
+    }
+  ],
+  "description": "Optional maximum risk. low, medium, high, or an integer from 0 to 100."
+}

addedInput schema / properties / minLiquidity

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 1000000000000,
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "pattern": "^\\d+(\\.\\d+)?$",
+      "type": "string"
+    }
+  ],
+  "description": "Optional minimum pool liquidity in USD. Tokens with unknown liquidity are left out."
+}

Changed3 schema fields changedOct 24, 2026

addedInput schema / properties / limit / anyOf

Added value: +[
+  {
+    "maximum": 25,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "pattern": "^\\d+$",
+    "type": "string"
+  }
+]

changedInput schema / properties / limit / description

Previous value: -"1 to 25, default 15"New value: +"How many tokens to return. Integer from 1 to 25, or a numeric string. Default 15."

removedInput schema / properties / limit / type
```
Removed value: -"string"
```

Changed3 schema fields changedOct 23, 2026
- removedInput schema / properties / limit / maximum
```
Removed value: -25
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"string"
```
First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses payment mechanics ($0.005 USDC via x402), the 402 behavior for unpaid calls, that invalid signed calls are rejected before settlement and not charged, cached/stale/cacheAgeMs semantics, and the 'unknown is never called safe' policy. These are exactly the operational details an agent cannot infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The usage hook is front-loaded, but the middle is heavily redundant — riskScore/riskLevel/verdict, liquidity, market cap, and 5m/1h/24h price and volume are each listed two or three times. Several sentences restate earlier ones verbatim in substance, so the definition is roughly twice the length it needs to be.

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?

For a complex read tool with no output schema, the description covers return fields, risk flag codes (low_liquidity, wash_suspect, etc.), fallback behavior when the public RPC fails, confidence levels, the summary block, and billing edge cases. An agent has everything needed to call it and interpret results.

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 the baseline is 3, but the description adds meaning: limit defaults to 15, minLiquidity is a USD floor, and crucially 'maxRisk leaves those tokens out' (unknown-risk exclusion) and that unknown-liquidity tokens are dropped. That is genuine value beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause states a specific verb and resource — trending Solana memecoins, each with a rug-check — and the phrase 'Use this before you buy, swap, or recommend' frames the resource unambiguously. It does not explicitly name a sibling (pretrade, token_check_demo) to contrast against, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use this before you buy, swap, or recommend a Solana memecoin' gives a clear triggering context, and the pricing/preview note tells the agent a free preview path exists. No explicit when-not-to-use or named alternative among the sibling tools is given, so it falls short of 5.

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

All Solana Wallet Intel 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?