com.coinbucha/bitcoin-signals
com-coinbucha-bitcoin-signals declares 9 capabilities across 9 tools, with 1 critical issue.
Issues
9 of 9 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
9 of 9 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
9 of 9 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
9 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
scan_signals | read |
declared |
get_hiring_signal | read |
declared |
get_sovereign_reserves | read |
declared |
sovereign_diff | read |
declared |
get_treasury_holdings | read |
declared |
get_etf_flows | read |
declared |
get_network_signal | read |
declared |
get_daily_brew | read |
declared |
get_signal_history | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-11 | 16 | tools/list on https://coinbucha.com/api/mcp, published in the official MCP registry as com.coinbucha/bitcoin-signals 0.1.1 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.