Remote MCP · Endpoint

LPSignal MCP server

No. LPSignal answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
app.lpsignal/lpsignal
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
794 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Uniswap/PancakeSwap/Aerodrome LP pools and price ranges ranked by net APR after impermanent loss
Listing
From the official MCP registry (active).
Recent checks of LPSignal
CheckedResultHandshake
44 minutes agoHandshake completed794 ms
8 days agoHandshake completed694 ms
9 days agoHandshake completed707 ms
11 days agoHandshake completed682 ms
12 days agoHandshake completed718 ms
13 days agoHandshake completed678 ms
14 days agoHandshake completed685 ms
14 days agoHandshake completed694 ms
16 days agoHandshake completed710 ms
19 days agoHandshake completed691 ms
21 days agoHandshake completed698 ms
24 days agoHandshake completed946 ms
26 days agoHandshake completed722 ms
28 days agoHandshake completed719 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with LPSignal and makes no claim about it beyond what these checks measured.