Ext Ops Panel
Open dashboard
Comparison

AWS HealthOmics vs io.github.kubeshop/testkube-mcp

AWS HealthOmics is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.kubeshop/testkube-mcp is an MCP server published by kubeshop. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-12. 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.kubeshop/testkube-mcp
Docker MCP Catalog Listed
Version: sha256:ec0cd4776cbe
Forks (GitHub): 1 805
Pulls (Docker Hub): 12 346
Stars (Docker Hub): 0
Stars (GitHub): 9 767
Not marked · First seen
Listed
Version: sha256:43aa88f2d416
Forks (GitHub): 178
Pulls (Docker Hub): 33 562
Stars (Docker Hub): 0
Stars (GitHub): 1 665
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 2.14.0
Forks (GitHub): 178
Stars (GitHub): 1 665
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.kubeshop/testkube-mcp
FactAWS HealthOmicsio.github.kubeshop/testkube-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)9 767 (better)1 665 (worse)
Pulls (Docker Hub) (differs)12 346 (worse)33 562 (better)
Forks (GitHub) (differs)1 805 (better)178 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/aws-healthomics-mcp-server)Remote server or your machine
Transport (differs)stdioStreamable HTTP, stdio
Tools it declares (differs)7328
Environment variables it asks for (differs)2, secrets among them: 09, secrets among them: 1
Licence (differs)Apache-2.0NOASSERTION
Repository (differs)github.com/awslabs/mcpgithub.com/kubeshop/testkube
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.

Tools each declares

Only AWS HealthOmics declares

  • ActivateAHOReadSets
  • AnalyzeAHORunPerformance
  • CancelAHORunBatch
  • CheckContainerAvailability
  • CloneContainerToECR
  • CreateAHOConfiguration
  • CreateAHORunCache
  • CreateAHORunGroup
  • CreateAHOSequenceStore
  • CreateAHOWorkflow
  • CreateAHOWorkflowVersion
  • CreateCodeConnection
Show the remaining 61
  • CreateContainerRegistryMap
  • CreatePullThroughCacheForHealthOmics
  • DeleteAHOBatch
  • DeleteAHOConfiguration
  • DeleteAHORunBatch
  • DiagnoseAHORunFailure
  • GenerateAHORunTimeline
  • GetAHOBatch
  • GetAHOConfiguration
  • GetAHOReadSetExportJob
  • GetAHOReadSetImportJob
  • GetAHOReadSetMetadata
  • GetAHOReferenceImportJob
  • GetAHOReferenceMetadata
  • GetAHOReferenceStore
  • GetAHORun
  • GetAHORunCache
  • GetAHORunEngineLogs
  • GetAHORunGroup
  • GetAHORunLogs
  • GetAHORunManifestLogs
  • GetAHORunTask
  • GetAHOSequenceStore
  • GetAHOSupportedRegions
  • GetAHOTaskLogs
  • GetAHOWorkflow
  • GetCodeConnection
  • GetSupportedFileTypes
  • GrantHealthOmicsRepositoryAccess
  • LintAHOWorkflowBundle
  • LintAHOWorkflowDefinition
  • ListAHOBatches
  • ListAHOConfigurations
  • ListAHOReadSetExportJobs
  • ListAHOReadSetImportJobs
  • ListAHOReadSets
  • ListAHOReferenceImportJobs
  • ListAHOReferenceStores
  • ListAHOReferences
  • ListAHORunCaches
  • ListAHORunGroups
  • ListAHORunTasks
  • ListAHORuns
  • ListAHORunsInBatch
  • ListAHOSequenceStores
  • ListAHOWorkflowVersions
  • ListAHOWorkflows
  • ListCodeConnections
  • ListECRRepositories
  • ListPullThroughCacheRules
  • PackageAHOWorkflow
  • SearchGenomicsFiles
  • StartAHOReadSetExportJob
  • StartAHOReadSetImportJob
  • StartAHOReferenceImportJob
  • StartAHORun
  • StartAHORunBatch
  • UpdateAHORunCache
  • UpdateAHORunGroup
  • UpdateAHOSequenceStore
  • ValidateHealthOmicsECRConfig

Only io.github.kubeshop/testkube-mcp declares

  • abort_workflow_execution
  • build_dashboard_url
  • create_workflow
  • create_workflowtemplate
  • fetch_execution_logs
  • get_execution_info
  • get_execution_schema
  • get_workflow
  • get_workflow_definition
  • get_workflow_execution_metrics
  • get_workflow_metrics
  • get_workflow_resource_history
Show the remaining 16
  • get_workflow_schema
  • get_workflowtemplate_definition
  • list_agents
  • list_artifacts
  • list_executions
  • list_labels
  • list_resource_groups
  • list_workflows
  • list_workflowtemplates
  • lookup_execution_id
  • read_artifact
  • run_workflow
  • update_execution_tags
  • update_workflow
  • update_workflowtemplate
  • wait_for_executions

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only AWS HealthOmics asks for

  • AWS_PROFILE
  • AWS_REGION

Only io.github.kubeshop/testkube-mcp asks for

  • TK_ACCESS_TOKEN (secret)
  • TK_CONTROL_PLANE_URL
  • TK_DASHBOARD_URL
  • TK_DEBUG
  • TK_ENV_ID (secret)
  • TK_MCP_SHTTP_HOST
  • TK_MCP_SHTTP_PORT
  • TK_MCP_TRANSPORT
  • TK_ORG_ID (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.kubeshop/testkube-mcp · 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