Log inSubmit server
Dexscreener logo

Dexscreener

Fetches DEX prices, liquidity, volume, pair, token, profile, and boost data across EVM and Solana chains.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Dexscreener

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "dexscreener": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-dexscreener"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Dexscreener MCP server exposes real-time DEX Screener market data through MCP tools for EVM and Solana chains. It retrieves pair details, token pairs, searches, token profiles, and boost rankings without authentication, using the DEX Screener JSON API. Connect through the Pipeworx gateway or run the package locally over stdio when agents need decentralized-exchange data.

Use cases

  • Inspect liquidity and volume for a DEX pair
  • Find indexed pairs for a token address
  • Search DEX Screener pairs by name or symbol
  • Review newly listed token profiles
  • Compare token boost rankings

Key features

  • Pair price, liquidity, volume, and transaction data
  • All indexed token pairs on a selected chain
  • Free-text pair search with up to 30 results
  • Latest token profile and boosted-token feeds
  • Top boost leaderboard with client-side filters
  • Gateway, HTTP, and local stdio access

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

6/6 checks healthy over the last 35d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 1h ago via OSV.dev · @pipeworx/mcp-dexscreener (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads625Package downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.

How Dexscreener works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Dexscreener

Dexscreener is an MCP server that connects AI agents to the DEX Screener JSON API for real-time decentralized-exchange market data. Its main tools retrieve pair details, token pairs, pair searches, latest token profiles, latest boosted tokens, and top token boosts across supported EVM and Solana chains.

Run `npx -y @pipeworx/mcp-dexscreener` as a local stdio MCP server, or configure an MCP client with that command and package. You can alternatively connect to the hosted gateway endpoint at `https://gateway.pipeworx.io/dexscreener/mcp`.

No, the provided setup does not require authentication or an API key. The server reads data from the DEX Screener API, which has an approximate limit of 300 requests per minute per IP.

Yes, Cursor is named as a supported MCP client in the setup instructions. Add the hosted gateway URL to Cursor, or configure it to launch the local npm package over stdio.

An empty result can mean that DEX Screener has nothing indexed for the request, not that the address is invalid. Upstream errors are reported separately as `upstream_down`, while an actual empty response is treated as `not_found`.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDexscreener AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/dexscreener?style=directory)](https://allmcps.com/mcp/dexscreener)
HTML Embed
<a href="https://allmcps.com/mcp/dexscreener"><img src="https://allmcps.com/api/badge/dexscreener?style=directory" alt="Dexscreener on AllMCPs" /></a>