Remote MCP · Endpoint

YieldCave MCP server

No. YieldCave answered an MCP handshake 36 minutes ago.

UpLast checked 36 minutes ago

Server URL

https://ccvhvxbqtvqbhexhrjnj.supabase.co/functions/v1/mcp

The last check completed an MCP handshake.

Registry name
com.yieldcave/yieldcave
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
579 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Tokenized asset data for agents: treasury yields, stablecoin rates, tokenized stocks, alerts.
Listing
From the official MCP registry (active).
Recent checks of YieldCave
CheckedResultHandshake
36 minutes agoHandshake completed579 ms
8 days agoHandshake completed554 ms
9 days agoHandshake completed254 ms
11 days agoHandshake completed635 ms
12 days agoHandshake completed242 ms
12 days agoHandshake completed645 ms
14 days agoHandshake completed496 ms
14 days agoHandshake completed565 ms
16 days agoHandshake completed304 ms
19 days agoHandshake completed631 ms
21 days agoHandshake completed427 ms
24 days agoHandshake completed559 ms
26 days agoHandshake completed649 ms
28 days agoHandshake completed464 ms

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

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 YieldCave and makes no claim about it beyond what these checks measured.