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 (11 hours ago)
Scores higher than 31% 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 Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 16 Oct 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- 15 Oct 26 37
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
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 Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.lpsignal.app/.well-known/oauth-protected-resource/v1/mcp", scope="mcp:read"
Bearer resource_metadata="https://api.lpsignal.app/.well-known/oauth-protected-resource/v1/mcp", scope="mcp:read"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://api.lpsignal.app/.well-known/oauth-protected-resource/v1/mcp", scope="mcp:read" |
Protected resource metadata
| Document | https://api.lpsignal.app/.well-known/oauth-protected-resource/v1/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.lpsignal.app/v1/mcp |
| Authorisation server | https://lpsignal.app |
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 | Auth required | 401 | |
| http (plaintext) | http://api.lpsignal.app/v1/mcp | HTTPS enforced | 308 | https://api.lpsignal.app/v1/mcp |
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 ~95
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. 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 ~146
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. Without a paid key opportunities appear 24 hours after they fired.
| 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.
my_account My account ~31
With an API key: the account's plan, the signal kinds pushed to it, and its custom alert rules.
Input schema present but exposes no named parameters.
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, 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'
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).
Is the LPSignal MCP server safe to use?
LPSignal scores 37 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 8 tools: list_pools, find_pair_pools, get_pool, backtest_range, list_signals, and 3 more. Their descriptions and schemas cost roughly 821 tokens of context every time the server is loaded.
Does the LPSignal MCP server require authentication?
Yes. LPSignal asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
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.