LPSignal
REMOTE · API.LPSIGNAL.APP · 2 COMPONENTS
Uniswap/PancakeSwap/Aerodrome LP pools and price ranges ranked by net APR after impermanent loss
Available components
Last scanned (8 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Crypto and Web3
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 65% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +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.
- 16 Oct 26 0
- 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 security
- Schema quality: 143 → 188 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://api.lpsignal.app/v1/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.lpsignal.app | CN=YE2,O=Let's Encrypt,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5ce87951dece00ef4dcd27c37a181094c7b |
| SANs: api.lpsignal.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.lpsignal.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| lpsignal.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.lpsignal.app/v1/mcp/public | Verified | 200 | |
| http (plaintext) | http://api.lpsignal.app/v1/mcp/public | HTTPS enforced | 308 | https://api.lpsignal.app/v1/mcp/public |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
backtest_range Backtest a price range ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | pool contract address (0x + 40 hex), or a Uniswap v4 pool id (0x + 64 hex) |
| chain | string | yes | – |
| days | integer | – | default 7 |
| rangePct | number | yes | half-width in percent; 0 = full range |
No output schema declared.
No examples provided.
find_pair_pools Pools of a token pair ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| tokenA | string | yes | e.g. USDC |
| tokenB | string | yes | e.g. WETH |
No output schema declared.
No examples provided.
get_pool One pool's backtests ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | pool contract address (0x + 40 hex), or a Uniswap v4 pool id (0x + 64 hex) |
| chain | string | yes | – |
No output schema declared.
No examples provided.
list_pools Rank LP pools ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
list_signals Latest signals ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
signal_track_record Signal track record ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | signals fired in the last N days (default 30) |
| kind | string | – | default net_apr |
No output schema declared.
No examples provided.
smart_lp_leaderboard Smart-LP leaderboard ~65
Wallets ranked by what their closed LP positions made versus simply holding the tokens. Without a Pro key: the top 10, addresses masked.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| limit | integer | – | default 10 |
| windowDays | integer | – | – |
No output schema declared.
No examples provided.
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.
remote · api.lpsignal.app
claude mcp add --transport http app-lpsignal-lpsignal 'https://api.lpsignal.app/v1/mcp/public'
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.