LPSignal MCP

LPSignal provides an MCP server that allows AI agents to access real-time and historical data on concentrated-liquidity pools across multiple EVM chains. It enables agents to retrieve pool details, backtest liquidity ranges, and receive signals for high net APR opportunities after impermanent loss, facilitating automated liquidity management strategies.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-18Operated by LPSignal

MCP endpoint (Streamable HTTP)

https://api.lpsignal.app/v1/mcp/public

Vendor documentation

What you can do with it

Retrieve current liquidity pool metrics and APR data
Backtest specific price ranges for historical performance
Receive signals for high net APR liquidity opportunities
Access smart LP leaderboards and track records

Tools advertised by the last live check:

list_pools
find_pair_pools
get_pool
backtest_range
list_signals
signal_track_record
smart_lp_leaderboard

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http lpsignal-mcp https://api.lpsignal.app/v1/mcp/public

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add lpsignal-mcp --url https://api.lpsignal.app/v1/mcp/public

Cursor

Merge this server into .cursor/mcp.json in your project, then enable lpsignal-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "lpsignal-mcp": {
      "url": "https://api.lpsignal.app/v1/mcp/public"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "lpsignal-mcp": {
      "type": "streamableHttp",
      "url": "https://api.lpsignal.app/v1/mcp/public",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start lpsignal-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "lpsignal-mcp": {
      "type": "http",
      "url": "https://api.lpsignal.app/v1/mcp/public"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http lpsignal-mcp https://api.lpsignal.app/v1/mcp/public

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "lpsignal-mcp": {
      "url": "https://api.lpsignal.app/v1/mcp/public"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "lpsignal-mcp": {
      "serverUrl": "https://api.lpsignal.app/v1/mcp/public"
    }
  }
}

See all 2,063

Do you run LPSignal MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing