Remote MCP · Endpoint

TRDEFI Liquidity MCP server

No. TRDEFI Liquidity answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://yield.trdefi.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.TRDEFI/liquidity
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
445 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Live non-custodial stablecoin liquidity: open positions, volume, and an on-chain swap quote.
Listing
From the official MCP registry (active).
Recent checks of TRDEFI Liquidity
CheckedResultHandshake
2 hours agoHandshake completed445 ms
2 days agoHandshake completed641 ms
4 days agoHandshake completed405 ms
6 days agoHandshake completed305 ms
8 days agoHandshake completed536 ms
9 days agoHandshake completed294 ms
11 days agoHandshake completed467 ms
12 days agoHandshake completed794 ms
14 days agoHandshake completed318 ms
16 days agoHandshake completed165 ms
17 days agoHandshake completed389 ms
19 days agoHandshake completed486 ms
20 days agoHandshake completed272 ms
21 days agoHandshake completed308 ms
22 days agoHandshake completed190 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 TRDEFI Liquidity and makes no claim about it beyond what these checks measured.