Skip to content

Diamond Bitcoin Intelligence MCP server

dev.workers.btc-intel.diamond/bitcoin-inteldiamond.btc-intel.workers.devstreamable-httpv13.3.0Scanned

Bitcoin MCP: fees, tx proofs, address checks. Pay per call by x402, Lightning or a prepaid pass.

35 tools: 1 do something that can't be undone, 30 change things and 4 only read.

Tools: 0 delete, 1 irreversible, 30 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 5
  • Can send data out · 0
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Diamond Bitcoin Intelligence MCP server can do

The Diamond Bitcoin Intelligence MCP server is published by diamond.btc-intel.workers.dev, a domain the MCP Registry verified. It has 35 tools. It can do things that cannot be undone, such as sending, paying or publishing (verify) and create or change data (30 tools: diamond_catalog, bitcoin_sanctions_screen, bitcoin_address_risk, bitcoin_market_pulse and 26 more), but cannot delete data. 4 tools only read.

5 tools bring in text other people can write (analyze, verify, score and 2 more).

The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 13, 2026, version 13.3.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

35 tools

Can't be undone 1Claude Code: ask
  • verifyGenerate a verified Bitcoin Core Merkle inclusion receipt for one to five transactions in one retained block.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    • The description says "irreversible".

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Generate a verified Bitcoin Core Merkle inclusion receipt for one to five transactions in one retained block. locator=blockhash:txid[,txid...]. Verify against a trusted header chain. Does not establish unspentness or irreversible finality. Price: 20 sats or US$0.02 (USDC) per call.

    Annotations the server declares

    • title: Verify transaction inclusion receipt
    • readOnlyHint: false
    • idempotentHint: true
    • openWorldHint: true
Changes things 30Claude Code: ask
  • analyzeAnalyze one to 25 buyer-supplied transaction sizes against a per-transaction fee cap.Reads text others write1 finding

    Why it is in this group

    • The name "analyze" says "analyze": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "analyze" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"idempotentHint":true,"openWorldHint":true}; The name "analyze" says "analyze": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Analyze one to 25 buyer-supplied transaction sizes against a per-transaction fee cap. plan=budget_sats:vbytes[,vbytes...], e.g. 1000:140,220,350. Uses fresh node fee estimates, rounds up to whole sats, and returns the fastest observed estimate fitting each cap. Estimates do not guarantee confirmation. No transaction is signed or broadcast. Price: 20 sats or US$0.01 (USDC) per call.

    Annotations the server declares

    • title: Batch transaction fee budget analysis
    • readOnlyHint: false
    • idempotentHint: true
    • openWorldHint: true
  • bitcoin_address_riskScreens one Bitcoin address: OFAC sanctions, ransomware payment lists, ownership clusters, sweeper bots and laundering-pattern cases seen by this node.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Screens one Bitcoin address: OFAC sanctions, ransomware payment lists, ownership clusters, sweeper bots and laundering-pattern cases seen by this node. Price: 300 sats or US$0.25 (USDC) per call.

    Annotations the server declares

    • title: Bitcoin address risk check
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_aml_liveLaundering-pattern cases (score 40 or more) this node scored in the last 60 minutes: up to 25, highest score first, with the rules that fired (peel chains, post-mix consolidation, …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Laundering-pattern cases (score 40 or more) this node scored in the last 60 minutes: up to 25, highest score first, with the rules that fired (peel chains, post-mix consolidation, structuring, rapid layering, risky-cluster payments and more). Heuristic, not proof. Paid per call. Price: 30 sats or US$0.03 (USDC) per call.

    Annotations the server declares

    • title: AML cases, last 60 minutes
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_aml_stats_24hLaundering-pattern statistics for the last 24 hours from this node: cases by score band, by rule and by severity, flagged cases per hour, US$ in flagged cases and the 5 largest fla…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Laundering-pattern statistics for the last 24 hours from this node: cases by score band, by rule and by severity, flagged cases per hour, US$ in flagged cases and the 5 largest flagged cases. Heuristic, not proof. Paid per call. Price: 20 sats or US$0.02 (USDC) per call.

    Annotations the server declares

    • title: AML pattern statistics, last 24 hours
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_batch_riskScreens up to 25 Bitcoin addresses in one call: OFAC sanctions, ransomware payment lists, ownership clusters, sweeper bots and laundering-pattern cases for each, plus a summary of …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Screens up to 25 Bitcoin addresses in one call: OFAC sanctions, ransomware payment lists, ownership clusters, sweeper bots and laundering-pattern cases for each, plus a summary of the flagged ones. For counterparty and withdrawal-address due diligence; about 60% cheaper per address than single checks. Price: 3000 sats or US$2.5 (USDC) per call.

    Annotations the server declares

    • title: Bitcoin batch risk check (up to 25 addresses)
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_block_headerHeader of any Bitcoin block by height or hash: hash, previous and next hash, merkle root, time, median time past, bits, difficulty, nonce, version, tx count, confirmations.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Header of any Bitcoin block by height or hash: hash, previous and next hash, merkle root, time, median time past, bits, difficulty, nonce, version, tx count, confirmations. Paid per call. Price: 2 sats or US$0.002 (USDC) per call.

    Annotations the server declares

    • title: Bitcoin block header
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_block_statsStatistics for one recent Bitcoin block (this pruned node keeps roughly the last 10,000) by height or hash: tx count, total fees, fee-rate percentiles, size, weight, subsidy, input…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Statistics for one recent Bitcoin block (this pruned node keeps roughly the last 10,000) by height or hash: tx count, total fees, fee-rate percentiles, size, weight, subsidy, inputs and outputs, SegWit share, and the miner (coinbase tag and pool). Paid per call. Price: 3 sats or US$0.003 (USDC) per call.

    Annotations the server declares

    • title: Bitcoin block statistics and miner
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_decode_psbtDecode and analyze a PSBT (base64): inputs, outputs, fee and fee rate when the input data is present, estimated vsize, signatures still missing and the next step.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Decode and analyze a PSBT (base64): inputs, outputs, fee and fee rate when the input data is present, estimated vsize, signatures still missing and the next step. Nothing is signed or broadcast. Paid per call. Price: 5 sats or US$0.005 (USDC) per call.

    Annotations the server declares

    • title: Decode and analyze a PSBT
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_decode_scriptDecode a Bitcoin script from hex (scriptPubKey, redeem or witness script): type, asm, descriptor, address, and the P2SH and P2WSH addresses that wrap it (Bitcoin Core decodescript)…1 finding

    Why it is in this group

    • The input takes a statement or command to run (input.script), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "bitcoin_decode_script" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.script), which can change anything it can reach.

      What this check looks for
    Description, as the server wrote it
    Decode a Bitcoin script from hex (scriptPubKey, redeem or witness script): type, asm, descriptor, address, and the P2SH and P2WSH addresses that wrap it (Bitcoin Core decodescript). Paid per call. Price: 2 sats or US$0.002 (USDC) per call.

    Annotations the server declares

    • title: Decode a Bitcoin script
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_decode_transactionDecode a raw Bitcoin transaction (hex): txid, wtxid, size, vsize, weight, inputs, outputs with addresses and values, SegWit and RBF flags.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Decode a raw Bitcoin transaction (hex): txid, wtxid, size, vsize, weight, inputs, outputs with addresses and values, SegWit and RBF flags. Nothing is broadcast. Paid per call. Price: 3 sats or US$0.003 (USDC) per call.

    Annotations the server declares

    • title: Decode a Bitcoin transaction
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_fee_estimatesBitcoin fee estimates right now: sat/vB to confirm within 1, 2, 3, 6, 12, 24, 144, 504 and 1008 blocks (Bitcoin Core estimatesmartfee on this node), plus mempool size and minimum r…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Bitcoin fee estimates right now: sat/vB to confirm within 1, 2, 3, 6, 12, 24, 144, 504 and 1008 blocks (Bitcoin Core estimatesmartfee on this node), plus mempool size and minimum relay fee. Paid per call. Price: 3 sats or US$0.003 (USDC) per call.

    Annotations the server declares

    • title: Bitcoin fee estimates
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_fee_historyFee rates actually paid in the last 12 Bitcoin blocks: per block the 10th to 90th percentile sat/vB, total fees, tx count, fullness and time, plus 12-block averages and the trend (…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Fee rates actually paid in the last 12 Bitcoin blocks: per block the 10th to 90th percentile sat/vB, total fees, tx count, fullness and time, plus 12-block averages and the trend (Bitcoin Core getblockstats). Paid per call. Price: 5 sats or US$0.005 (USDC) per call.

    Annotations the server declares

    • title: Fee rates paid in the last 12 blocks
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_latest_blockThe latest Bitcoin block: height, hash, age, transaction count, total fees, fee-rate percentiles, size, weight and subsidy.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The latest Bitcoin block: height, hash, age, transaction count, total fees, fee-rate percentiles, size, weight and subsidy. Paid per call. Price: 3 sats or US$0.003 (USDC) per call.

    Annotations the server declares

    • title: Latest Bitcoin block
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_market_pulseLive: fee rates (1 block to 1 day), mempool, last 24 h whale transactions and AML cases from this node, implied BTC/USD.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Live: fee rates (1 block to 1 day), mempool, last 24 h whale transactions and AML cases from this node, implied BTC/USD. Price: 20 sats or US$0.02 (USDC) per call.

    Annotations the server declares

    • title: Bitcoin market pulse
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_mempool_blocksProjected next Bitcoin blocks from this node's live mempool, ordered by cluster-mempool chunk fee rate: for each of the next 4 blocks the tx count, vsize, total fees and min / medi…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Projected next Bitcoin blocks from this node's live mempool, ordered by cluster-mempool chunk fee rate: for each of the next 4 blocks the tx count, vsize, total fees and min / median / max sat/vB, the fee rate the next block needs, and a fee-rate histogram of the whole mempool. Paid per call. Price: 5 sats or US$0.005 (USDC) per call.

    Annotations the server declares

    • title: Projected next Bitcoin blocks
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_mining_poolsWhich mining pools found the last 144 Bitcoin blocks (about 24 hours), identified from coinbase tags: blocks and share per pool, plus the 10 latest blocks with their pool.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Which mining pools found the last 144 Bitcoin blocks (about 24 hours), identified from coinbase tags: blocks and share per pool, plus the 10 latest blocks with their pool. Paid per call. Price: 5 sats or US$0.005 (USDC) per call.

    Annotations the server declares

    • title: Mining pool share, last 144 blocks
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_nowBitcoin right now in one call: fee estimates (sat/vB for 1 to 1008 blocks), mempool size, the latest block and network status (hashrate, difficulty retarget, halving), from this no…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Bitcoin right now in one call: fee estimates (sat/vB for 1 to 1008 blocks), mempool size, the latest block and network status (hashrate, difficulty retarget, halving), from this node's own Bitcoin Core. Paid per call. Price: 8 sats or US$0.008 (USDC) per call.

    Annotations the server declares

    • title: Bitcoin right now: fees, mempool, block, network
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_sanctions_screenFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. Is this Bitcoin address on the OFAC SDN sanctions list or a known ransomware payment address? Exact list matches only. For ownership clusters, sweeper bots and laundering patterns use bitcoin_address_risk.

    Annotations the server declares

    • title: Bitcoin sanctions screen (free)
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_transaction_aml_checkAML check for one Bitcoin transaction: the laundering-pattern case this node logged for it in the last 30 days (score, level, rules fired such as peel chains, post-mix consolidatio…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    AML check for one Bitcoin transaction: the laundering-pattern case this node logged for it in the last 30 days (score, level, rules fired such as peel chains, post-mix consolidation, structuring), or a clear no-case answer. Heuristic, not proof. Paid per call. Price: 50 sats or US$0.05 (USDC) per call.

    Annotations the server declares

    • title: AML check for one Bitcoin transaction
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_transaction_etaConfirmation outlook for a Bitcoin transaction: its effective (cluster chunk) fee rate, the projected block it sits in, the fee rate the next block needs, and the RBF total fee or …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Confirmation outlook for a Bitcoin transaction: its effective (cluster chunk) fee rate, the projected block it sits in, the fee rate the next block needs, and the RBF total fee or CPFP child fee that would get it in. Confirmed ones (last 6 blocks) report confirmations. Paid per call. Price: 5 sats or US$0.005 (USDC) per call.

    Annotations the server declares

    • title: Confirmation outlook for a Bitcoin transaction
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_whale_stats_24hWhale flow statistics for the last 24 hours from this node: count and US$ volume of transactions of US$100,000 or more per hour, size bands, mempool vs block split and the 10 large…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Whale flow statistics for the last 24 hours from this node: count and US$ volume of transactions of US$100,000 or more per hour, size bands, mempool vs block split and the 10 largest transactions. Paid per call. Price: 10 sats or US$0.01 (USDC) per call.

    Annotations the server declares

    • title: Whale flow statistics, last 24 hours
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_whales_liveBitcoin transactions of US$100,000 or more this node saw in the last 10 minutes: up to 50, largest first (txid, BTC, US$, inputs, outputs, mempool or block, AML score), with the wi…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Bitcoin transactions of US$100,000 or more this node saw in the last 10 minutes: up to 50, largest first (txid, BTC, US$, inputs, outputs, mempool or block, AML score), with the window's count and totals. Paid per call. Price: 10 sats or US$0.01 (USDC) per call.

    Annotations the server declares

    • title: Whale transactions, last 10 minutes
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • check_outputsBatch output status for one to 25 unique Bitcoin outpoints (txid:vout pairs).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Batch output status for one to 25 unique Bitcoin outpoints (txid:vout pairs). Reports this node's chainstate and sequential mempool observations, value, script, confirmations and coinbase flag. Missing does not prove spent. No cryptographic unspentness proof or spendability guarantee; all-absent batches rejected before charging. Price: 20 sats or US$0.02 (USDC) per call.

    Annotations the server declares

    • title: Batch Bitcoin output status
    • readOnlyHint: false
    • idempotentHint: true
    • openWorldHint: true
  • diamond_catalogFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. Lists Diamond's paid Bitcoin intelligence tools with prices in sats and USD, payment methods (x402 USDC on Base, Lightning) and terms.

    Annotations the server declares

    • title: Diamond catalog (free)
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • lightning_decode_invoiceDecode a Lightning BOLT11 invoice: amount, description, payee node, payment hash, creation and expiry time, whether it has expired, route hints.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Decode a Lightning BOLT11 invoice: amount, description, payee node, payment hash, creation and expiry time, whether it has expired, route hints. Paid per call. Price: 2 sats or US$0.002 (USDC) per call.

    Annotations the server declares

    • title: Decode a Lightning invoice
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • plan_cpfpCPFP budget scenarios for a mempool transaction and its ancestors.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    CPFP budget scenarios for a mempool transaction and its ancestors. package=txid:target_sat_vb:child_vbytes[,child_vbytes...]. Up to 25 unique sizes; actual ancestor base fees, ceiling arithmetic and observed relay/mempool floors. Not transaction construction, package-policy validation, broadcast or a confirmation guarantee. Price: 20 sats or US$0.02 (USDC) per call.

    Annotations the server declares

    • title: CPFP child fee-budget scenarios
    • readOnlyHint: false
    • idempotentHint: true
    • openWorldHint: true
  • recommendFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. Use fees or fee_estimates for current fee estimates, fee_history for past blocks, or feeplan for transaction size scenarios. Other tasks cover inclusion, outputs, CPFP, risk, monitoring, reports and market data. Compares the published per-call price with an optional budget. Creates no payment.

    Annotations the server declares

    • title: Choose a Diamond service by task and price
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • scoreReturn Diamond's existing heuristic risk level and findings for one Bitcoin address.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "score" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "return": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Return Diamond's existing heuristic risk level and findings for one Bitcoin address. Combines public list matches and node observations. Flags require review; a clean result does not certify safety, legal compliance or ownership. Price: 300 sats or US$0.25 (USDC) per call.

    Annotations the server declares

    • title: Address-risk observations
    • readOnlyHint: false
    • idempotentHint: true
    • openWorldHint: true
  • watch_bitcoin_addressAlerts for 30 days on every confirmed transaction paying to or spending from the address: private feed (web, JSON, RSS) and phone push.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Alerts for 30 days on every confirmed transaction paying to or spending from the address: private feed (web, JSON, RSS) and phone push. Returns the feed links. Price: 1000 sats or US$1 (USDC) per call.

    Annotations the server declares

    • title: Watch a Bitcoin address (30 days)
    • readOnlyHint: false
    • idempotentHint: false
    • openWorldHint: false
  • whale_geopolitics_reportOne day's report: whale flows vs world news, lagged correlations, laundering patterns, headlines and the analyst brief (JSON).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    One day's report: whale flows vs world news, lagged correlations, laundering patterns, headlines and the analyst brief (JSON). Price: 1000 sats or US$0.8 (USDC) per call.

    Annotations the server declares

    • title: Whale x Geopolitics daily report
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • bitcoin_address_infoValidate and classify one Bitcoin address: valid or not (with the reason), type (P2PKH, P2SH, P2WPKH, P2WSH, P2TR), witness version and scriptPubKey.No findings

    Why it is in this group

    • The description's first verb is "validate": a word for reading.
    Description, as the server wrote it
    Validate and classify one Bitcoin address: valid or not (with the reason), type (P2PKH, P2SH, P2WPKH, P2WSH, P2TR), witness version and scriptPubKey. Paid per call. Price: 2 sats or US$0.002 (USDC) per call.

    Annotations the server declares

    • title: Validate a Bitcoin address
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_network_statusBitcoin network status: height, difficulty, estimated hashrate, the next difficulty adjustment (blocks left, estimated change) and the next halving (blocks left, estimated date).No findings

    Why it is in this group

    • The name "bitcoin_network_status" says "status": a word for reading.
    Description, as the server wrote it
    Bitcoin network status: height, difficulty, estimated hashrate, the next difficulty adjustment (blocks left, estimated change) and the next halving (blocks left, estimated date). Paid per call. Price: 3 sats or US$0.003 (USDC) per call.

    Annotations the server declares

    • title: Bitcoin network status
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • bitcoin_transaction_statusStatus of one Bitcoin transaction as seen by this node: in the mempool (fee rate, age, RBF, estimated blocks to confirm) or confirmed in one of the last 6 blocks (confirmations).No findings

    Why it is in this group

    • The name "bitcoin_transaction_status" says "status": a word for reading.
    Description, as the server wrote it
    Status of one Bitcoin transaction as seen by this node: in the mempool (fee rate, age, RBF, estimated blocks to confirm) or confirmed in one of the last 6 blocks (confirmations). Paid per call. Price: 5 sats or US$0.005 (USDC) per call.

    Annotations the server declares

    • title: Bitcoin transaction status
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:20 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
36
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 36 tools that change things (1 irreversible, 35 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://diamond.btc-intel.workers.dev/api/mcp: tools/list returned 40 tools to an anonymous client, including verify (irreversible), diamond_catalog (write), bitcoin_sanctions_screen (write), bitcoin_address_risk (write), bitcoin_market_pulse (write) and 31 more

    What this check looks for

Posture changes

  1. Nov 15, 2026
    • Tools that change things, listed without credentials: 31 to 36

Findings

Matches of fixed checks, with the text they matched.

3 warn
  • The server marks "analyze" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"idempotentHint":true,"openWorldHint":true}; The name "analyze" says "analyze": a word for reading.

    What this check looks for
  • Warnscore

    The server marks "score" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "return": a word for reading.

    What this check looks for
  • The server marks "bitcoin_decode_script" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.script), which can change anything it can reach.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 31 -> 36.View diff
    • Tools that change things, listed without credentials: 31 to 36
  2. Tools31 changed.~31 changedView diff
  3. Tools21 added, 1 changed.+21 added~1 changedView diff

Install

Pinned to version 13.3.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http bitcoin-intel https://diamond.btc-intel.workers.dev/api/mcp
claude mcp add --transport http bitcoin-intel https://diamond.btc-intel.workers.dev/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__bitcoin-intel__search",
      "mcp__bitcoin-intel__bitcoin_network_status",
      "mcp__bitcoin-intel__bitcoin_address_info",
      "mcp__bitcoin-intel__bitcoin_transaction_status"
    ],
    "ask": [
      "mcp__bitcoin-intel__diamond_catalog",
      "mcp__bitcoin-intel__bitcoin_sanctions_screen",
      "mcp__bitcoin-intel__bitcoin_address_risk",
      "mcp__bitcoin-intel__bitcoin_market_pulse",
      "mcp__bitcoin-intel__whale_geopolitics_report",
      "mcp__bitcoin-intel__watch_bitcoin_address",
      "mcp__bitcoin-intel__bitcoin_batch_risk",
      "mcp__bitcoin-intel__analyze",
      "mcp__bitcoin-intel__verify",
      "mcp__bitcoin-intel__score",
      "mcp__bitcoin-intel__recommend",
      "mcp__bitcoin-intel__check_outputs",
      "mcp__bitcoin-intel__plan_cpfp",
      "mcp__bitcoin-intel__bitcoin_fee_estimates",
      "mcp__bitcoin-intel__bitcoin_latest_block",
      "mcp__bitcoin-intel__bitcoin_decode_transaction",
      "mcp__bitcoin-intel__lightning_decode_invoice",
      "mcp__bitcoin-intel__bitcoin_decode_psbt",
      "mcp__bitcoin-intel__bitcoin_now",
      "mcp__bitcoin-intel__bitcoin_mempool_blocks",
      "mcp__bitcoin-intel__bitcoin_fee_history",
      "mcp__bitcoin-intel__bitcoin_block_header",
      "mcp__bitcoin-intel__bitcoin_block_stats",
      "mcp__bitcoin-intel__bitcoin_mining_pools",
      "mcp__bitcoin-intel__bitcoin_decode_script",
      "mcp__bitcoin-intel__bitcoin_transaction_eta",
      "mcp__bitcoin-intel__bitcoin_whales_live",
      "mcp__bitcoin-intel__bitcoin_aml_live",
      "mcp__bitcoin-intel__bitcoin_transaction_aml_check",
      "mcp__bitcoin-intel__bitcoin_aml_stats_24h",
      "mcp__bitcoin-intel__bitcoin_whale_stats_24h"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bitcoin-intel. Review it before you use it.

Capability tags behind 5 rules
  • mcp__bitcoin-intel__analyze untrusted-input
  • mcp__bitcoin-intel__verify untrusted-input
  • mcp__bitcoin-intel__score untrusted-input
  • mcp__bitcoin-intel__check_outputs untrusted-input
  • mcp__bitcoin-intel__plan_cpfp untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.workers.btc-intel.diamond/bitcoin-intel/verify?hash=caa7f34c341c4fdb4b63f111c12f5471f661d174ef6cf1d45077ecf39d96290b" | jq -e '.changed == false'

Pinned hash caa7f34c341c, from Nov 13, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.workers.btc-intel.diamond/bitcoin-intel/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.workers.btc-intel.diamond/bitcoin-intel
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.workers.btc-intel.diamond/bitcoin-intel.svg)](https://radar.anlyon.com/servers/dev.workers.btc-intel.diamond/bitcoin-intel)

Source: MCP Registry. Synced Nov 13, 2026, 04:17 UTC.

Diamond Bitcoin Intelligence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Diamond Bitcoin Intelligence MCP server safe?

No scan can promise that. What its definitions show: 35 tools, 31 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Diamond Bitcoin Intelligence MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Diamond Bitcoin Intelligence MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: verify.

What tools does the Diamond Bitcoin Intelligence MCP server have?

35 tools: 1 irreversible, 30 write, 4 read. verify, diamond_catalog, bitcoin_sanctions_screen, bitcoin_address_risk, bitcoin_market_pulse, whale_geopolitics_report, watch_bitcoin_address, bitcoin_batch_risk and 27 more.

Does the Diamond Bitcoin Intelligence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Diamond Bitcoin Intelligence MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Diamond Bitcoin Intelligence MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.