Nansen

Loading token info

token_info

Read-only

Get token information — spot on-chain details or Hyperliquid perpetual futures stats.

On-chain tokens mode (default): Returns token details (name, symbol, market cap, FDV, supply, deployment date, socials) and spot trading metrics (volume, buys/sells, buyers/sellers, holders, liquidity).

Perps mode: Returns Hyperliquid perp stats — mark price, funding, open interest, buy/sell pressure, trader participation.

Returns: Token information as markdown.

On-chain tokens fields:
- **Market Cap / FDV**: Market capitalization and fully diluted valuation
- **Circulating / Total Supply**: Token supply metrics
- **Deployed**: When the token was deployed
- **Volume (Total / Buy / Sell)**: Trading volume in USD
- **Buys / Sells**: Number of buy/sell transactions
- **Unique Buyers / Sellers**: Distinct trading addresses
- **Total Holders**: Number of token holders
- **Liquidity**: Available liquidity in USD

Perps fields:
- **Mark Price**: Current perp mark price
- **Price Change**: Change vs previous price
- **Max Leverage**: Maximum leverage offered for the perp on Hyperliquid (e.g. "40x")
- **Funding Rate (hourly/annualized)**: Current funding rate
- **Open Interest**: Total current open interest in USD
- **Volume (Total / Buy / Sell)**: Perp volume in USD
- **Net Flow (Buy - Sell)**: Buy/sell pressure in USD
- **Traders**: Number of traders

Example: On-chain tokens (default mode): { "mode": "onchain_tokens", "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "timeframe": "1d" }

Hyperliquid perps:
```
{
  "mode": "perps",
  "tokenAddress": "BTC",
  "timeframe": "7d"
}
```

Notes: - On-chain tokens mode uses contract addresses - Perps mode uses token symbols (e.g. BTC, ETH, HYPE) - Both modes use the same timeframe parameter

Input Schema

TableJSON Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 16, 2026

changedInput schema / properties / request / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "description": "Request for token info — spot (on-chain token details) or perps (Hyperliquid stats).",
-    "properties": {
-      "chain": {
-        "default": "ethereum",
-        "description": "Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, mantra, monad, near, optimism, plasma, polygon, robinhood, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync",
-        "type": "string"
-      },
-      "mode": {
-        "default": "onchain_tokens",
-        "description": "Analysis mode: 'onchain_tokens' for on-chain token information, 'perps' for Hyperliquid perpetual futures stats by symbol. If mode is omitted and token_address is a symbol (not a contract address), mode defaults to 'perps'.",
-        "enum": [
-          "onchain_tokens",
-          "perps"
-        ],
-        "type": "string"
-      },
-      "timeframe": {
-        "default": "1d",
-        "description": "Timeframe for token metrics (5m, 1h, 6h, 12h, 1d, 7d)",
-        "enum": [
-          "5m",
-          "1h",
-          "6h",
-          "12h",
-          "1d",
-          "7d"
-        ],
-        "type": "string"
-      },
-      "tokenAddress": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "tokenAddress"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Request for token info — spot (on-chain token details) or perps (Hyperliquid stats).",
+    "properties": {
+      "chain": {
+        "default": "ethereum",
+        "description": "Blockchain network. Supported: arbitrum, arc, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, mantra, monad, near, optimism, plasma, polygon, robinhood, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync",
+        "type": "string"
+      },
+      "mode": {
+        "default": "onchain_tokens",
+        "description": "Analysis mode: 'onchain_tokens' for on-chain token information, 'perps' for Hyperliquid perpetual futures stats by symbol. If mode is omitted and token_address is a symbol (not a contract address), mode defaults to 'perps'.",
+        "enum": [
+          "onchain_tokens",
+          "perps"
+        ],
+        "type": "string"
+      },
+      "timeframe": {
+        "default": "1d",
+        "description": "Timeframe for token metrics (5m, 1h, 6h, 12h, 1d, 7d)",
+        "enum": [
+          "5m",
+          "1h",
+          "6h",
+          "12h",
+          "1d",
+          "7d"
+        ],
+        "type": "string"
+      },
+      "tokenAddress": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "tokenAddress"
+    ],
+    "type": "object"
+  }
+]

Changed1 schema field changedJul 18, 2026

changedInput schema / properties / request / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "description": "Request for token info — spot (on-chain token details) or perps (Hyperliquid stats).",
-    "properties": {
-      "chain": {
-        "default": "ethereum",
-        "description": "Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, mantra, monad, near, optimism, plasma, polygon, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync",
-        "type": "string"
-      },
-      "mode": {
-        "default": "onchain_tokens",
-        "description": "Analysis mode: 'onchain_tokens' for on-chain token information, 'perps' for Hyperliquid perpetual futures stats by symbol. If mode is omitted and token_address is a symbol (not a contract address), mode defaults to 'perps'.",
-        "enum": [
-          "onchain_tokens",
-          "perps"
-        ],
-        "type": "string"
-      },
-      "timeframe": {
-        "default": "1d",
-        "description": "Timeframe for token metrics (5m, 1h, 6h, 12h, 1d, 7d)",
-        "enum": [
-          "5m",
-          "1h",
-          "6h",
-          "12h",
-          "1d",
-          "7d"
-        ],
-        "type": "string"
-      },
-      "tokenAddress": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "tokenAddress"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Request for token info — spot (on-chain token details) or perps (Hyperliquid stats).",
+    "properties": {
+      "chain": {
+        "default": "ethereum",
+        "description": "Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, mantra, monad, near, optimism, plasma, polygon, robinhood, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync",
+        "type": "string"
+      },
+      "mode": {
+        "default": "onchain_tokens",
+        "description": "Analysis mode: 'onchain_tokens' for on-chain token information, 'perps' for Hyperliquid perpetual futures stats by symbol. If mode is omitted and token_address is a symbol (not a contract address), mode defaults to 'perps'.",
+        "enum": [
+          "onchain_tokens",
+          "perps"
+        ],
+        "type": "string"
+      },
+      "timeframe": {
+        "default": "1d",
+        "description": "Timeframe for token metrics (5m, 1h, 6h, 12h, 1d, 7d)",
+        "enum": [
+          "5m",
+          "1h",
+          "6h",
+          "12h",
+          "1d",
+          "7d"
+        ],
+        "type": "string"
+      },
+      "tokenAddress": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "tokenAddress"
+    ],
+    "type": "object"
+  }
+]

Changed1 schema field changedJun 12, 2026

changedInput schema / properties / request / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "description": "Request for token info — spot (on-chain token details) or perps (Hyperliquid stats).",
-    "properties": {
-      "chain": {
-        "default": "ethereum",
-        "description": "Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, mantra, monad, near, optimism, plasma, polygon, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync",
-        "type": "string"
-      },
-      "mode": {
-        "default": "onchain_tokens",
-        "description": "Analysis mode: 'onchain_tokens' for on-chain token information, 'perps' for Hyperliquid perpetual futures stats by symbol",
-        "enum": [
-          "onchain_tokens",
-          "perps"
-        ],
-        "type": "string"
-      },
-      "timeframe": {
-        "default": "1d",
-        "description": "Timeframe for token metrics (5m, 1h, 6h, 12h, 1d, 7d)",
-        "enum": [
-          "5m",
-          "1h",
-          "6h",
-          "12h",
-          "1d",
-          "7d"
-        ],
-        "type": "string"
-      },
-      "tokenAddress": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "tokenAddress"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Request for token info — spot (on-chain token details) or perps (Hyperliquid stats).",
+    "properties": {
+      "chain": {
+        "default": "ethereum",
+        "description": "Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, mantra, monad, near, optimism, plasma, polygon, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync",
+        "type": "string"
+      },
+      "mode": {
+        "default": "onchain_tokens",
+        "description": "Analysis mode: 'onchain_tokens' for on-chain token information, 'perps' for Hyperliquid perpetual futures stats by symbol. If mode is omitted and token_address is a symbol (not a contract address), mode defaults to 'perps'.",
+        "enum": [
+          "onchain_tokens",
+          "perps"
+        ],
+        "type": "string"
+      },
+      "timeframe": {
+        "default": "1d",
+        "description": "Timeframe for token metrics (5m, 1h, 6h, 12h, 1d, 7d)",
+        "enum": [
+          "5m",
+          "1h",
+          "6h",
+          "12h",
+          "1d",
+          "7d"
+        ],
+        "type": "string"
+      },
+      "tokenAddress": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "tokenAddress"
+    ],
+    "type": "object"
+  }
+]

Changed3 schema fields changedMay 19, 2026

removedInput schema / $defs

Removed value: -{
-  "LookbackPeriod": {
-    "description": "Lookback periods for time-based analysis.",
-    "enum": [
-      "5m",
-      "1h",
-      "6h",
-      "12h",
-      "1d",
-      "7d"
-    ],
-    "type": "string"
-  },
-  "TokenInfoRequest": {
-    "description": "Request for token info — spot (on-chain token details) or perps (Hyperliquid stats).",
-    "properties": {
-      "chain": {
-        "default": "ethereum",
-        "description": "Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, mantra, monad, near, optimism, plasma, polygon, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync",
-        "type": "string"
-      },
-      "mode": {
-        "default": "onchain_tokens",
-        "description": "Analysis mode: 'onchain_tokens' for on-chain token information, 'perps' for Hyperliquid perpetual futures stats by symbol",
-        "enum": [
-          "onchain_tokens",
-          "perps"
-        ],
-        "type": "string"
-      },
-      "timeframe": {
-        "$ref": "#/$defs/LookbackPeriod",
-        "default": "1d",
-        "description": "Timeframe for token metrics (5m, 1h, 6h, 12h, 1d, 7d)"
-      },
-      "tokenAddress": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "tokenAddress"
-    ],
-    "type": "object"
-  }
-}

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / request / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "$ref": "#/$defs/TokenInfoRequest"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Request for token info — spot (on-chain token details) or perps (Hyperliquid stats).",
+    "properties": {
+      "chain": {
+        "default": "ethereum",
+        "description": "Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, mantra, monad, near, optimism, plasma, polygon, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync",
+        "type": "string"
+      },
+      "mode": {
+        "default": "onchain_tokens",
+        "description": "Analysis mode: 'onchain_tokens' for on-chain token information, 'perps' for Hyperliquid perpetual futures stats by symbol",
+        "enum": [
+          "onchain_tokens",
+          "perps"
+        ],
+        "type": "string"
+      },
+      "timeframe": {
+        "default": "1d",
+        "description": "Timeframe for token metrics (5m, 1h, 6h, 12h, 1d, 7d)",
+        "enum": [
+          "5m",
+          "1h",
+          "6h",
+          "12h",
+          "1d",
+          "7d"
+        ],
+        "type": "string"
+      },
+      "tokenAddress": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "tokenAddress"
+    ],
+    "type": "object"
+  }
+]

Changed1 schema field changedMay 13, 2026

changedInput schema / $defs / TokenInfoRequest / properties / chain / description

Previous value: -"Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, monad, near, optimism, plasma, polygon, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync"New value: +"Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, mantra, monad, near, optimism, plasma, polygon, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync"

AddedApr 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds substantial behavioral context: it details the return format (markdown), the two modes with distinct fields, and notes about address vs symbol usage. It also provides example JSON structures, clarifying expected inputs. This goes well beyond the annotations and fully informs the agent of behavior.

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

Conciseness5/5

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

The description is long but well-structured, using headings, bullet lists, and examples. It front-loads the purpose and then systematically details fields, notes, and examples. Each section earns its place; there is no filler or repetition. The structure makes it easy to scan and reference.

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?

The description is complete for a tool of this complexity. It covers both modes, all parameters, the return fields for each mode, and practical notes (address vs symbol, timeframe options). The example JSONs are provided. With the output schema present (as indicated), the description does not need to explain return values further. Nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite the schema coverage being reported as 0%, the description thoroughly explains all parameters. It covers mode (onchain_tokens vs perps), chain (with supported networks), timeframe (with allowed values), and tokenAddress (explaining address vs symbol). The examples clarify the exact format. The description compensates fully for the lack of schema-level parameter documentation.

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 description clearly states the tool's purpose: 'Get token information — spot on-chain details or Hyperliquid perpetual futures stats.' It names the two modes and differentiates them, and the title 'Loading token info' aligns. The description distinguishes this tool from siblings like token_dex_trades or token_ohlcv by focusing on token info rather than specific transactions or price data.

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?

The description provides clear guidance on when to use each mode: on-chain for spot details (contract addresses) and perps for Hyperliquid stats (symbols). It also explains the default mode and the distinction between address vs symbol. However, it does not explicitly mention when to use this tool instead of sibling tools like token_dex_trades or token_ohlcv, so no exclusions or alternatives are stated. This is clear context but lacks explicit 'when-not' guidance for other tools.

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

All Nansen 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?