Diamond Bitcoin Intelligence
REMOTE · DIAMOND.TAIL1B5F86.TS.NET
Free Bitcoin sanctions screen; paid address risk checks, market pulse, whale reports and alerts.
Available components
Last scanned (10 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1966 tokens (~140/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
- Structured output schemas are declared (43% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Tool “recommend” rewrote its description, which is the text the model reads security
- Schema quality: 1565 → 1966 ▼ functional
- Tool coverage: 33% → 43% ▲ functional
- New tool “check_outputs” functional
- New tool “plan_cpfp” functional
- 3 Nov 26 +1
- Schema quality: 955 → 1565 ▼ functional
- First check of Tool coverage: 33 functional
- New tool “analyze” functional
- New tool “recommend” functional
- New tool “score” functional
- New tool “search” functional
- New tool “verify” functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- Schema quality: 780 → 955 ▼ functional
- New tool “bitcoin_batch_risk” functional
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://diamond.tail1b5f86.ts.net/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_CHACHA20_POLY1305_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=diamond.tail1b5f86.ts.net | CN=YE2,O=Let's Encrypt,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 652e977e01b5200c741d3187a30ecba401d |
| SANs: diamond.tail1b5f86.ts.net | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of diamond.tail1b5f86.ts.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| net. | DS published | 37331 | 13 | Verified |
| ts.net. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://diamond.tail1b5f86.ts.net/api/mcp | Verified | 200 | |
| http (plaintext) | http://diamond.tail1b5f86.ts.net/api/mcp | HTTPS enforced | 302 | https://diamond.tail1b5f86.ts.net/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze Batch transaction fee budget analysis ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| l402 | string | – | Optional. After paying the Lightning invoice: '<token>:<preimage>'. |
| pay_with | string | – | Optional. 'lightning' returns a BOLT11 invoice and a token instead of the x402 payment request. |
| plan | string | yes | Per-transaction fee cap in sats, colon, and one to 25 comma-separated transaction sizes in vbytes. Example 1000:140,220,350. Fee cap 1..100000000; each size 60..100000. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| plans | array | yes | – |
| product | string | yes | – |
No examples provided.
bitcoin_address_risk Bitcoin address risk check ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Bitcoin mainnet address (bc1..., 1... or 3...) |
| l402 | string | – | Optional. After paying the Lightning invoice: '<token>:<preimage>'. |
| pay_with | string | – | Optional. 'lightning' returns a BOLT11 invoice and a token instead of the x402 payment request. |
No output schema declared.
No examples provided.
bitcoin_batch_risk Bitcoin batch risk check (up to 25 addresses) ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | 1 to 25 Bitcoin mainnet addresses (bc1..., 1... or 3...); a comma-separated string also works |
| l402 | string | – | Optional. After paying the Lightning invoice: '<token>:<preimage>'. |
| pay_with | string | – | Optional. 'lightning' returns a BOLT11 invoice and a token instead of the x402 payment request. |
No output schema declared.
No examples provided.
bitcoin_market_pulse Bitcoin market pulse ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| l402 | string | – | Optional. After paying the Lightning invoice: '<token>:<preimage>'. |
| pay_with | string | – | Optional. 'lightning' returns a BOLT11 invoice and a token instead of the x402 payment request. |
No output schema declared.
No examples provided.
bitcoin_sanctions_screen Bitcoin sanctions screen (free) ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Bitcoin mainnet address (bc1..., 1... or 3...) |
No output schema declared.
No examples provided.
check_outputs Batch Bitcoin output status ~191
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.
| Name | Type | Req | Description |
|---|---|---|---|
| l402 | string | – | Optional. After paying the Lightning invoice: '<token>:<preimage>'. |
| outpoints | string | yes | One to 25 unique comma-separated txid:vout pairs. txid is 64 hex characters; vout 0..65535. URLs disclose these public outpoints to Diamond. |
| pay_with | string | – | Optional. 'lightning' returns a BOLT11 invoice and a token instead of the x402 payment request. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| mempool_queries_atomic | boolean | yes | – |
| outputs | array | yes | – |
| product | string | yes | – |
No examples provided.
diamond_catalog Diamond catalog (free) ~39
Free. Lists Diamond's paid Bitcoin intelligence tools with prices in sats and USD, payment methods (x402 USDC on Base, Lightning) and terms.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plan_cpfp CPFP child fee-budget scenarios ~205
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.
| Name | Type | Req | Description |
|---|---|---|---|
| l402 | string | – | Optional. After paying the Lightning invoice: '<token>:<preimage>'. |
| package | string | yes | txid:target_sat_vb:child_vbytes[,child_vbytes...]. Target 0.001..10000 sat/vB (up to 3 decimals), one to 25 unique child sizes of 60..100000 vbytes. |
| pay_with | string | – | Optional. 'lightning' returns a BOLT11 invoice and a token instead of the x402 payment request. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| plans | array | yes | – |
| product | string | yes | – |
No examples provided.
recommend Choose a Diamond service by task and price ~74
Free. Choose a Diamond tool for fees, inclusion, outputs, CPFP, risk, monitoring, daily reports or market data. Compares the published per-call price with an optional budget. Creates no payment.
| Name | Type | Req | Description |
|---|---|---|---|
| max_usdc | number | – | Optional per-call USDC budget for service selection. |
| task | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_tool | string | yes | – |
| payment_created | boolean | yes | – |
| scope | string | yes | – |
No examples provided.
score Address-risk observations ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Bitcoin mainnet address (bc1..., 1... or 3...) |
| l402 | string | – | Optional. After paying the Lightning invoice: '<token>:<preimage>'. |
| pay_with | string | – | Optional. 'lightning' returns a BOLT11 invoice and a token instead of the x402 payment request. |
No output schema declared.
No examples provided.
search Search Diamond services ~37
Free. Search Diamond's available tools, use cases, input descriptions and published prices.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Keywords for Diamond's service catalog. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
| scope | string | yes | – |
No examples provided.
verify Verify transaction inclusion receipt ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| l402 | string | – | Optional. After paying the Lightning invoice: '<token>:<preimage>'. |
| locator | string | yes | 64-character block hash, colon, and one to five comma-separated unique transaction ids in that block. |
| pay_with | string | – | Optional. 'lightning' returns a BOLT11 invoice and a token instead of the x402 payment request. |
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | – |
| proof_hex | string | yes | – |
| txids | array | yes | – |
No examples provided.
watch_bitcoin_address Watch a Bitcoin address (30 days) ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Bitcoin mainnet address (bc1..., 1... or 3...) |
| feed | string | – | Optional: an existing Address Watch feed id to add to or extend |
| l402 | string | – | Optional. After paying the Lightning invoice: '<token>:<preimage>'. |
| pay_with | string | – | Optional. 'lightning' returns a BOLT11 invoice and a token instead of the x402 payment request. |
No output schema declared.
No examples provided.
whale_geopolitics_report Whale x Geopolitics daily report ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD, last 90 days. Default: latest. |
| l402 | string | – | Optional. After paying the Lightning invoice: '<token>:<preimage>'. |
| pay_with | string | – | Optional. 'lightning' returns a BOLT11 invoice and a token instead of the x402 payment request. |
No output schema declared.
No examples provided.
How do I install the Diamond Bitcoin Intelligence MCP server?
Diamond Bitcoin Intelligence is a hosted endpoint at https://diamond.tail1b5f86.ts.net/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · diamond.tail1b5f86.ts.net
claude mcp add --transport http net-ts-tail1b5f86-diamond-bitcoin-intel 'https://diamond.tail1b5f86.ts.net/api/mcp'
What is the Diamond Bitcoin Intelligence MCP server?
Diamond Bitcoin Intelligence is an MCP server listed in the public MCP registry as net.ts.tail1b5f86.diamond/bitcoin-intel. Free Bitcoin sanctions screen; paid address risk checks, market pulse, whale reports and alerts. This page covers its hosted endpoint (https://diamond.tail1b5f86.ts.net/api/mcp).
Is the Diamond Bitcoin Intelligence MCP server safe to use?
Diamond Bitcoin Intelligence scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Diamond Bitcoin Intelligence MCP server expose?
Diamond Bitcoin Intelligence exposes 14 tools: diamond_catalog, bitcoin_sanctions_screen, bitcoin_address_risk, bitcoin_market_pulse, whale_geopolitics_report, and 9 more. Their descriptions and schemas cost roughly 1,822 tokens of context every time the server is loaded.
Does the Diamond Bitcoin Intelligence MCP server require authentication?
No. We connected to Diamond Bitcoin Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Diamond Bitcoin Intelligence MCP server still maintained?
Diamond Bitcoin Intelligence is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Diamond Bitcoin Intelligence MCP server?
VerifyMCP ran 12 checks on Diamond Bitcoin Intelligence, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Diamond Bitcoin Intelligence: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.