Ext Ops Panel
Open dashboard
Comparison

AWS HealthOmics vs Agentic Target Evidence

AWS HealthOmics is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Agentic Target Evidence is an MCP server published by athril. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 HealthOmicsAgentic Target Evidence
Docker MCP Catalog Listed
Version: sha256:ec0cd4776cbe
Forks (GitHub): 1 830
Pulls (Docker Hub): 12 800
Stars (Docker Hub): 0
Stars (GitHub): 9 835
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.4
Forks (GitHub): 5
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

AWS HealthOmics vs Agentic Target Evidence
FactAWS HealthOmicsAgentic Target Evidence
Marketplaces that list it11
Stars (GitHub) (differs)9 835 (better)0 (worse)
Pulls (Docker Hub) (differs)12 800No figure on Docker Hub
Forks (GitHub) (differs)1 830 (better)5 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/aws-healthomics-mcp-server)On your machine (ghcr.io/athril/agentic-target-evidence/mcp-gateway:v0.1.4)
Transportstdiostdio
Tools it declares (differs)73Not published
Environment variables it asks for (differs)2, secrets among them: 03, secrets among them: 2
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/mcpgithub.com/athril/agentic-target-evidence
Changes in the last 7 days00
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.

Agentic Target Evidence

In its own words, on Official MCP Registry:

Read-only biomedical evidence tools for drug-target validation: DepMap, gnomAD, OpenTargets, PubMed…

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

Agentic Target Evidence As a local MCP server: Docker image

Claude Code
claude mcp add --env "NCBI_API_KEY=<YOUR_NCBI_API_KEY>" --env "USPTO_API_KEY=<YOUR_USPTO_API_KEY>" --transport stdio agentic-target-evidence -- docker run -i --rm -e NCBI_API_KEY -e USPTO_API_KEY ghcr.io/athril/agentic-target-evidence/mcp-gateway:v0.1.4

Requires: NCBI_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 Agentic Target Evidence 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 Agentic Target Evidence asks for

  • MCP_TRANSPORT
  • NCBI_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: Agentic Target Evidence · 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.

Where the data comes from: how the catalog is built