Archived listing / no verified MCP endpoint/Finance

BitcoinYield listing

No MCP endpoint is published. This listing is retained for reference.

BitcoinYield was a yield comparison service for Bitcoin, stablecoins, ETH and SOL across DeFi and CeFi, ranking the best proven rate at each A-D risk grade. Its last known MCP tools were list_yields, which returned the best yield per asset by grade, and list_offers, which returned top offers for one asset filtered by chain and risk. The provider is offline: the site and API now return HTTP 410 with the message that BitcoinYield is no longer available, so the endpoint, transport and no-auth posture are last-known values rather than a current configuration.

Archived listingNo verified MCP endpoint is published. This page is retained for reference only.Official docs
Source checked Nov 13, 2026 No MCP endpoint Reviewed 2026-11-16
About

Where it fits

Readers checking what the retired BitcoinYield server exposed; it is no longer usable.

  • Reference the last known list_yields behaviour.
  • Reference the last known list_offers filters.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The provider's page did not load when we checked. Confirm the current setup steps before troubleshooting the client.
  • The server connects but no tools appear. Confirm the URL and transport, then restart the client.
  • The first tool call times out. Try a smaller request and check the provider's status or rate limits.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

BitcoinYield documentationhttps://bitcoinyield.co/docs