dexscreener_get_tokens_by_chain_and_addresses
Get Dexscreener-indexed pairs for up to 30 token addresses on the same chain, in one request. Hits `GET /tokens/v1/{chainId}/{tokenAddresses}` (addresses joined with `,`). Returns `{ schemaVersion, pairs: Pair[] }` — the array contains the union of every pair the addresses share, so a token that has multiple pairs will contribute several rows. Use this to fan out a portfolio or a watchlist of tokens in a single round-trip. For a single token, prefer `dexscreener_get_pairs_by_chain_and_address`; for a chain-agnostic lookup, use `dexscreener_get_token_pairs`.
Get Dexscreener-indexed pairs for up to 30 token addresses on the same chain, in one request. Hits GET /tokens/v1/{chainId}/{tokenAddresses} (addresses joined with ,).
Endpoint
GET /tokens/v1/{chainId}/{tokenAddresses}
Input
The tool takes a single JSON object. Every field, its type, and an example are on the generated reference at GET /mcp/tools, under this tool's name.
Calling it
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": { "name": "dexscreener_get_tokens_by_chain_and_addresses", "arguments": {} }
}Put your arguments in place of the empty object. A call that fails comes back as a normal result carrying isError: true and a message naming what went wrong, not as a JSON-RPC protocol error.
Notes
Returns { schemaVersion, pairs: Pair[] } — the array contains the union of every pair the addresses share, so a token that has multiple pairs will contribute several rows. Use this to fan out a portfolio or a watchlist of tokens in a single round-trip. For a single token, prefer dexscreener_get_pairs_by_chain_and_address; for a chain-agnostic lookup, use dexscreener_get_token_pairs.
The full request and response shape, and a live playground, live on the generated reference at GET /mcp/tools.
dexscreener_get_pairs_by_chain_and_address
Get every Dexscreener-indexed liquidity pair for a token, restricted to a single chain. Hits `GET /token-pairs/v1/{chainId}/{tokenAddress}`. Returns `{ schemaVersion, pairs: Pair[] }`. Use this when the chain is known — it is faster and cheaper than `dexscreener_get_token_pairs`, which scans every chain Dexscreener indexes. For a chain-agnostic lookup, use `dexscreener_get_token_pairs`; for a batch of up to 30 tokens on the same chain, use `dexscreener_get_tokens_by_chain_and_addresses`.
dexscreener_get_pair_by_address
Get a single Dexscreener-indexed pair by `chainId` + `pairId`. Hits `GET /latest/dex/pairs/{chainId}/{pairId}`. Returns `{ schemaVersion, pairs: Pair[] }` — the array has exactly one element on a hit, and is empty (not 404) on an unknown pair. Use this to re-fetch the live price, liquidity, volume, and 24h change for a known pair without re-running a search.