DexScreener MCP Server

Name: DexScreener MCP Server
Author: openSVM

@openSVM

リポジトリ

DexScreener MCP Server について

概要はまだありません

#dexscreener #api #mcp-server

基本情報

カテゴリ

その他

ライセンス

Unlicense

ランタイム

node

トランスポート

stdio

公開者

openSVM

設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is DexScreener MCP Server?

An MCP server implementation that provides real-time access to DEX pair data, token information, and market statistics across multiple blockchains via the DexScreener API.

How to use DexScreener MCP Server?

Install using the provided one-line script (which automatically adds it to Claude Desktop) or manually via npm install && npm run build && npm run setup. Then invoke the seven available tools (e.g., get_latest_token_profiles, get_pairs_by_token_addresses) through an MCP client.

Key features of DexScreener MCP Server

Rate-limited API access respecting DexScreener’s limits
Comprehensive error handling for various failure modes
Type-safe TypeScript interfaces
Support for all DexScreener API endpoints
Integration tests included
One-line install for Claude Desktop

Use cases of DexScreener MCP Server

Fetch the latest token profiles and boosted tokens for market monitoring
Retrieve DEX pair details by chain and address
Search for trading pairs by query string
Check orders paid for a specific token
Integrate real-time DEX data into AI assistants or analytics pipelines

FAQ from DexScreener MCP Server

What data does DexScreener MCP Server provide?

It provides DEX pair data, token information, market statistics, latest token profiles, boosted tokens, and token order checks across multiple blockchains, all sourced from the DexScreener API.

What are the rate limits for the server?

Token Profile/Boost endpoints are limited to 60 requests per minute; DEX/Pairs endpoints are limited to 300 requests per minute, enforced by the server to comply with DexScreener’s API.

What runtime or dependencies are required?

The server is built with Node.js and TypeScript; dependencies are installed via npm. No API key or authentication is mentioned in the README.

How does error handling work?

Errors from rate limiting, invalid parameters, network failures, or API errors are returned in a standardized format with appropriate error codes and messages.