# Dexscreener (npm · @pipeworx/mcp-dexscreener)

DEX Screener MCP — DEX price/liquidity/volume data

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-dexscreener/dexscreener-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-dexscreener/dexscreener-mcp)
- npm · `@pipeworx/mcp-dexscreener`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-dexscreener/pipeworx-mcp-dexscreener.md), [page](https://verifymcp.io/servers/pipeworx-io-dexscreener/pipeworx-mcp-dexscreener)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-dexscreener`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-dexscreener).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 725 tokens (~103/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 85% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Dexscreener MCP server?

Dexscreener runs locally as an npm package, launched with npx -y @pipeworx/mcp-dexscreener. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-dexscreener -- npx -y @pipeworx/mcp-dexscreener
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-dexscreener -- npx -y @pipeworx/mcp-dexscreener
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-dexscreener": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-dexscreener"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-dexscreener --command npx --arg -y --arg @pipeworx/mcp-dexscreener
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-dexscreener:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-dexscreener"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-dexscreener": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-dexscreener"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-dexscreener -t stdio -c npx -a -y @pipeworx/mcp-dexscreener
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 81, +1)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 80, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (7)

### `get_pair` (~74 tokens)

Pair detail (price USD/native, liquidity, 24h volume, 5m/1h/6h/24h tx counts).

Input parameters:

- `chain` (string, required): Chain id — ethereum | solana | bsc | polygon | arbitrum | base | …
- `pair_address` (string, required): Pair / pool address

### `get_token` (~69 tokens)

All trading pairs for a token address on one chain. If calling by bare name is ambiguous (collides with blockscout_get_token), call this as `dexscreener_get_token` instead.

Input parameters:

- `chain` (string, required): Chain id
- `token_address` (string, required): Token contract address

### `search_pairs` (~61 tokens)

Free-text search across all DEX Screener chains for trading pairs matching a token name, symbol, or address. Returns up to 30 pairs with price USD, liquidity, 24h volume, and chain/DEX info.

Input parameters:

- `query` (string, required)

### `latest_token_profiles` (~18 tokens)

Newest token profiles created (cross-chain).

### `latest_boosted_tokens` (~21 tokens)

Tokens being actively promoted on DEX Screener.

### `token_boosts_top` (~46 tokens)

Most-boosted tokens, optionally filtered to a chain / token.

Input parameters:

- `chain` (string)
- `token` (string): Token address (chain required if passed)

### `dexscreener_screener` (~379 tokens)

A filterable screen for new/trending tokens on one chain (default solana), by liquidity, volume and market cap — composes DEX Screener's promoted-token lists (latest_token_profiles + latest_boosted_tokens, which is what DEX Screener itself surfaces as "new/trending") with per-token pool detail (same data as get_token) to filter and rank. Answers 'trending solana memecoins with liquidity over $1000 and market cap under $1M', 'new solana pairs with high volume', 'recent tokens on solana above a liquidity floor'. NOT DEX Screener's full new-pair firehose (their public API has no such endpoint) — it screens the tokens currently being promoted/profiled on DEX Screener, which is the same 'new/trending' surface a human sees on their homepage. Each matching pool includes price, liquidity USD, 24h volume, market cap/FDV, and when the pool was created. Checks up to 30 candidate tokens per call.

Input parameters:

- `chain` (string): Chain id, default "solana". Any DEX Screener chain id works (ethereum, bsc, base, …).
- `limit` (number): Max pools to return, 1-50 (default 20).
- `max_market_cap_usd` (number): Maximum market cap / FDV in USD. Default: no ceiling.
- `min_liquidity_usd` (number): Minimum pool liquidity in USD. Default 0 (no floor).
- `min_volume_24h_usd` (number): 24h volume floor in USD. Default 0 (no floor).
- `sort` (string): Sort by 24h volume (default), pool liquidity, or pool creation time (newest first).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-dexscreener/pipeworx-mcp-dexscreener#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the Dexscreener MCP server?

Dexscreener is an MCP server listed in the public MCP registry as io.github.pipeworx-io/dexscreener. DEX Screener MCP, DEX price/liquidity/volume data. This page covers its npm package (@pipeworx/mcp-dexscreener).

### Is the Dexscreener MCP server safe to use?

Dexscreener scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Dexscreener MCP server expose?

Dexscreener exposes 7 tools: get_pair, get_token, search_pairs, latest_token_profiles, latest_boosted_tokens, and 2 more. Their descriptions and schemas cost roughly 668 tokens of context every time the server is loaded.

### Is the Dexscreener MCP server still maintained?

Dexscreener is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Dexscreener MCP server under?

Dexscreener declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-dexscreener
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-dexscreener
- Repository: https://github.com/pipeworx-io/mcp-dexscreener
- Website: https://pipeworx.io/packs/dexscreener
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-dexscreener/pipeworx-mcp-dexscreener.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-dexscreener/pipeworx-mcp-dexscreener.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-dexscreener/pipeworx-mcp-dexscreener