AWS HealthOmics vs SanYu Research Engine
AWS HealthOmics is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). SanYu Research Engine is an MCP server published by kfx2026. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |  SanYu Research Engine |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ec0cd4776cbe Forks (GitHub): 1 857 Pulls (Docker Hub): 13 148 Stars (Docker Hub): 0 Stars (GitHub): 9 892 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | SanYu Research Engine |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 892 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 13 148 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 857 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-11-08 |
| Where it runs (differs) | On your machine (mcp/aws-healthomics-mcp-server) | Remote server (sanyu.wentangkeji.com/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 73 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/kfx2026/sanyu-research-mcp |
| Changes in the last 7 days (differs) | 0 | 6 |
| First seen (differs) | 2026-10-11 | 2026-11-06 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 31 h ago returned HTTP 200 |
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.
SanYu Research Engine
145 tools: 106 deterministic engines (stats, survival, bioinfo, primers) + 39 AI writers.
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-serverSanYu Research Engine As a remote MCP server
claude mcp add --transport http sanyu-research https://sanyu.wentangkeji.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only SanYu Research Engine has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of SanYu Research Engine publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of SanYu Research Engine publish no settings it asks for, so we do not compare settings.
What it can do: AWS HealthOmics · What it can do: SanYu Research Engine · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.