bitcoin-signals

Is bitcoin-signals MCP server safe?

• None of the hidden-instruction wordings we know were found in its tool descriptions.
• Its error messages showed no secrets or internal details.
• All 10 of its tools are labeled read-only.
• Overall it scored 95/100 on 3 Nov 2026.

A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

What it can do

10 tools, in the server's own words.

Test results

Safe mode: only tools labeled read-only were run. How the test works

• !
  Ready for the newest MCP version

  1 warning

  • !Uses an older MCP version (2025-11-25). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
  note
• !
  Follows MCP best practices (not scored yet)

  1 tip (not scored)

  • !10 tools answer with structured data but don't declare its shape (outputSchema): scan_signals, get_hiring_signal, get_sovereign_reserves, sovereign_diff, get_treasury_holdings, get_etf_flows and 4 more. If those answers change shape, nothin
  note
• ✓
  ConnectsConnected in 417 ms
  pass
• ✓
  Lists its toolsFound 10 tools
  pass
• ✓
  Every tool is describedAll 10 tools and their inputs are described
  pass
• ✓
  Tools are labeled safe or dangerousEvery tool has a safety label
  pass
• ✓
  No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.
  pass
• ✓
  Tools work with good inputs

  All good

  • ✓scan_signals: Worked (157 ms)
  • ✓get_hiring_signal: Worked (303 ms)
  • ✓get_sovereign_reserves: Worked (159 ms)
  • ✓sovereign_diff: Worked (162 ms)
  • ✓get_treasury_holdings: Worked (231 ms)
  • ✓get_etf_flows: Worked (591 ms)
  • ✓get_network_signal: Worked (198 ms)
  • ✓get_bitcoin_company_calendar: Worked (157 ms)
  • and 2 more
  pass
• ✓
  Bad inputs give a clean error

  All good

  • ✓scan_signals: Refused wrong type for "min_strength" with a clear error
  • ✓get_hiring_signal: Refused wrong type for "company" with a clear error
  • ✓get_sovereign_reserves: Refused wrong type for "country" with a clear error
  • ✓sovereign_diff: Refused wrong type for "from" with a clear error
  • ✓get_bitcoin_company_calendar: Refused wrong type for "ticker" with a clear error
  • ✓get_signal_history: Refused missing required input "signal_type" with a clear error
  • ✓get_signal_history: Refused wrong type for "signal_type" with a clear error
  pass
• ✓
  Fast enough

  All good

  • ✓Connecting took 417 ms
  • ✓Listing tools took 58 ms
  • ✓Average tool answer: 227 ms
  • ✓get_etf_flows: Slowest tool: get_etf_flows (591 ms)
  pass
• ✓
  No secrets leakedChecked 7 error messages: no secrets or internal details
  pass
• ✓
  Resources and prompts work

  All good (18 resources, 2 templates, 3 prompts)

  • ✓Opened 10 of 10 resources (a sample of 10 of 18)
  • ✓coinbucha://sovereign/{country}: Filling in the pattern and opening it works (coinbucha://sovereign/qamcp-test)
  • ✓coinbucha://sovereign/snapshot/{date}: A made-up value gets a clean error (coinbucha://sovereign/snapshot/qamcp-test)
  • –An address that doesn't exist was not checked: the server limited our requests (HTTP 429)
  • –morning_bitcoin_brief: Not checked: the server limited our requests (HTTP 429)
  • –sovereign_reserve_check: Not checked: the server limited our requests (HTTP 429)
  • –hiring_velocity_check: Not checked: the server limited our requests (HTTP 429)
  pass
• –
  Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)
  not tested

Test it yourself

Free and open source. Same checks, same score.

Show this score on GitHub

Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.

Score over time

• 3 Nov 202695

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use bitcoin-signals, signed in with GitHub, one per person. Reviews never change the score.