Ext Ops Panel
Open dashboard
Comparison

Zen vs model-registry

model-registry is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.

Zen is an MCP server published by BeehiveInnovations. Marketplaces we read that list it: 1 (Docker MCP Catalog). model-registry is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-20. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceZenmodel-registry
Docker MCP Catalog Listed
Version: sha256:02cbe1d325db
Forks (GitHub): 1 036
Pulls (Docker Hub): 34 962
Stars (Docker Hub): 0
Stars (GitHub): 11 792
Not marked · First seen
Not listed
Community marketplace barnburner121/claude-plugin-marketplace Not listed Removed on 2026-10-18
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
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

Zen vs model-registry
FactZenmodel-registryno longer listed ·
Marketplaces that list it (differs)10
Stars (GitHub) (differs)11 7923
Pulls (Docker Hub) (differs)34 962No figure on Docker Hub
Forks (GitHub) (differs)1 0360
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/zen)On your machine (@barnburner121/plugin-hub-mcp)
Transport (differs)stdioNot stated
Tools it declares (differs)18Not published
Environment variables it asks for (differs)4, secrets among them: 4Not published
Parts of the bundle (differs)Not a bundle2
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/beehiveinnovations/zen-mcp-servergithub.com/barnburner121/claude-plugin-marketplace
Changes in the last 7 days (differs)04
First seen (differs)2026-10-112026-10-14

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of model-registry

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • dominodatalab

    Full Domino Data Lab platform support — workspaces, jobs, model deployment, experiment tracking, GenAI tracing, Spark/Ray/Dask, and app deployment for data science teams

    by dominodatalab · Plugin bundle

    Listed on: Claude Code: claude-plugins-official, Claude Code: claude-plugins-community · Describes nearly the same job

  • mlflow io.github.us-all/mlflow

    MLflow MCP — experiments, runs, registered models, versions, traces, assessments (MLflow 3)

    by us-all · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • datarobot-agent-skills

    DataRobot skills for AI/ML workflows — model training, deployment, predictions, feature engineering, monitoring, explainability, data preparation, App Framework CI/CD, and…

    by datarobot-oss · Plugin bundle

    Listed on: Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Community GitHub marketplaces · Describes nearly the same job

  • MLflow Skills

    Skills for tracing, evaluating, and improving AI agents with MLflow. Supports the full agent improvement loop: instrument → trace → evaluate → iterate → validate.

    by mlflow · Plugin bundle

    Listed on: Claude Code: claude-plugins-official · Describes nearly the same job

  • AIRAS

    Automated AI research toolkit: hypothesis generation, experiments, and paper writing

    by airas-org · MCP server

    Listed on: Official MCP Registry, Community GitHub marketplaces · Describes nearly the same job

  • probabl-skills

    Skills to support Machine Learning experimentation using the Python ecosystem.

    by probabl-ai · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

Zen

In its own words, on Docker MCP Catalog:

Bridges multiple AI models and CLIs, enabling orchestrated workflows across Claude Code, Gemini CLI, Codex CLI, and other AI development tools.

model-registry

In its own words, on Community GitHub marketplaces:

Generate ML model registry and versioning

How to run each

Zen As a local MCP server: Docker image

Claude Code
claude mcp add --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --env "OPENROUTER_API_KEY=<YOUR_OPENROUTER_API_KEY>" --env "XAI_API_KEY=<YOUR_XAI_API_KEY>" --transport stdio zen -- docker run -i --rm -e GEMINI_API_KEY -e OPENAI_API_KEY -e OPENROUTER_API_KEY -e XAI_API_KEY mcp/zen

Requires: GEMINI_API_KEY (secret), OPENAI_API_KEY (secret), OPENROUTER_API_KEY (secret), XAI_API_KEY (secret)

model-registry

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 model-registry publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of model-registry publish no settings it asks for, so we do not compare settings.

What it can do: Zen · What it can do: model-registry · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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