Fire in da houseTop Tip:Paying $100+ per month for Perplexity, MidJourney, Runway, ChatGPT and other tools is crazy - get all your AI tools in one site starting at $15 per month with Galaxy AI Fire in da houseCheck it out free

dexscreener-mcp-server

MCP.Pizza Chef: openSVM

The DexScreener MCP Server is a dedicated MCP server implementation that interfaces with the DexScreener API to deliver real-time decentralized exchange (DEX) pair data, token profiles, and market statistics across multiple blockchain networks. It features rate-limited API access to comply with DexScreener's usage policies, comprehensive error handling, and type-safe interfaces for robust integration. Supporting all DexScreener API endpoints, this server enables seamless access to up-to-date token and market information, making it ideal for developers building blockchain analytics, trading bots, or portfolio trackers. Installation is straightforward with automated scripts or manual npm commands, and it includes integration tests to ensure reliability.

Use This MCP server To

Access real-time DEX pair data across blockchains Retrieve latest token profiles and boosted tokens Fetch market statistics for decentralized exchanges Integrate DexScreener data into trading bots Build blockchain portfolio tracking tools Monitor token performance with up-to-date info Respect DexScreener API rate limits automatically

README

DexScreener MCP Server

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.

One-line install (automatically adds to Claude Desktop):

curl -L https://raw.githubusercontent.com/opensvm/dexscreener-mcp-server/main/install.sh | bash

Features

  • Rate-limited API access (respects DexScreener's rate limits)
  • Comprehensive error handling
  • Type-safe interfaces
  • Support for all DexScreener API endpoints
  • Integration tests

Installation

Manual installation:

npm install
npm run build
npm run setup

Testing

npm test

Usage

Available Tools

  1. get_latest_token_profiles

    • Get the latest token profiles
    • No parameters required
    const result = await mcpClient.callTool('dexscreener', 'get_latest_token_profiles');
  2. get_latest_boosted_tokens

    • Get the latest boosted tokens
    • No parameters required
    const result = await mcpClient.callTool('dexscreener', 'get_latest_boosted_tokens');
  3. get_top_boosted_tokens

    • Get tokens with most active boosts
    • No parameters required
    const result = await mcpClient.callTool('dexscreener', 'get_top_boosted_tokens');
  4. get_token_orders

    • Check orders paid for a specific token
    const result = await mcpClient.callTool('dexscreener', 'get_token_orders', {
      chainId: 'solana',
      tokenAddress: 'So11111111111111111111111111111111111111112'
    });
  5. get_pairs_by_chain_and_address

    • Get one or multiple pairs by chain and pair address
    const result = await mcpClient.callTool('dexscreener', 'get_pairs_by_chain_and_address', {
      chainId: 'solana',
      pairId: 'HxFLKUAmAMLz1jtT3hbvCMELwH5H9tpM2QugP8sKyfhc'
    });
  6. get_pairs_by_token_addresses

    • Get one or multiple pairs by token address (max 30)
    const result = await mcpClient.callTool('dexscreener', 'get_pairs_by_token_addresses', {
      tokenAddresses: 'So11111111111111111111111111111111111111112'
    });
  7. search_pairs

    • Search for pairs matching query
    const result = await mcpClient.callTool('dexscreener', 'search_pairs', {
      query: 'SOL'
    });

Rate Limits

The server implements rate limiting to comply with DexScreener's API limits:

  • Token Profile/Boost endpoints: 60 requests per minute
  • DEX/Pairs endpoints: 300 requests per minute

Error Handling

The server handles various error scenarios:

  • Rate limit exceeded
  • Invalid parameters
  • Network errors
  • API errors

Errors are returned in a standardized format with appropriate error codes and messages.

API Documentation

For detailed API documentation, see docs/api-reference.md.

Development

Project Structure

.
├── src/
│   ├── types/           # TypeScript interfaces and types
│   ├── services/        # API service implementations
│   ├── tests/           # Integration tests
│   └── index.ts         # Main server implementation
├── scripts/            # Setup and utility scripts
├── docs/              # Documentation
└── README.md          # This file

Adding New Features

  1. Define types in src/types/
  2. Implement service methods in src/services/
  3. Add tool handlers in src/index.ts
  4. Update documentation
  5. Add tests

License

MIT

dexscreener-mcp-server FAQ

How do I install the DexScreener MCP Server?
You can install it automatically using the provided curl script or manually via npm commands: npm install, npm run build, and npm run setup.
Does the server handle DexScreener API rate limits?
Yes, it includes built-in rate limiting to respect DexScreener's API usage policies and prevent request throttling.
What kind of data can I access with this MCP server?
You can access real-time DEX pair data, token profiles, boosted tokens, and market statistics across multiple blockchains.
Is the DexScreener MCP Server compatible with multiple blockchains?
Yes, it supports data retrieval from DexScreener's API across various blockchain networks.
How does the server ensure data reliability?
It features comprehensive error handling and integration tests to maintain stable and accurate data access.
Can I use this server with different LLM providers?
Yes, it integrates with MCP clients that can work with OpenAI, Claude, Gemini, and other LLM providers.
Are there type-safe interfaces available?
Yes, the server provides type-safe interfaces for safer and more predictable API interactions.
How do I test the DexScreener MCP Server after installation?
Run npm test to execute the included test suite and verify the server's functionality.