gpu-cli vs Liquid Compute GPU test
gpu-cli is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
gpu-cli is a plugin bundle for AI coding tools published by GPU CLI. No marketplace we read lists it any more. 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. 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
| Marketplace |   Liquid Compute GPU test | |
|---|---|---|
| Community marketplace gpu-cli/gpu | Removed on 2026-10-23 Version: 2.0.0 Forks (GitHub): 0 Stars (GitHub): 8 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 | gpu-clino longer listed · | Liquid Compute GPU test |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 8 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.liquidcompute.co/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/gpu-cli/gpu | github.com/liquid-compute/gcat |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-20 | 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. 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 gpu-cli
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Find the right NVIDIA skill for GPU acceleration, CUDA, AI agents, data loading, training, inference, robotics, Physical AI, Omniverse, simulation, and other NVIDIA-powered…
-
Skills for NVIDIAs ecosystem spans GPU acceleration, CUDA, AI agents, inference, robotics, Physical AI, Omniverse, and simulation. This plugin helps you understand the pieces…
-
gpu-bridge io.github.fjnunezp75/gpu-bridge
30 GPU-powered AI services as MCP tools. LLM, image, video, audio, embeddings & more.
-
AMD's verified Agent Skills in one plugin: route image/audio through local AI on Ryzen AI, serve LLMs on AMD Instinct GPUs with vLLM, optimize inference throughput with Hyperloom…
-
Provision private AI model endpoints on dedicated GPUs (Llama, Qwen, Mistral). Pay per minute.
-
MCP-first control plane for ComfyUI workflows with explicit approvals and no silent downloads.
What each says it does
gpu-cli
Transform natural language into complete ML workflows - training, inference, media processing, and more.
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
gpu-cli
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Liquid 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
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: gpu-cli · What it can do: Liquid Compute GPU test · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.