Inspektor Gadget vs Liquid Compute GPU test
Inspektor Gadget is an MCP server published by inspektor-gadget. Marketplaces we read that list it: 1 (Docker MCP Catalog). Liquid Compute GPU test is an MCP server published by liquidcompute.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  Inspektor Gadget |   Liquid Compute GPU test |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:a54c99a50a81 Forks (GitHub): 6 Pulls (Docker Hub): 13 430 Stars (Docker Hub): 2 Stars (GitHub): 28 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 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 | Inspektor Gadget | Liquid Compute GPU test |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 28 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 13 430 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 6 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | On your machine (mcp/inspektor-gadget) | Remote server (api.liquidcompute.co/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 37 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/inspektor-gadget/ig-mcp-server | github.com/liquid-compute/gcat |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago, requires a key |
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
Inspektor Gadget
AI interface to troubleshoot and observe Kubernetes/Container workloads.
Liquid Compute GPU test
Run GPU acceptance tests on your NVIDIA GPU nodes over SSH: DCGM, GEMM, HBM/PCIe bandwidth, NCCL.
How to run each
Inspektor Gadget As a local MCP server: Docker image
claude mcp add --transport stdio inspektor-gadget -- docker run -i --rm mcp/inspektor-gadgetLiquid Compute GPU test As a remote MCP server
claude mcp add --transport http gcat https://api.liquidcompute.co/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Liquid Compute GPU test has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Liquid Compute GPU test publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Inspektor Gadget · What it can do: Liquid Compute GPU test · 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.