putty
MCPDexscreenerPairs

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`.

Get every Dexscreener-indexed liquidity pair for a token, restricted to a single chain. Hits GET /token-pairs/v1/{chainId}/{tokenAddress}.

Endpoint

GET /token-pairs/v1/{chainId}/{tokenAddress}

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_pairs_by_chain_and_address", "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[] }. 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.

The full request and response shape, and a live playground, live on the generated reference at GET /mcp/tools.

On this page