DexScreener MCP Server logo

DexScreener MCP Server

by openSVM

An MCP server implementation for accessing the DexScreener API, providing real-time access to DEX pair data, token information, and market statistics across multiple blockchains. It offers a convenient way to retrieve and utilize DexScreener data within your applications.

View on GitHub

Last updated: N/A

What is DexScreener MCP Server?

This server is an MCP (Multi-Chain Protocol) implementation that provides access to the DexScreener API. It allows users to retrieve real-time data about DEX pairs, token information, and market statistics from multiple blockchains.

How to use DexScreener MCP Server?

The server can be installed using the provided one-line install script or manually using npm. Once installed, you can use the available tools (e.g., get_latest_token_profiles, get_pairs_by_token_addresses) by calling them with the mcpClient.callTool method, passing the tool name and any required parameters.

Key features of DexScreener MCP Server

  • Rate-limited API access (respects DexScreener's rate limits)

  • Comprehensive error handling

  • Type-safe interfaces

  • Support for all DexScreener API endpoints

Use cases of DexScreener MCP Server

  • Real-time price monitoring of DEX pairs

  • Token information retrieval for analysis

  • Market statistics tracking across multiple blockchains

  • Building decentralized applications (dApps) that require DEX data

FAQ from DexScreener MCP Server

What is DexScreener?

DexScreener is a platform that provides real-time data on decentralized exchanges (DEXs).

What blockchains are supported?

The server supports all blockchains supported by the DexScreener API.

How do I handle rate limits?

The server implements rate limiting to comply with DexScreener's API limits. Ensure your application handles potential rate limit errors.

Where can I find the API documentation?

Detailed API documentation can be found in the docs/api-reference.md file.

How do I contribute to the project?

You can contribute by defining new types, implementing service methods, adding tool handlers, updating documentation, and adding tests.