Skip to main content
Glama
liquidity-pools-mcp

liquidity-pools-mcp

by kukapay

Liquidity Pools MCP Server

An MCP server that tracks and analyzes DEX liquidity pools to power intelligent DeFi agents and automated strategies.

GitHub License Python Version Status

Features

  • Liquidity Pool Data Retrieval: Fetches liquidity pool details for a specified chain ID and token address using the DexScreener API.

  • Markdown Table Output: Presents pool data in a clear markdown table with columns for Dex ID, Pair Address, Base/Quote Token Symbols, Price USD, 24h Buy/Sell Transactions, 24h Volume, Liquidity USD, and Market Cap.

  • Total Liquidity Calculation: Computes and displays the total liquidity in USD across all pools.

  • Prompt Guidance: Includes a prompt to guide users on analyzing liquidity pool data, including pool count, table output, total liquidity, and notable metrics.

Related MCP server: dex-kline-mcp

Prerequisites

  • Python 3.10 or higher.

  • uv: Recommended for managing dependencies (documentation).

Installation

  1. Clone the Repository:

    git clone https://github.com/kukapay/liquidity-pools-mcp.git
    cd liquidity-pools-mcp
  2. Install Dependencies:

    Using uv (recommended for faster dependency management):

    uv sync

    Or using pip:

    pip install mcp[cli]
  3. Installing to Claude Desktop:

    Install the server as a Claude Desktop application:

    uv run mcp install main.py --name "Liquidity Pools"

    Configuration file as a reference:

    {
       "mcpServers": {
           "Liquidity Pools": {
               "command": "uv",
               "args": [ "--directory", "/path/to/liquidity-pools-mcp", "run", "main.py" ] 
           }
       }
    }

    Replace /path/to/liquidity-pools-mcp with your actual installation path.

Usage

Use the MCP Inspector or integrate with a client (e.g., Claude Desktop) to call the get_liquidity_pools tool.

Example Prompt:

Fetch the liquidity pools for token 0xe6DF05CE8C8301223373CF5B969AFCb1498c5528 on chain bsc.

Example Output:

| Dex ID      | Pair Address                              | Base/Quote | Price USD | 24h Buys/Sells | 24h Volume | Liquidity USD | Market Cap |
|-------------|-------------------------------------------|------------|-----------|----------------|------------|---------------|------------|
| pancakeswap | 0x123...abc                              | CAKE/BUSD  | 2.45      | 150/100        | 500000     | 1000000       | 2000000    |
| apeswap     | 0x456...def                              | CAKE/BNB   | 2.43      | 80/50          | 300000     | 800000        | 1900000    |

**Total Liquidity USD**: 1800000

License

This project is licensed under the MIT License. See the LICENSE file for details.

Available Tools

1 tool
get_liquidity_poolsA
Fetch all liquidity pools for a given chain ID and token address from DexScreener API.

Args:
    chain_id (str): The blockchain identifier (e.g., 'bsc' for Binance Smart Chain, 'eth' for Ethereum)
    token_address (str): The contract address of the token (e.g., '0xe6DF05CE8C8301223373CF5B969AFCb1498c5528')
    ctx (Context): MCP context for logging and request handling

Returns:
    str: A markdown table containing liquidity pool details including dexId, pairAddress, 
         base/quote token symbols, price USD, 24h buy/sell transactions, 24h volume, 
         liquidity USD, and market cap, followed by total liquidity USD

Inputs: chain_id (required), token_address (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap between tools. The tool has a single, clearly defined purpose of fetching liquidity pools from DexScreener API.

    Naming Consistency5/5

    The single tool follows a clear verb_noun pattern (get_liquidity_pools), which is consistent within this minimal set. There are no other tools to create inconsistency.

    Tool Count2/5

    A single tool is too few for a server focused on liquidity pools, which typically involves operations like creating, updating, or analyzing pools beyond just fetching. This feels incomplete for the domain.

    Completeness2/5

    The tool surface is severely incomplete for liquidity pool management. It only provides a fetch operation (get), missing essential CRUD operations like create, update, or delete pools, as well as analytical tools for deeper insights.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers