Home / MCP registry index / net.ts.tail1b5f86.diamond/bitcoin-intel
Diamond Bitcoin Intelligence
net.ts.tail1b5f86.diamond/bitcoin-intel in the official MCP registry.
Endpoint https://diamond.tail1b5f86.ts.net/api/mcp.
The registry describes it as: Free Bitcoin sanctions screen; paid address risk checks, market pulse, whale reports and alerts.
We read its 7 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
diamond_catalog bitcoin_sanctions_screen bitcoin_address_risk bitcoin_market_pulse whale_geopolitics_report watch_bitcoin_address bitcoin_batch_risk
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/net-ts-tail1b5f86-diamond-bitcoin-intel)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.