io.github.kubeshop/testkube-mcp vs Python Package Runtime Test
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). Python Package Runtime Test is an MCP server published by ligafew. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 |  io.github.kubeshop/testkube-mcp | |
|---|---|---|
| Official MCP Registry | Listed Version: 2.14.0 Forks (GitHub): 178 Stars (GitHub): 1 669 Not marked · First seen |
Listed Version: 1.0.2 No figure published Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:43aa88f2d416 Forks (GitHub): 178 Pulls (Docker Hub): 33 592 Stars (Docker Hub): 0 Stars (GitHub): 1 669 Not marked · First seen |
Not listed |
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 | io.github.kubeshop/testkube-mcp | Python Package Runtime Test |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 669 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 33 592 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 178 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (apcs-public-mcp-gateway.apcs-mcp.workers.dev/mcp/python-package-runtime-test) |
| Transport (differs) | Streamable HTTP, stdio | Streamable HTTP |
| Tools it declares (differs) | 28 | Not published |
| Environment variables it asks for (differs) | 9, secrets among them: 1 | Not published |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/kubeshop/testkube | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check | not checked yet | not checked yet |
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
io.github.kubeshop/testkube-mcp
MCP server for Testkube - Manage test workflows, executions, and artifacts via AI assistants
Python Package Runtime Test
Hosted Python sandbox for package runtime verification: pip install and usable-import evidence.
How to run each
io.github.kubeshop/testkube-mcp As a local MCP server: Docker image
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/testkubeRequires: TK_ACCESS_TOKEN (secret), TK_ENV_ID (secret), TK_ORG_ID (secret)
Python Package Runtime Test As a remote MCP server
claude mcp add --transport http python-package-runtime-test https://apcs-public-mcp-gateway.apcs-mcp.workers.dev/mcp/python-package-runtime-testCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Python Package Runtime Test publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Python Package Runtime Test publish no settings it asks for, so we do not compare settings.
What it can do: io.github.kubeshop/testkube-mcp · What it can do: Python Package Runtime Test · Compare two other plugins
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.