Uniswap Poolspy MCP Server

If you already use Uniswap Poolspy MCP, the uniswap poolspy mcp mcp server is the piece that lets your assistant work with it directly. An MCP server that tracks newly created liquidity pools on Uniswap across nine blockchain networks — Ethereum, Base, Optimism, Arbitrum, Polygon, BNB Smart Chain (BSC), Avalanche, Celo, and Blast — providing real-time data for DeFi.

What the server does

• Monitors Uniswap V3 pool creation across 9 blockchain networks
• Customizable time range and result limits for querying new pools
• Supports sorting by timestamp, transaction count, volume, or TVL

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Configuration — To make the server discoverable by MCP clients (e.g., Claude Desktop), configure it in an mcpServers file:

Credentials and setup notes

Configuration is passed through the environment: THEGRAPH_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Python 3.10 or higher - uv for package management - A valid The Graph API key - MCP-compatible environment (e.g., Claude Desktop) for full functionality

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Uniswap Poolspy MCP's toolset — Configuration — is a fair guide to whether it matches your workflow. It is maintained by kukapay; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.