Ext Ops Panel
Open dashboard
Comparison

AWS HealthOmics vs io.github.mims-harvard/tooluniverse

AWS HealthOmics is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.mims-harvard/tooluniverse is an MCP server published by mims-harvard. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-11-11. 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
MarketplaceAWS HealthOmicsio.github.mims-harvard/tooluniverse
Docker MCP Catalog Listed
Version: sha256:ec0cd4776cbe
Forks (GitHub): 1 868
Pulls (Docker Hub): 13 323
Stars (Docker Hub): 0
Stars (GitHub): 9 906
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.5.9
Downloads/month (PyPI): 40 535
Downloads/week (PyPI): 14 741
Forks (GitHub): 276
Stars (GitHub): 1 787
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

AWS HealthOmics vs io.github.mims-harvard/tooluniverse
FactAWS HealthOmicsio.github.mims-harvard/tooluniverse
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)9 906 (better)1 787 (worse)
Pulls (Docker Hub) (differs)13 323No figure on Docker Hub
Forks (GitHub) (differs)1 868 (better)276 (worse)
Last release (differs)Not published2026-11-05
Where it runs (differs)On your machine (mcp/aws-healthomics-mcp-server)On your machine (tooluniverse)
Transportstdiostdio
Tools it declares (differs)73Not published
Environment variables it asks for (differs)2, secrets among them: 017, secrets among them: 16
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not a bundle174
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/awslabs/mcpgithub.com/mims-harvard/tooluniverse
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

AWS HealthOmics

In its own words, on Docker MCP Catalog:

Generate, run, debug lifescience workflows.

io.github.mims-harvard/tooluniverse

In its own words, on Official MCP Registry:

2,700+ scientific tools for AI scientists: life science, research, literature, and more.

How to run each

AWS HealthOmics As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio aws-healthomics -- docker run -i --rm mcp/aws-healthomics-mcp-server

io.github.mims-harvard/tooluniverse As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "AZURE_OPENAI_API_KEY=<YOUR_AZURE_OPENAI_API_KEY>" --env "BIOGRID_API_KEY=<YOUR_BIOGRID_API_KEY>" --env "BRENDA_PASSWORD=<YOUR_BRENDA_PASSWORD>" --env "DISGENET_API_KEY=<YOUR_DISGENET_API_KEY>" --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "HF_TOKEN=<YOUR_HF_TOKEN>" --env "NCBI_API_KEY=<YOUR_NCBI_API_KEY>" --env "NVIDIA_API_KEY=<YOUR_NVIDIA_API_KEY>" --env "OMIM_API_KEY=<YOUR_OMIM_API_KEY>" --env "ONCOKB_API_TOKEN=<YOUR_ONCOKB_API_TOKEN>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --env "OPENROUTER_API_KEY=<YOUR_OPENROUTER_API_KEY>" --env "SEMANTIC_SCHOLAR_API_KEY=<YOUR_SEMANTIC_SCHOLAR_API_KEY>" --env "UMLS_API_KEY=<YOUR_UMLS_API_KEY>" --env "USPTO_API_KEY=<YOUR_USPTO_API_KEY>" --transport stdio tooluniverse -- uvx tooluniverse tooluniverse-smcp-stdio --compact-mode

Requires: ANTHROPIC_API_KEY (secret), AZURE_OPENAI_API_KEY (secret), BIOGRID_API_KEY (secret), BRENDA_PASSWORD (secret), DISGENET_API_KEY (secret), GEMINI_API_KEY (secret), HF_TOKEN (secret), NCBI_API_KEY (secret), NVIDIA_API_KEY (secret), OMIM_API_KEY (secret), ONCOKB_API_TOKEN (secret), OPENAI_API_KEY (secret), OPENROUTER_API_KEY (secret), SEMANTIC_SCHOLAR_API_KEY (secret), UMLS_API_KEY (secret), USPTO_API_KEY (secret)

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

Tools each declares

The marketplaces of io.github.mims-harvard/tooluniverse publish no list of tools, so we do not compare tools.

Settings each asks for

Only AWS HealthOmics asks for

  • AWS_PROFILE
  • AWS_REGION

Only io.github.mims-harvard/tooluniverse asks for

  • ANTHROPIC_API_KEY (secret)
  • AZURE_OPENAI_API_KEY (secret)
  • BIOGRID_API_KEY (secret)
  • BRENDA_EMAIL
  • BRENDA_PASSWORD (secret)
  • DISGENET_API_KEY (secret)
  • GEMINI_API_KEY (secret)
  • HF_TOKEN (secret)
  • NCBI_API_KEY (secret)
  • NVIDIA_API_KEY (secret)
  • OMIM_API_KEY (secret)
  • ONCOKB_API_TOKEN (secret)
Show the remaining 8
  • OPENAI_API_KEY (secret)
  • OPENROUTER_API_KEY (secret)
  • PYTHONIOENCODING
  • PYTORCH_ENABLE_MPS_FALLBACK
  • PYTORCH_MPS_HIGH_WATERMARK_RATIO
  • SEMANTIC_SCHOLAR_API_KEY (secret)
  • UMLS_API_KEY (secret)
  • USPTO_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: AWS HealthOmics · What it can do: io.github.mims-harvard/tooluniverse · 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. 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