Skip to content

MCP servers › dev.workers.btc-intel.diamond › bitcoin-intel

MCP server · registry snapshot 2026-11-13 · last tested 2026-11-13

bitcoin-intel MCP server

Registry name dev.workers.btc-intel.diamond/bitcoin-intel

Diamond Bitcoin Intelligence — the publisher's title

by diamond.btc-intel.workers.dev · domain (the registry's namespace rule)Website ↗

Bitcoin MCP: fees, tx proofs, address checks. Pay per call by x402, Lightning or a prepaid pass. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-13version 13.3.0streamable HTTP40 tools

Summary

dev.workers.btc-intel.diamond/bitcoin-intel is a remote MCP server listed in the official MCP registry at version 13.3.0, under the namespace of the domain diamond.btc-intel.workers.dev. On 2026-11-13 ProtocolProbe connected to it in read-only mode and read its inventory: 40 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
40
Last tested
2026-11-13

Tool list size

16,117 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (40 tools). Counted with Anthropic's token counter on 2026-11-13, from the tool list we read on 2026-11-13. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-13 (diamond.btc-intel.workers.dev), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (13.3.0).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-13
Mode
read-only (no tool calls)
Latest version
13.3.0, published 2026-11-13 (registry, as of the 2026-11-13 snapshot)
First listed version
2026-11-07 (earliest version still in the registry; older removed versions would be earlier)
Version history
4 versions listed, 2026-11-07 to 2026-11-13; 4 in the 90 days before the 2026-11-13 snapshot; 1 marked deprecated.
Most recent 4 versions
  • 13.3.0 · 2026-11-13
  • 13.2.1 · 2026-11-11
  • 13.2.0 · 2026-11-10 · deprecated
  • 13.1.0 · 2026-11-07
(versions still listed in the registry only)
Registry data
snapshot 2026-11-13
Package and repository
checked 2026-11-13
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 13.2.1 (published 2026-11-11) → 13.3.0 (published 2026-11-13), between the registry lists of 2026-11-12 and 2026-11-13.

No release note: the registry entry links no GitHub repository.

Source: the official MCP Registry list on 2026-11-12 and on 2026-11-13; release notes from the GitHub Releases API, checked 2026-11-13.

What it is

What does this server offer?

Observed inventory
40tools
0resources
0prompts

None of its 40 tools are described as changing anything. For 40 the reading was uncertain, so no mark is shown.

  • diamond_catalogon 1 other server

    “Free.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    Takes no inputs.

  • bitcoin_sanctions_screenon 1 other server

    “Free.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    1 input, 1 required
    • addressstringrequired“Bitcoin mainnet address (bc1..., 1...”
  • bitcoin_address_riskon 1 other server

    “Screens one Bitcoin address: OFAC sanctions, ransomware payment lists, ownership clusters, sweeper bots and laundering-pattern cases seen by this node.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • addressstringrequired“Bitcoin mainnet address (bc1..., 1...”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_market_pulseon 1 other server

    “Live: fee rates (1 block to 1 day), mempool, last 24 h whale transactions and AML cases from this node, implied BTC/USD.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    3 inputs
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • whale_geopolitics_reporton 1 other server

    “One day's report: whale flows vs world news, lagged correlations, laundering patterns, headlines and the analyst brief (JSON).”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs
    • datestring“YYYY-MM-DD, last 90 days.”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • watch_bitcoin_addresson 1 other server

    “Alerts for 30 days on every confirmed transaction paying to or spending from the address: private feed (web, JSON, RSS) and phone push.”

    Publisher declares: read-only no · idempotent no · open-world no

    5 inputs, 1 required
    • addressstringrequired“Bitcoin mainnet address (bc1..., 1...”
    • feedstring“Optional: an existing Address Watch feed id to add to or extend”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_batch_risk

    “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.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • addressesarrayrequired“1 to 25 Bitcoin mainnet addresses (bc1..., 1...”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • “Free.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    1 input, 1 required
    • querystringrequired“Keywords for Diamond's service catalog.”
  • “Analyze one to 25 buyer-supplied transaction sizes against a per-transaction fee cap.”

    Publisher declares: read-only no · idempotent yes · open-world yes

    4 inputs, 1 required
    • planstringrequired“Per-transaction fee cap in sats, colon, and one to 25 comma-separated transaction sizes in vbytes.”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • “Generate a verified Bitcoin Core Merkle inclusion receipt for one to five transactions in one retained block.”

    Publisher declares: read-only no · idempotent yes · open-world yes

    4 inputs, 1 required
    • locatorstringrequired“64-character block hash, colon, and one to five comma-separated unique transaction ids in that block.”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • “Return Diamond's existing heuristic risk level and findings for one Bitcoin address.”

    Publisher declares: read-only no · idempotent yes · open-world yes

    4 inputs, 1 required
    • addressstringrequired“Bitcoin mainnet address (bc1..., 1...”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • “Free.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    2 inputs, 1 required
    • taskstringrequired
    • max_usdcnumber“Optional per-call USDC budget for service selection.”
Show 28 more tools
  • check_outputs

    “Batch output status for one to 25 unique Bitcoin outpoints (txid:vout pairs).”

    Publisher declares: read-only no · idempotent yes · open-world yes

    4 inputs, 1 required
    • outpointsstringrequired“One to 25 unique comma-separated txid:vout pairs.”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • plan_cpfp

    “CPFP budget scenarios for a mempool transaction and its ancestors.”

    Publisher declares: read-only no · idempotent yes · open-world yes

    4 inputs, 1 required
    • packagestringrequired“txid:target_sat_vb:child_vbytes[,child_vbytes...].”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_fee_estimates

    “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.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    3 inputs
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_latest_block

    “The latest Bitcoin block: height, hash, age, transaction count, total fees, fee-rate percentiles, size, weight and subsidy.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    3 inputs
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_network_status

    “Bitcoin network status: height, difficulty, estimated hashrate, the next difficulty adjustment (blocks left, estimated change) and the next halving (blocks left, estimated date).”

    Publisher declares: read-only yes · idempotent yes · open-world no

    3 inputs
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_decode_transaction

    “Decode a raw Bitcoin transaction (hex): txid, wtxid, size, vsize, weight, inputs, outputs with addresses and values, SegWit and RBF flags.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • hexstringrequired“Raw transaction as hex”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_address_info

    “Validate and classify one Bitcoin address: valid or not (with the reason), type (P2PKH, P2SH, P2WPKH, P2WSH, P2TR), witness version and scriptPubKey.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • addrstringrequired“A Bitcoin address to validate”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • lightning_decode_invoice

    “Decode a Lightning BOLT11 invoice: amount, description, payee node, payment hash, creation and expiry time, whether it has expired, route hints.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • invoicestringrequired“A Lightning BOLT11 invoice (lnbc...)”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_transaction_status

    “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).”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • txidstringrequired“Transaction id (64 hex characters)”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_decode_psbt

    “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.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • psbtstringrequired“A PSBT in base64 (URL-encode + as %2B)”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_now

    “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 Co…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    3 inputs
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_mempool_blocks

    “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, th…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    3 inputs
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_fee_history

    “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 getblo…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    3 inputs
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_block_header

    “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.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • block_idstringrequired“Block height (for example 974000) or block hash (64 hex characters)”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_block_stats

    “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, SegW…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • block_idstringrequired“Block height (for example 974000) or block hash (64 hex characters)”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_mining_pools

    “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.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    3 inputs
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_decode_script

    “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).”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • scriptstringrequired“A Bitcoin script as hex”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_transaction_eta

    “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…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • txidstringrequired“Transaction id (64 hex characters)”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_whales_live

    “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 to…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    3 inputs
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_aml_live

    “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 …”

    Publisher declares: read-only yes · idempotent yes · open-world no

    3 inputs
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_transaction_aml_check

    “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…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • txidstringrequired“Transaction id (64 hex characters)”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_aml_stats_24h

    “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.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    3 inputs
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • bitcoin_whale_stats_24h

    “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.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    3 inputs
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • base_token_checkon 4 other servers

    “Base token safety check for one ERC-20 contract: proxy/upgradeable, owner and whether it is renounced, mint, blacklist, pause, fee/tax and limit switches found in the bytecode, DEX liquidity, pair ag…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • tokenstringrequired“ERC-20 token contract address on Base (0x + 40 hex characters)”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • evm_sanctions_screen

    “OFAC SDN sanctions screen for one EVM address (0x...): listed or not, with the entry name, programs and currencies; covers every 0x address on the U.S.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • evm_addressstringrequired“An EVM address (0x + 40 hex characters): a wallet or a contract”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • base_tx_decode

    “Decode one Base transaction: success, failed or pending, confirmations, block time, fee, ETH value and every ERC-20 transfer in it (token, from, to, amount) - verify a payment.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • base_txstringrequired“A Base transaction hash (0x + 64 hex characters)”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • base_wallet_check

    “Base wallet snapshot for one address: ETH, USDC, EURC, DAI, cbBTC, WETH and VIRTUAL balances, transaction count, contract or wallet, and an OFAC sanctions check.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • evm_addressstringrequired“An EVM address (0x + 40 hex characters): a wallet or a contract”
    • pay_withstring“Optional.”
    • l402string“Optional.”
    • passstring“Optional.”
  • diamond_budget

    “Free.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    3 inputs
    • budgetstring“b089 = US$0.89 (US$1.00 of calls, default), b499 = US$4.99 (US$5.50), b999 = US$9.99 (US$11.50)”
    • pay_withstring“How the budget will be paid (default usdc).”
    • passstring“Optional.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-13.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
99% of 136
Tools with a description
100% of 40
Typical description length
257 characters

The tool set

Counted from the listing

Tools
40
Size of the list
about 11,483 tokens for an agent to load (characters ÷ 4)
Naming
35 of 40 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 40 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-13 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://diamond.btc-intel.workers.dev/api/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "bitcoin-intel": {
      "url": "https://diamond.btc-intel.workers.dev/api/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "bitcoin-intel": {
      "type": "http",
      "url": "https://diamond.btc-intel.workers.dev/api/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"bitcoin-intel","type":"http","url":"https://diamond.btc-intel.workers.dev/api/mcp"}'
Claude Code
claude mcp add --transport http bitcoin-intel https://diamond.btc-intel.workers.dev/api/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "bitcoin-intel": {
      "type": "streamableHttp",
      "url": "https://diamond.btc-intel.workers.dev/api/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "bitcoin-intel": {
      "httpUrl": "https://diamond.btc-intel.workers.dev/api/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.bitcoin-intel]
url = "https://diamond.btc-intel.workers.dev/api/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "bitcoin-intel": {
      "url": "https://diamond.btc-intel.workers.dev/api/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://diamond.btc-intel.workers.dev/api/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-13. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-13. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-13. Source: read 2026-11-13.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-13. Source: read 2026-11-13.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint diamond.btc-intel.workers.dev/api/mcpSession openedmatchesour test · 2026-11-13
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-13

Tool list changes

Our reads compared · no tool called

Hosted endpoint diamond.btc-intel.workers.dev/api/mcp

2 of 2 comparisons between consecutive reads showed a change (3 reads, 2026-11-07 to 2026-11-13; versions 13.1.0 to 13.3.0).

Last change seen between our reads on 2026-11-12 (version 13.2.1) and 2026-11-13 (version 13.3.0).

Added (5):

base_token_checkbase_tx_decodebase_wallet_checkdiamond_budgetevm_sanctions_screen

Changed (31) (25 shown):

analyze: input schemabitcoin_address_info: input schemabitcoin_address_risk: input schemabitcoin_aml_live: input schemabitcoin_aml_stats_24h: input schemabitcoin_batch_risk: input schemabitcoin_block_header: input schemabitcoin_block_stats: input schemabitcoin_decode_psbt: input schemabitcoin_decode_script: input schemabitcoin_decode_transaction: input schemabitcoin_fee_estimates: input schemabitcoin_fee_history: input schemabitcoin_latest_block: input schemabitcoin_market_pulse: input schemabitcoin_mempool_blocks: input schemabitcoin_mining_pools: input schemabitcoin_network_status: input schemabitcoin_now: input schemabitcoin_transaction_aml_check: input schemabitcoin_transaction_eta: input schemabitcoin_transaction_status: input schemabitcoin_whale_stats_24h: input schemabitcoin_whales_live: input schemacheck_outputs: input schema

and 6 more.

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-13 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-13. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about dev.workers.btc-intel.diamond/bitcoin-intel

Answered from the data above

Who publishes dev.workers.btc-intel.diamond/bitcoin-intel?

The registry ties the namespace dev.workers.btc-intel.diamond to the domain diamond.btc-intel.workers.dev; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does dev.workers.btc-intel.diamond/bitcoin-intel need an API key or sign-in?

It opened a session without any credential on 2026-11-13. The registry entry declares no required credential; no declaration is not a guarantee.

Has dev.workers.btc-intel.diamond/bitcoin-intel been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (no operator permission)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-13
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-13, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 4,113 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 40 tools, 0 resources, 0 prompts.
  4. 7,782 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-13; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-13
MCP capability
tools
our test · 2026-11-13
Transport
streamable HTTP
registry · 2026-11-13
Required credentials
none declared
registry · 2026-11-13 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-13
Lifecycle status
registry · 2026-11-13
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-13

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “dev.workers.btc-intel.diamond/bitcoin-intel: MCP server record.” Data checked 2026-11-13. https://protocolprobe.com/mcp/servers/dev.workers.btc-intel.diamond/bitcoin-intel

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/dev.workers.btc-intel.diamond/bitcoin-intel)](https://protocolprobe.com/mcp/servers/dev.workers.btc-intel.diamond/bitcoin-intel)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology