Remote MCP · Endpoint

LP Pool Check MCP server

No. LP Pool Check answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://lpcheck.openkrill.app/mcp

The last check completed an MCP handshake.

Registry name
app.openkrill/lpcheck
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
196 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Read a liquidity pool's volume, TVL and fee APR over 1 and 7 days, and spot a short APR spike.
Listing
From the official MCP registry (active).
Recent checks of LP Pool Check
CheckedResultHandshake
2 hours agoHandshake completed196 ms
1 day agoHandshake completed151 ms
4 days agoHandshake completed4.20 s
6 days agoHandshake completed143 ms
9 days agoHandshake completed721 ms
11 days agoHandshake completed312 ms
13 days agoHandshake completed148 ms
15 days agoHandshake completed342 ms
17 days agoHandshake completed68 ms
19 days agoHandshake completed44 ms
21 days agoHandshake completed41 ms
22 days agoHandshake completed99 ms
24 days agoHandshake completed969 ms
25 days agoHandshake completed846 ms
27 days agoHandshake completed53 ms

The last 15 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 LP Pool Check and makes no claim about it beyond what these checks measured.