Ext Ops Panel
Open dashboard
Comparison

Chroma vs AlphaFold Sovereign MCP

Chroma is an MCP server published by chroma-core. Marketplaces we read that list it: 1 (Docker MCP Catalog). AlphaFold Sovereign MCP is an MCP server published by smaniches. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-03. 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
MarketplaceChromaAlphaFold Sovereign MCP
Docker MCP Catalog Listed
Version: sha256:c050ca8e1d4e
Forks (GitHub): 120
Pulls (Docker Hub): 61 822
Stars (Docker Hub): 5
Stars (GitHub): 601
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.5.9
Downloads/month (PyPI): 745
Downloads/week (PyPI): 534
Forks (GitHub): 2
Stars (GitHub): 4
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.5.9
Downloads/month (PyPI): 745
Downloads/week (PyPI): 534
Forks (GitHub): 2
Stars (GitHub): 4
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

Chroma vs AlphaFold Sovereign MCP
FactChromaAlphaFold Sovereign MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)601 (better)4 (worse)
Pulls (Docker Hub) (differs)61 822No figure on Docker Hub
Forks (GitHub) (differs)120 (better)2 (worse)
Last release (differs)Not published2026-10-30
Where it runs (differs)On your machine (mcp/chroma)On your machine (alphafold-sovereign-mcp)
Transportstdiostdio
Tools it declares (differs)13Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/chroma-core/chroma-mcpgithub.com/smaniches/alphafold-sovereign-mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11

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

Chroma

In its own words, on Docker MCP Catalog:

A Model Context Protocol (MCP) server implementation that provides database capabilities for Chroma.

AlphaFold Sovereign MCP

In its own words, on Official MCP Registry:

MCP server for AlphaFold and 8 other biomedical data sources with a local SQLite knowledge graph

How to run each

Chroma As a local MCP server: Docker image

Claude Code
claude mcp add --env "CHROMA_API_KEY=<YOUR_CHROMA_API_KEY>" --transport stdio chroma -- docker run -i --rm -e CHROMA_API_KEY mcp/chroma

Requires: CHROMA_API_KEY (secret)

AlphaFold Sovereign MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio alphafold-sovereign-mcp -- uvx alphafold-sovereign-mcp

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

Tools each declares

The marketplaces of AlphaFold Sovereign MCP publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of AlphaFold Sovereign MCP publish no settings it asks for, so we do not compare settings.

What it can do: Chroma · What it can do: AlphaFold Sovereign MCP · 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. Package data comes from the Python Package Index (pypi.org). 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