Remote MCP · Endpoint

Web3Juice MCP server

No. Web3Juice answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://web3juice.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.web3juice/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
870 ms
Tools exposed
14 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Evidence-backed DeFi yield data for ~17,000 pools: rates, yield sources, 90-day history. Read-only.
Listing
From the official MCP registry (active).
Recent checks of Web3Juice
CheckedResultHandshake
7 hours agoHandshake completed870 ms
4 days agoHandshake completed502 ms
14 days agoHandshake completed361 ms
15 days agoHandshake completed398 ms
15 days agoHandshake completed386 ms
17 days agoHandshake completed545 ms
18 days agoHandshake completed756 ms
19 days agoHandshake completed919 ms
20 days agoHandshake completed705 ms
21 days agoHandshake completed845 ms
23 days agoFailed - the request timed out—
26 days agoHandshake completed571 ms
28 days agoHandshake completed372 ms

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

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