# Dexscreener [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/pipeworx-io/mcp-dexscreener  
**GitHub Stars:** 1  
**npm Downloads (last month):** 625  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/dexscreener

## Description
DEX Screener MCP — DEX price/liquidity/volume data

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "dexscreener": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-dexscreener"]
  }
}
```

## Documentation

## What Dexscreener does

The Dexscreener MCP server gives MCP-compatible agents access to DEX Screener data across major EVM networks and Solana. It is intended for queries about decentralized-exchange markets, including current pair prices, liquidity, trading volume, and transaction activity.

The server provides six domain tools:

- `get_pair` returns details for one chain and pair address.
- `get_token` returns all indexed pairs for a token on one chain.
- `search_pairs` searches pairs by free-text query and returns up to 30 results.
- `latest_token_profiles` lists newly added token profiles.
- `latest_boosted_tokens` lists tokens currently promoted on DEX Screener.
- `token_boosts_top` returns the top boosted-token leaderboard, with optional chain and token filtering.

Supported chain identifiers include `ethereum`, `solana`, `bsc`, `polygon`, `arbitrum`, `base`, `avalanche`, `optimism`, and `fantom`.

## How it works

The server reads JSON from `https://api.dexscreener.com/`. Requests are mapped to DEX Screener routes for pair details, token pairs, searches, profiles, and boost data. The upstream API allows roughly 300 requests per minute per IP.

An empty result is a valid response from this data source. For example, the API can return an empty list for profile or boost routes, or a pair response with `pairs: null`, when nothing is indexed. An upstream error is reported separately rather than being treated as proof that a supplied address or chain is invalid.

For `token_boosts_top`, chain and token values are filtered by the server after retrieving the leaderboard because the upstream route does not accept those filters in its path.

## Setup and configuration

The Dexscreener MCP server can be connected through the hosted Pipeworx gateway or launched as a local npm package. The gateway endpoint is `https://gateway.pipeworx.io/dexscreener/mcp`. A full gateway connection is also available at `https://gateway.pipeworx.io/mcp`.

Gateway connections include the pack tools plus shared Pipeworx tools such as discovery, search, memory, and cross-catalog question routing. The exact tool set is reported by the MCP `initialize` response.

For local execution, configure an MCP client to run `npx -y @pipeworx/mcp-dexscreener`. This uses MCP over stdin and stdout, requires no Pipeworx account, and exposes only the Dexscreener pack tools. No environment variables are documented as required.

The tools can also be called over HTTP through the Pipeworx tool endpoints, including `POST /v1/tools/dexscreener_get_pair` with a JSON request body.

## Limitations and notes

The server depends on DEX Screener indexing. An unknown address does not necessarily produce a 404; empty data can be returned with HTTP 200. Consumers should distinguish `not_found` results from `upstream_down` errors and avoid treating an upstream failure as evidence that their arguments are wrong.

The gateway pack endpoint adds shared tools that are not part of the local package. Use the standalone mode when a client should see only the six DEX Screener tools, or use the gateway when cross-catalog routing is useful. The project is licensed under MIT.

_Full upstream README: https://allmcps.com/mcp/dexscreener/readme_