Remote MCP · Endpoint

BitcoinYield MCP server

Yes, as of 48 minutes ago: the server returned an HTTP error.

DownLast checked 48 minutes ago

Server URL

https://bitcoinyield.co/api/mcp

The last check failed: the server returned an HTTP error.

Registry name
co.bitcoinyield/yields
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
2 tools
Uptime, last 30 days
92.9% from 14 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
48 minutes agoFailed - the server returned an HTTP error—
10 days agoHandshake completed132 ms
10 days agoHandshake completed154 ms
11 days agoHandshake completed174 ms
12 days agoHandshake completed125 ms
14 days agoHandshake completed145 ms
14 days agoHandshake completed103 ms
15 days agoHandshake completed163 ms
17 days agoHandshake completed159 ms
19 days agoHandshake completed114 ms
21 days agoHandshake completed145 ms
24 days agoHandshake completed106 ms
26 days agoHandshake completed112 ms
28 days agoHandshake completed483 ms

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

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.