1. Conduid
  2. Blockchain
  3. DexScreener Pairs
MCP server · Blockchain

DexScreener Pairs

Discover crypto trading pairs across supported chains on DexScreener. Fetch up-to-date pair details by chain and address, or list all pairs for a token. Speed up market research for pricing, liquidity, and new opportunities.

Unclaimed last commit 11 months ago blockchain
34Low

Scored 7 months ago · breakdown

About DexScreener Pairs

DexScreener Pairs is an MCP server published by catwhisperingninja in the Blockchain category: discover crypto trading pairs across supported chains on DexScreener. Fetch up-to-date pair details by chain and address, or list all pairs for a token. Speed up market research for pricing, liquidity, and new opportunities.

Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/catwhisperingninja/cat-dexscreener

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about DexScreener Pairs

Powered by Claude · Grounded in docs

I know everything about DexScreener Pairs. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

DexScreener MCP Server

smithery badge

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

Runtime configuration

Provide SMITHERY_API_KEY at runtime. Do not bake it into the image.

Docker Compose (recommended):

  1. Using .env file:
echo "SMITHERY_API_KEY=your_api_key" > .env

Ensure your service has:

services:
  dexscreener-mcp:
    env_file:
      - .env
    environment:
      NODE_ENV: production
  1. Or via inline environment variables:
services:
  dexscreener-mcp:
    environment:
      SMITHERY_API_KEY: ${SMITHERY_API_KEY}
      NODE_ENV: production

Kubernetes:

  • Store the key in a Secret:
kubectl create secret generic smithery-api --from-literal=SMITHERY_API_KEY=your_api_key
  • Reference it in your Deployment:
env:
  - name: SMITHERY_API_KEY
    valueFrom:
      secretKeyRef:
        name: smithery-api
        key: SMITHERY_API_KEY

Note: If a default is required, set it in the orchestrator (Compose/Kubernetes), not in the Dockerfile.

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

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About DexScreener Pairs

How do I install DexScreener Pairs?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is DexScreener Pairs safe to use with an AI agent?

Its trust score is 34 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is DexScreener Pairs still maintained?

The last commit was 11 months ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.