Skip to main content
Glama
enesjakozh
kukapay

uniswap-poolspy-mcp

by kukapay
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

Uniswap PoolSpy MCP 서버

Ethereum, Base, Optimism, Arbitrum, Polygon, BNB Smart Chain(BSC), Avalanche, Celo, Blast 등 9개 블록체인 네트워크에서 Uniswap에 새로 생성된 유동성 풀을 추적하는 MCP 서버로, DeFi 분석가, 트레이더, 개발자에게 실시간 데이터를 제공합니다.

파이썬특허상태

특징

  • 9개 블록체인 네트워크에서 Uniswap V3 풀 생성을 모니터링합니다.

  • 새로운 풀을 쿼리하기 위한 사용자 정의 가능한 시간 범위 및 결과 제한.

  • 타임스탬프, 거래 수, 볼륨 또는 TVL을 기준으로 정렬을 지원합니다.

Related MCP server: uniswap-trader-mcp

필수 조건

  • Python 3.10 이상

  • 패키지 관리를 위한 uv

  • 유효한 The Graph API 키

  • 전체 기능을 위한 MCP 호환 환경(예: Claude Desktop)

설치

  1. 저장소 복제 :

    지엑스피1

  2. 환경 설정 : 아직 uv 설치하지 않았다면 설치하세요.

    curl -LsSf https://astral.sh/uv/install.sh | sh

  3. 종속성 설치 : uv 사용하여 pyproject.toml 에서 종속성을 동기화합니다.

    uv sync

  4. API 키 구성 : 프로젝트 루트에 .env 파일을 만듭니다.

    echo "THEGRAPH_API_KEY=your-api-key-here" > .env

    your-api-key-here 실제 The Graph API 키로 바꾸세요.

용법

서버 실행

MCP 서버를 시작합니다.

uv run main.py

MCP Inspector를 사용한 개발의 경우:

uv run mcp dev main.py

Claude Desktop과 통합

MCP 플러그인으로 서버를 설치하세요:

uv run mcp install main.py --name "UniswapPoolSpy"

구성

MCP 클라이언트(예: Claude Desktop)에서 서버를 검색할 수 있도록 하려면 mcpServers 파일에서 서버를 구성하세요.

{
  "mcpServers": {
    "Uniswap-PoolSpy": {
      "command": "uv",
      "args": ["--directory", "path/to/uniswap-poolspy-mcp", "run", "main.py"],
      "env": {
        "THEGRAPH_API_KEY": "your api key from The Graph"
      }
    }
  }
}

새 풀 쿼리

Claude Desktop의 get_new_pools 도구를 다음과 같은 자연어 쿼리와 함께 사용하세요.

  • "지난 10분 동안 이더리움의 새로운 풀을 보여주세요"

  • "Base에 볼륨별로 정렬된 풀 목록, 최대 50개로 제한"

  • "지난 1시간 동안 Polygon에 어떤 풀이 생성되었으며, TVL 순으로 정렬되어 있습니까?"

이 도구는 다음 매개변수를 허용합니다.

  • chain : 블록체인 네트워크(예: "이더리움", "베이스", "옵티미즘")

  • order_by : 정렬 필드("timestamp", "txcount", "volume", "tvl")

  • time_range_seconds : 룩백 기간(초) (기본값: 300)

  • limit : 반환할 풀의 최대 개수(기본값: 100)

출력 예

Newly Created Trading Pools (Last 5 Minutes, Limit: 100):
Pool Address: 0x1234...abcd
Tokens: WETH/USDC
Created At: 2025-03-18 12:34:56
Block Number: 12345678
Transaction Count: 5
Volume (USD): 15000.25
Total Value Locked (USD): 50000.75

Pool Address: 0x5678...efgh
Tokens: DAI/USDT
Created At: 2025-03-18 12:33:45
Block Number: 12345670
Transaction Count: 3
Volume (USD): 8000.50
Total Value Locked (USD): 25000.00

지원되는 체인

  • 이더리움

  • 베이스

  • 낙천주의

  • 중재

  • 다각형

  • BNB 스마트 체인(BSC)

  • 눈사태

  • 셀로

  • 폭발

특허

이 프로젝트는 MIT 라이선스에 따라 라이선스가 부여되었습니다. 자세한 내용은 라이선스 파일을 참조하세요.

Available Tools

1 tool
get_new_poolsB

Returns a list of trading pools created in the specified time range on Uniswap V3.

Parameters: chain (str): The blockchain on which Uniswap is deployed. Default is 'ethereum'. Supported options include: 'ethereum', 'base', 'optimism', 'arbitrum', 'polygon', 'bsc', 'avalanche', 'celo' and 'blast'. order_by (str): The field to sort data in descending order before returning to the user. Default is 'timestamp'. Supported options include: - timestamp: Sort by Timestamp - txcount: Sort by Transaction Count - tvl: Sort by Total Value Locked - volume: Sort by Volume time_range_seconds (int): The time range in seconds to look back for new pools. Default is 300 seconds (5 minutes). limit (int): The maximum number of pools to return. Default is 100 pools.

ParametersJSON Schema
NameRequiredDescriptionDefault
chainNoethereum
limitNo
order_byNotimestamp
time_range_secondsNo

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes a read-only operation ('returns a list') but lacks details on permissions, rate limits, error handling, or response format. For a tool with 4 parameters and no annotation coverage, this leaves significant behavioral gaps, though it minimally indicates a safe read operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and appropriately sized, with a clear purpose statement followed by a parameter breakdown. Each sentence adds value, and there is no redundant information. However, it could be slightly more front-loaded with key usage notes, preventing a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 parameters, no annotations, and no output schema, the description is moderately complete. It covers parameter semantics thoroughly but lacks behavioral context (e.g., response format, error cases) and usage guidelines. For a read-only tool with moderate complexity, this is adequate but has clear gaps, aligning with a minimum viable description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by detailing all 4 parameters: 'chain', 'order_by', 'time_range_seconds', and 'limit'. It provides clear semantics, default values, supported options for 'chain' and 'order_by', and explanations of each parameter's role, adding substantial value beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Returns a list of trading pools created in the specified time range on Uniswap V3.' It specifies the verb ('returns'), resource ('trading pools'), and scope ('created in the specified time range on Uniswap V3'). However, with no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, preventing a score of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. It only lists parameters without contextual usage advice. While no sibling tools are specified, the description still lacks general usage context, such as typical scenarios or limitations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedget_new_pools
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'get_new_pools' has a single, clearly defined purpose: retrieving newly created Uniswap V3 pools within a specified time range.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'get_new_pools' follows a clear verb_noun pattern (get + new_pools), which would be consistent if more tools were added.

Tool Count2/5

A single tool is too few for a server named 'uniswap-poolspy-mcp', which suggests broader monitoring or analysis of Uniswap pools. This minimal toolset limits functionality to only retrieving new pools, lacking operations like querying existing pools, analyzing pool metrics, or tracking pool changes over time.

Completeness2/5

The tool surface is severely incomplete for the implied domain of Uniswap pool monitoring. While 'get_new_pools' covers discovery of new pools, there are significant gaps: no tools for getting pool details, tracking liquidity or volume trends, analyzing historical data, or performing CRUD-like operations on pool information, which agents would need for comprehensive analysis.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kukapay/uniswap-poolspy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server