Ext Ops Panel
Open dashboard
Comparison

OpenZeppelin Stellar Contracts vs Diamond Bitcoin Intelligence

OpenZeppelin Stellar Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Diamond Bitcoin Intelligence is an MCP server published by diamond.tail1b5f86.ts.net. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceOpenZeppelin Stellar ContractsDiamond Bitcoin Intelligence
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 13.0.0
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

OpenZeppelin Stellar Contracts vs Diamond Bitcoin Intelligence
FactOpenZeppelin Stellar ContractsDiamond Bitcoin Intelligence
Marketplaces that list it11
Last release (differs)Not published2026-10-18
Where it runs (differs)Remote server (mcp.openzeppelin.com/contracts/stellar/mcp)Remote server (diamond.tail1b5f86.ts.net/api/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declares (differs)6Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
RepositoryNot statedNot stated
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-17
Endpoint at the last check (differs)Responded 6 days agoResponded 5 days ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

OpenZeppelin Stellar Contracts

In its own words, on Docker MCP Catalog:

Access to OpenZeppelin Stellar Contracts.

Diamond Bitcoin Intelligence

In its own words, on Official MCP Registry:

Free Bitcoin sanctions screen; paid address risk checks, market pulse, whale reports and alerts.

How to run each

OpenZeppelin Stellar Contracts As a remote MCP server

Claude Code
claude mcp add --transport http openzeppelin-stellar https://mcp.openzeppelin.com/contracts/stellar/mcp

Diamond Bitcoin Intelligence As a remote MCP server

Claude Code
claude mcp add --transport http bitcoin-intel https://diamond.tail1b5f86.ts.net/api/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Only OpenZeppelin Stellar Contracts has

  • stellar-account
  • stellar-fungible
  • stellar-governor
  • stellar-non-fungible
  • stellar-stablecoin
  • stellar-vault

Only Diamond Bitcoin Intelligence has

  • bitcoin_address_risk
  • bitcoin_market_pulse
  • bitcoin_sanctions_screen
  • diamond_catalog
  • watch_bitcoin_address
  • whale_geopolitics_report

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Diamond Bitcoin Intelligence as of 2026-10-22). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: OpenZeppelin Stellar Contracts · What it can do: Diamond Bitcoin Intelligence · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built