Dexscreener
NPM · @PIPEWORX/MCP-DEXSCREENER · 2 COMPONENTS
DEX Screener MCP — DEX price/liquidity/volume data
Available components
Last scanned (6 hours ago)
Scores higher than 76% of npm servers
Category Crypto and Web3
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-dexscreener). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 725 tokens (~103/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 85% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 1 Nov 26 +1
- 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. security
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-dexscreener@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-dexscreener |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-dexscreener/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3617508940 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a1b48517f1c35bf4096cfa35b49d40ce3544ab51fc1d2a2d057ea9acf67bd2bf2657022a75903f4ad1036ba703199784799c52f1de7108796e07e1922 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
dexscreener_screener ~379
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
get_pair ~74
Pair detail (price USD/native, liquidity, 24h volume, 5m/1h/6h/24h tx counts).
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain id — ethereum | solana | bsc | polygon | arbitrum | base | … |
| pair_address | string | yes | Pair / pool address |
No output schema declared.
No examples provided.
get_token ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain id |
| token_address | string | yes | Token contract address |
No output schema declared.
No examples provided.
latest_boosted_tokens ~21
Tokens being actively promoted on DEX Screener.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
latest_token_profiles ~18
Newest token profiles created (cross-chain).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_pairs ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
token_boosts_top ~46
Most-boosted tokens, optionally filtered to a chain / token.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| token | string | – | Token address (chain required if passed) |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-dexscreener
claude mcp add pipeworx-io-dexscreener -- npx -y @pipeworx/mcp-dexscreener
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.