# LPSignal (remote · api.lpsignal.app)

Uniswap/PancakeSwap/Aerodrome LP pools and price ranges ranked by net APR after impermanent loss

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `api.lpsignal.app`: 37/100, [markdown](https://verifymcp.io/servers/app-lpsignal-lpsignal/v1-mcp.md), [page](https://verifymcp.io/servers/app-lpsignal-lpsignal/v1-mcp)
- remote · `api.lpsignal.app`: 68/100 (this document), [markdown](https://verifymcp.io/servers/app-lpsignal-lpsignal/v1-mcp-public.md), [page](https://verifymcp.io/servers/app-lpsignal-lpsignal/v1-mcp-public)

## Channel facts

- Endpoint: `https://api.lpsignal.app/v1/mcp/public`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1318 tokens (~188/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 65% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the LPSignal MCP server?

LPSignal is a hosted endpoint at https://api.lpsignal.app/v1/mcp/public, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.app-lpsignal-lpsignal]
url = "https://api.lpsignal.app/v1/mcp/public"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-lpsignal-lpsignal": {
      "type": "remote",
      "url": "https://api.lpsignal.app/v1/mcp/public",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-lpsignal-lpsignal --url 'https://api.lpsignal.app/v1/mcp/public' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-lpsignal-lpsignal:
    url: "https://api.lpsignal.app/v1/mcp/public"
```

### Netclaw

```json
{
  "McpServers": {
    "app-lpsignal-lpsignal": {
      "Transport": "http",
      "Url": "https://api.lpsignal.app/v1/mcp/public"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-lpsignal-lpsignal -t streamable-http -u 'https://api.lpsignal.app/v1/mcp/public'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 67, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “find_pair_pools” rewrote its description, which is the text the model reads
- [security] Tool “list_signals” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 143 → 188
- [functional improvement] Stability: unverified → 0.03

### 2026-10-15 (score 67)

First indexed and scored.

## MCP tools (7)

### `list_pools` (~169 tokens)

Rank LP pools

Active pools ranked by the net APR (fees − impermanent loss) of their best price range over a window (default 7 days), with that range's ticks, TVL, 24h volume and the pool-level fee APR DEX sites show. Filter by chain and pool class.

Input parameters:

- `chain` (string)
- `class` (string): stable = stablecoin pairs, correlated = e.g. ETH/stETH, volatile = everything else
- `limit` (integer): default 10
- `minTvlUsd` (number): default 10000
- `offset` (integer)
- `order` (string)
- `sort` (string): default netApr
- `window` (integer): backtest window in hours (default 168 = 7 days)

### `find_pair_pools` (~108 tokens)

Pools of a token pair

Every listed pool of a token pair across chains, DEXes and fee tiers (TVL ≥ $10k), each with its best range by 7-day net APR, best first — a small pool can rank first, so weigh tvlUsd. Symbols are matched case-insensitively, in either order.

Input parameters:

- `chain` (string)
- `tokenA` (string, required): e.g. USDC
- `tokenB` (string, required): e.g. WETH

### `get_pool` (~99 tokens)

One pool's backtests

A pool's details and its backtest of every range it is evaluated on (fee APR, impermanent loss, net APR, time in range, the exact ticks) over 1 hour, 24 hours, 7 days and 30 days.

Input parameters:

- `address` (string, required): pool contract address (0x + 40 hex), or a Uniswap v4 pool id (0x + 64 hex)
- `chain` (string, required)

### `backtest_range` (~129 tokens)

Backtest a price range

Backtest a symmetric range of ±rangePct% around the price at the window's start (0 = full range) on a pool over the last `days` days: fee APR, impermanent loss, net APR, time in range, the ticks.

Input parameters:

- `address` (string, required): pool contract address (0x + 40 hex), or a Uniswap v4 pool id (0x + 64 hex)
- `chain` (string, required)
- `days` (integer): default 7
- `rangePct` (number, required): half-width in percent; 0 = full range

### `list_signals` (~168 tokens)

Latest signals

The newest signals: opportunities (net_apr: a range paying a high net APR over 7 days and still today; burst: the last hour; hot_pool: a big pool's fee APR jumping) and risk alerts (depeg, tvl_outflow), with the exact ticks and, once scored, the realised outcome. Each says access: live, or delayed_24h (opportunities on a free plan or without sign-in appear 24 hours after they fired). Page back with before.

Input parameters:

- `before` (string): page: signals with an id below this
- `kinds` (array)
- `limit` (integer): default 10
- `source` (string): with a key: rules = your custom-rule matches, subscribed = what your push channels deliver

### `signal_track_record` (~87 tokens)

Signal track record

How past opportunity signals really did: each is backtested again on its exact ticks after the fact (7 days for net_apr, 24 hours for burst). Counts, share positive, median APR at the signal vs realised, the worst.

Input parameters:

- `days` (integer): signals fired in the last N days (default 30)
- `kind` (string): default net_apr

### `smart_lp_leaderboard` (~65 tokens)

Smart-LP leaderboard

Wallets ranked by what their closed LP positions made versus simply holding the tokens. Without a Pro key: the top 10, addresses masked.

Input parameters:

- `chain` (string)
- `limit` (integer): default 10
- `windowDays` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-lpsignal-lpsignal/v1-mcp-public#diagnostics

## Score history

- 2026-10-18: 68
- 2026-10-17: 68
- 2026-10-16: 67
- 2026-10-15: 67

## Common questions

### What is the LPSignal MCP server?

LPSignal is an MCP server listed in the public MCP registry as app.lpsignal/lpsignal. Uniswap/PancakeSwap/Aerodrome LP pools and price ranges ranked by net APR after impermanent loss. This page covers its hosted endpoint (https://api.lpsignal.app/v1/mcp/public).

### Is the LPSignal MCP server safe to use?

LPSignal scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the LPSignal MCP server expose?

LPSignal exposes 7 tools: list_pools, find_pair_pools, get_pool, backtest_range, list_signals, and 2 more. Their descriptions and schemas cost roughly 825 tokens of context every time the server is loaded.

### Does the LPSignal MCP server require authentication?

No. We connected to LPSignal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the LPSignal MCP server still maintained?

LPSignal is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.lpsignal.app/v1/mcp/public
- Repository: https://github.com/LPSignals/lpsignal-mcp
- Website: https://lpsignal.app/docs
- Changelog RSS feed: https://verifymcp.io/servers/app-lpsignal-lpsignal/v1-mcp-public.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-lpsignal-lpsignal/v1-mcp-public.json
- HTML version of this page: https://verifymcp.io/servers/app-lpsignal-lpsignal/v1-mcp-public