← Registry

General Tools

bitcoinyield.co

Provides general-purpose tools through the Model Context Protocol.

1 endpoint1 known toolsFirst detected September 19, 2026Last detected September 19, 2026

ENDPOINT 1

https://bitcoinyield.co/api/mcp

No auth detected

MCP server metadata

Name
BitcoinYield
Version
1.0.0
Capabilities
tools
Server instructions

Compare live crypto yields across the whole market, DeFi and CeFi. Use list_yields to browse the current best live APY and risk grade for each asset.

Known tools 1

list_yields

One entry per asset (BTC, USDC, USDT, DAI, ETH) with the current best live APY across the whole market, DeFi and CeFi, plus its A-D risk grade.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.bitcoinyield]
url = "https://bitcoinyield.co/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "bitcoinyield": {
      "type": "http",
      "url": "https://bitcoinyield.co/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: bitcoinyield
Remote MCP URL: https://bitcoinyield.co/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "bitcoinyield": {
      "url": "https://bitcoinyield.co/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "bitcoinyield": {
      "type": "http",
      "url": "https://bitcoinyield.co/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "bitcoinyield",
  "transport": "streamable-http",
  "url": "https://bitcoinyield.co/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.