Ext Ops Panel
Open dashboard
Comparison

OpenZeppelin Stellar Contracts vs bd-skills

OpenZeppelin Stellar Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). bd-skills is a plugin bundle for AI coding tools published by bitdriftlabs. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). As of our marketplace pass on 2026-10-14. 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 Contractsbd-skills
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Copilot CLI: github/awesome-copilot Not listed Listed
Version: 0.1.26
Forks (GitHub): 0
Stars (GitHub): 13
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 bd-skills
FactOpenZeppelin Stellar Contractsbd-skills
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub13
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.openzeppelin.com/contracts/stellar/mcp)Installs as a plugin bundle
Transport (differs)Streamable HTTPNot stated
Tools it declares (differs)6Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle4
Licence (differs)Apache-2.0PolyForm Shield License 1.0.0
Repository (differs)Not statedgithub.com/bitdriftlabs/bd-skills
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno remote endpoint we check

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.

bd-skills

In its own words, on Copilot CLI: github/awesome-copilot:

Helps GitHub Copilot investigate mobile app telemetry, diagnose crashes, manage [bitdrift](bitdrift.ai) workflows and dashboards, integrate the Capture SDK into iOS, Android, and React Native apps, and configure User Journey monitoring. Includes four skills covering CLI operations, SDK instrumentation, documentation lookup, and user journey monitoring; live account operations require the bd CLI and [bitdrift](bitdrift.ai) account and authentication.

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

bd-skills

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Tools each declares

The marketplaces of bd-skills publish no list of tools, so we do not compare tools.

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: bd-skills · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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