Ext Ops Panel
Open dashboard
Comparison

TestAtlas vs io.github.kubeshop/testkube-mcp

TestAtlas is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.

TestAtlas is a plugin bundle for AI coding tools published by Karzone. No marketplace we read lists it any more. 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-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceTestAtlasio.github.kubeshop/testkube-mcp
Community marketplace karzone/testatlas Removed on 2026-10-17
Version: 0.1.3
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.14.2
Forks (GitHub): 180
Stars (GitHub): 1 673
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:43aa88f2d416
Forks (GitHub): 180
Pulls (Docker Hub): 33 936
Stars (Docker Hub): 0
Stars (GitHub): 1 673
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

TestAtlas vs io.github.kubeshop/testkube-mcp
FactTestAtlasno longer listed · io.github.kubeshop/testkube-mcp
Marketplaces that list it (differs)02
Stars (GitHub) (differs)31 673
Pulls (Docker Hub) (differs)No figure on Docker Hub33 936
Forks (GitHub) (differs)0180
Last release (differs)Not published2026-10-19
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP, stdio
Tools it declares (differs)Not published28
Environment variables it asks for (differs)Not published9, secrets among them: 1
Hooks it runs (differs)1Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)MITNOASSERTION
Repository (differs)github.com/karzone/testatlasgithub.com/kubeshop/testkube
Changes in the last 7 days (differs)02
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago, requires a key

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of TestAtlas

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • OrangePro

    Find test gaps, generate grounded tests, and dynamically prove behavior with mutation testing.

    by orangepro.ai · MCP server

    Listed on: Official MCP Registry, Community GitHub marketplaces · Describes nearly the same job

  • Meticulous

    Agent skills for Meticulous visual regression testing — review test runs, investigate replays, debug diffs. Also connects the hosted Meticulous MCP server.

    by alwaysmeticulous · Plugin bundle

    Listed on: Claude Code: claude-plugins-community, Community GitHub marketplaces · Describes nearly the same job

  • testing-toolkit

    Comprehensive testing toolkit for test strategy, coverage analysis, and test data generation. Includes test strategist agent for planning optimal testing approaches.

    by Arman Nourifar · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • QA Radar

    Tells AI agents which files to test first — churn, coverage, and test mapping as risk scores.

    by MuratKus · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • qa-expert

    QA process setup with AAA test cases, P0-P4 bug tracking, metrics reports, OWASP security testing and third-party handoffs. Use for test planning, approved-batch execution and…

    by daymade · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • test-results-analyzer

    Use this agent for analyzing test results, synthesizing test data, identifying trends, and genera...

    by DevsForge Community · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

TestAtlas

In its own words, on Community GitHub marketplaces:

Find existing steps before writing new ones, trace the blast radius of a change, and keep the map fresh

io.github.kubeshop/testkube-mcp

In its own words, on Official MCP Registry:

MCP server for Testkube - Manage test workflows, executions, and artifacts via AI assistants

How to run each

TestAtlas

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.kubeshop/testkube-mcp As a local MCP server: Docker image

Claude Code
claude mcp add --env "TK_ACCESS_TOKEN=<YOUR_TK_ACCESS_TOKEN>" --env "TK_ENV_ID=<YOUR_TK_ENV_ID>" --env "TK_ORG_ID=<YOUR_TK_ORG_ID>" --transport stdio testkube -- docker run -i --rm -e TK_ACCESS_TOKEN -e TK_ENV_ID -e TK_ORG_ID mcp/testkube

Requires: TK_ACCESS_TOKEN (secret), TK_ENV_ID (secret), TK_ORG_ID (secret)

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

Only io.github.kubeshop/testkube-mcp has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of TestAtlas publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of TestAtlas publish no settings it asks for, so we do not compare settings.

What it can do: TestAtlas · What it can do: io.github.kubeshop/testkube-mcp · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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