Remote MCP · Endpoint

BitcoinYield MCP server

No. BitcoinYield answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://bitcoinyield.co/api/mcp

The last check completed an MCP handshake.

Registry name
co.bitcoinyield/yields
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
483 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Best live crypto yield at each A-D risk grade on BTC, ETH, SOL and stablecoins, DeFi and CeFi.
Listing
From the official MCP registry (active).
Recent checks of BitcoinYield
CheckedResultHandshake
2 hours agoHandshake completed483 ms
2 days agoHandshake completed220 ms
4 days agoHandshake completed116 ms
6 days agoHandshake completed93 ms
8 days agoHandshake completed165 ms
9 days agoHandshake completed111 ms
11 days agoHandshake completed150 ms
12 days agoHandshake completed108 ms
14 days agoHandshake completed176 ms
16 days agoHandshake completed83 ms
17 days agoHandshake completed89 ms
19 days agoHandshake completed115 ms
20 days agoHandshake completed89 ms
21 days agoHandshake completed99 ms
22 days agoHandshake completed231 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 BitcoinYield and makes no claim about it beyond what these checks measured.