AWS HealthOmics vs BioSymphony BioProspector
BioSymphony BioProspector is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
AWS HealthOmics is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). BioSymphony BioProspector is a plugin bundle for AI coding tools published by BioSymphony. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-26. 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
| Marketplace |  AWS HealthOmics | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ec0cd4776cbe Forks (GitHub): 1 827 Pulls (Docker Hub): 12 796 Stars (Docker Hub): 0 Stars (GitHub): 9 830 Not marked · First seen |
Not listed |
| Community marketplace biosymphony/bioprospector | Not listed | Removed on 2026-10-17 Version: 0.1.0 Forks (GitHub): 1 Stars (GitHub): 2 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
| Fact | AWS HealthOmics | BioSymphony BioProspectorno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 9 830 | 2 |
| Pulls (Docker Hub) (differs) | 12 796 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 827 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-healthomics-mcp-server) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 73 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | Not published |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/biosymphony/bioprospector |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
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 BioSymphony BioProspector
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Plan public-safe structural biology campaigns.
-
Thinking tools for AI agents making discoveries in the life sciences
-
197 ready-to-use life sciences skills that turn Claude into a domain expert for genomics, proteomics, drug discovery, biostatistics, scientific computing, and scientific writing…
-
Predict structures, screen molecules and proteins, and design binders.
-
Corollary — scientific AI models, tools and databases
Find open biology and chemistry AI models, bioinformatics tools and databases, and run them online.
-
Connect to preclinical research tools and databases (literature search, genomics analysis, target prioritization) to accelerate early-stage life sciences R&D
What each says it does
AWS HealthOmics
Generate, run, debug lifescience workflows.
BioSymphony BioProspector
Plan public-safe biosynthetic pathway discovery campaigns.
How to run each
AWS HealthOmics As a local MCP server: Docker image
claude mcp add --transport stdio aws-healthomics -- docker run -i --rm mcp/aws-healthomics-mcp-serverBioSymphony BioProspector
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 BioSymphony BioProspector publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of BioSymphony BioProspector publish no settings it asks for, so we do not compare settings.
What it can do: AWS HealthOmics · What it can do: BioSymphony BioProspector · 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.