MCP servers observed by Lowdown
dev.workers.btc-intel.diamond/bitcoin-intel MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-10 to 2026-11-19) (Lowdown checks this server every 3 days); 40 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-16 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.workers.btc-intel.diamond/bitcoin-intel
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.workers.btc-intel.diamond/bitcoin-intel?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-19: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 3 compared days.
- 2026-11-16: input or output schemas changed, descriptions changed, tool names changed; tool count 35 → 40
- 2026-11-13: input or output schemas changed, descriptions changed
What tools does it list?
40 tools on 2026-11-19:
analyzebase_token_checkbase_tx_decodebase_wallet_checkbitcoin_address_infobitcoin_address_riskbitcoin_aml_livebitcoin_aml_stats_24hbitcoin_batch_riskbitcoin_block_headerbitcoin_block_statsbitcoin_decode_psbtbitcoin_decode_scriptbitcoin_decode_transactionbitcoin_fee_estimatesbitcoin_fee_historybitcoin_latest_blockbitcoin_market_pulsebitcoin_mempool_blocksbitcoin_mining_poolsbitcoin_network_statusbitcoin_nowbitcoin_sanctions_screenbitcoin_transaction_aml_checkbitcoin_transaction_etabitcoin_transaction_statusbitcoin_whale_stats_24hbitcoin_whales_livecheck_outputsdiamond_budgetdiamond_catalogevm_sanctions_screenlightning_decode_invoiceplan_cpfprecommendscoresearchverifywatch_bitcoin_addresswhale_geopolitics_report
MCP Registry declaration
- Registry name:
dev.workers.btc-intel.diamond/bitcoin-intel - Declared version: 13.3.0
- Status: active
- Declared hosts:
diamond.btc-intel.workers.dev
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:dev.workers.btc-intel.diamond/bitcoin-intel", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.workers.btc-intel.diamond/bitcoin-intel?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).