Nansen

Tracking token transfers

token_transfers

Get 25 token transfers (per page) for a specific token based on the sort order. Default is most recent transfers first.

NOTE: This tool does not support native tokens (so11111111111111111111111111111111111111112, 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee).

Columns returned:

Time: Timestamp when the transfer occurred (block_timestamp: ISO 8601 format)
From Label: Source address label (from_address_label: sender of tokens)
To Label: Destination address label (to_address_label: receiver of tokens)
From Address: Raw source address (from_address: hex address)
To Address: Raw destination address (to_address: hex address)
Amount: Quantity of tokens transferred (transfer_amount: numeric)
Value USD: USD value of the transfer at time of transaction (transfer_value_usd: currency formatted)
Type: Transfer category (transaction_type: DEX, CEX, transfer, etc.)
Tx Hash: Blockchain transaction hash for verification (transaction_hash)

Sorting Options (all fields support "asc"/"desc"): Available for sorting: timestamp, amount

Examples: # Basic request (most recent transfers first) { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "24H_AGO", "to": "NOW"}, "orderBy": "timestamp", "order_by_direction": "desc" }

# Smart money only filter (largest transfers first)
```
{
  "chain": "ethereum",
  "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab",
  "dateRange": {"from": "7D_AGO", "to": "NOW"},
  "transferOriginCategories": ["all_transfers"],
  "onlySmartTradersAndFunds": true,
  "orderBy": "amount",
  "order_by_direction": "desc"
}
```

# Filter by DEX only with minimum transfer value (USD)
```
{
  "chain": "ethereum",
  "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab",
  "dateRange": {"from": "24H_AGO", "to": "NOW"},
  "transferOriginCategories": ["dex"],
  "transferValueUsd": {"from": 1000}
}
```

# Filter transfers sent FROM a specific wallet
```
{
  "chain": "base",
  "tokenAddress": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
  "dateRange": {"from": "2025-03-12", "to": "2025-03-12"},
  "fromAddress": "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72",
  "orderBy": "timestamp",
  "order_by_direction": "desc"
}
```

Available Filters:

Address Filters:

fromAddress (str or list[str], optional): Filter by sender address(es) Example: "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72" Example: ["0xaddr1", "0xaddr2"]
toAddress (str or list[str], optional): Filter by recipient address(es) Use fromAddress/toAddress when looking for a specific wallet's transfers.

Transfer Origin Categories:

transferOriginCategories (list[str]): List of transfer types to include Possible values: ['dex', 'cex', 'non_exchange_transfers', 'all_transfers'] Default: ['all_transfers'] Examples:
- ['dex'] - only DEX transfers
- ['cex'] - only CEX transfers
- ['dex', 'cex'] - both DEX and CEX
- ['non_exchange_transfers'] - only non-exchange transfers
- ['all_transfers'] - all types (default)

Smart Money Filter:

onlySmartTradersAndFunds (bool): Only show smart money transfers (default: false) When true, filters to show only transfers involving profitable addresses

Numeric Range Filter:

transferValueUsd (object, optional): Filter by USD value of transfer Format: {"from": X, "to": Y} or {"from": X} or {"to": Y}
- Specify only from for minimum bound (no maximum)
- Specify only to for maximum bound (no minimum)
- Specify both for a bounded range Example: {"from": 1000} - only transfers worth at least $1,000 USD Example: {"to": 50000} - only transfers up to $50,000 USD Example: {"from": 1000, "to": 50000} - transfers between $1,000 and $50,000 USD Note: This filters by the USD value of the transfer at time of transaction

Notes: - Use fromAddress/toAddress to find transfers for a specific wallet - Use transferOriginCategories to control which transfer origins are included - Smart Money filter shows only transfers involving profitable addresses (definition of Smart Money) - transferValueUsd filters by USD value at time of transaction

Input Schema

TableJSON Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It explicitly states the page size (25), default sort order, lack of native token support, and clarifies nuanced behaviors (e.g., smart money filter means 'only transfers involving profitable addresses'; transferValueUsd filters by USD value at time of transaction). It also lists return columns, giving insight into output. However, it does not mention rate limits, error conditions, or how to advance pages via the 'page' parameter, which would be additional useful behavioral context.

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?

The description is long but extremely well-structured: a concise opening statement, a note on unsupported tokens, a clear columns list, sorting options, multiple example code blocks, and a structured list of filters. Every section adds practical value, and the use of headers, bold text, and code blocks makes it easy to scan. It is not redundant, though the length is justified by the tool's complexity. It is therefore concise in structure, not in word count, which earns a 4.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with many filters and an output schema, the description is highly complete: it covers purpose, return columns, sorting, all filters with examples, and a key limitation (native tokens). It also provides practical usage tips. The only notable gap is that pagination beyond the first page is not explained (the 'page' parameter appears in the schema but not in the description), and there is no mention of error handling or edge cases like empty results. Given the overall thoroughness, this is a strong 4.

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?

The top-level schema parameter ('request') has no description, resulting in a schema description coverage of 0%. The tool description fully compensates by explaining all available filters in detail: fromAddress, toAddress, transferOriginCategories, onlySmartTradersAndFunds, transferValueUsd, and sorting options. It provides formats, possible values, defaults, and examples for each, adding substantial meaning beyond the raw schema. This is exemplary compensation for sparse schema 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 starts with a clear, specific statement: 'Get 25 token transfers (per page) for a specific token based on the sort order.' It names the resource (token transfers), the verb (get), pagination (25 per page), and sorting, which distinguishes it from sibling tools like token_dex_trades or token_flows. The scope is explicit (for a specific token), and the unsupported native token note further refines the tool's purpose.

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 usage context, including when to use filters (e.g., 'Use fromAddress/toAddress when looking for a specific wallet's transfers') and what each filter controls. It also gives multiple examples covering different use cases (basic, smart money, DEX filter, from-address filter). However, it does not explicitly compare to sibling tools or state when not to use this tool, so it stops short of the explicit alternative guidance needed for a 5.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation5/5

Each tool has a clearly defined purpose, and overlapping tools (e.g., token_flows vs token_recent_flows_summary, nansen_score_top_tokens vs token_discovery_screener) include explicit guidance on when to use them. Even with similar names like prediction_market_trades and prediction_market_address_trades, the descriptions and parameters make the distinction unambiguous.

Naming Consistency4/5

Most tools follow a domain_prefix_noun pattern (address_, token_, prediction_market_), making them predictable within families. However, outliers like general_search, growth_chain_rank, hyperliquid_leaderboard, and transaction_lookup break the pattern, and some names are long or inconsistently formatted (e.g., smart_traders_and_funds_perp_trades vs smart_traders_and_funds_token_balances).

Tool Count3/5

With 38 tools, the server is far above the typical 3-15 range, making it heavy for agents to navigate. However, Nansen is a broad analytics platform covering wallets, tokens, prediction markets, and smart money activity, so the high count is justifiable as each tool serves a distinct function.

Completeness5/5

The tool set provides comprehensive coverage across token analysis (ohlcv, trading, holders, flows, PnL, technicals), wallet analysis (portfolio, transactions, counterparties), prediction markets (lookup, orderbook, trades, PnL), and discovery. The only obvious omission is NFT support, but it is explicitly documented as out of scope, so no critical dead ends exist.

Resources

Need Help?