Bitcoin Signals MCP server
{
"mcpServers": {
"coinbucha": {
"type": "http",
"url": "https://coinbucha.com/api/mcp"
}
}
}{
"mcpServers": {
"coinbucha": {
"type": "http",
"url": "https://coinbucha.com/api/mcp"
}
}
}{
"mcpServers": {
"coinbucha": {
"type": "http",
"url": "https://coinbucha.com/api/mcp"
}
}
}{
"servers": {
"coinbucha": {
"type": "http",
"url": "https://coinbucha.com/api/mcp"
}
}
}{
"mcpServers": {
"coinbucha": {
"type": "http",
"url": "https://coinbucha.com/api/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.1.1
What it does
MCP server that exposes Bitcoin market and network signals—sovereign reserves, hiring velocity, hashrate, ETF flows, and corporate treasury holdings—as ranked, non-price indicators with strength scores, directions, and source citations. Intended for AI agents and analysts who need leading indicators rather than price analysis.
- Monitor Bitcoin adoption signals across sovereigns, corporations, and mining infrastructure to assess structural trends.
- Query hiring velocity in Bitcoin and crypto infrastructure to gauge sector momentum.
- Retrieve ranked composite signals filtered by strength and direction to identify current market tailwinds or headwinds.
Tools this server exposes
| Tool | Does |
|---|---|
| scan_signals | Returns ranked composite signal feed with filters for minimum strength, direction, and signal types. |
| get_hiring_signal | Returns Bitcoin and crypto infrastructure hiring velocity including open roles and 30/90-day deltas. |
| get_sovereign_reserves | Returns sovereign Bitcoin holdings ranked by country or tier. |
| get_treasury_holdings | Returns corporate Bitcoin treasury holdings for public companies. |
| get_etf_flows | Returns spot Bitcoin ETF net flows for latest day and trailing 5/30-day periods. |
| get_network_signal | Returns Bitcoin network hashrate level and 30/90-day trend. |
| get_daily_brew | Returns today's machine-readable signal digest. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.