AWS HealthOmics vs Infrawise
AWS HealthOmics is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Infrawise is an MCP server published by Sidd27. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. 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
| Marketplace |  AWS HealthOmics |  Infrawise |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ec0cd4776cbe Forks (GitHub): 1 820 Pulls (Docker Hub): 12 526 Stars (Docker Hub): 0 Stars (GitHub): 9 803 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Downloads/month (npm): 1 026 Downloads/week (npm): 100 Forks (GitHub): 5 Stars (GitHub): 22 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.0.0 Downloads/month (npm): 1 026 Downloads/week (npm): 100 Forks (GitHub): 5 Stars (GitHub): 22 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 | Infrawise |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 9 803 (better) | 22 (worse) |
| Pulls (Docker Hub) (differs) | 12 526 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 820 (better) | 5 (worse) |
| Last release (differs) | Not published | 2026-10-21 |
| Where it runs (differs) | On your machine (mcp/aws-healthomics-mcp-server) | On your machine (infrawise) |
| Transport | stdio | stdio |
| 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 | MIT |
| Repository (differs) | github.com/awslabs/mcp | github.com/sidd27/infrawise |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-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
Generate, run, debug lifescience workflows.
Infrawise
Live AWS, database & Kafka infrastructure context for AI coding assistants via MCP.
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-serverInfrawise As a local MCP server: npm package
claude mcp add --transport stdio infrawise -- npx -y infrawiseCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Infrawise publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Infrawise publish no settings it asks for, so we do not compare settings.
What it can do: AWS HealthOmics · What it can do: Infrawise · 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 public npm registry (registry.npmjs.org). 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.