Liquid Compute GPU test vs io.github.fjnunezp75/gpu-bridge
Liquid Compute GPU test is an MCP server published by liquidcompute.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.fjnunezp75/gpu-bridge is an MCP server published by fjnunezp75. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 |   Liquid Compute GPU test |  io.github.fjnunezp75/gpu-bridge |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2.4.3 Downloads/month (npm): 210 Downloads/week (npm): 59 Forks (GitHub): 2 Stars (GitHub): 2 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 | Liquid Compute GPU test | io.github.fjnunezp75/gpu-bridge |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 2 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 2 (better) |
| Last release (differs) | 2026-10-16 | Not published |
| Where it runs (differs) | Remote server (api.liquidcompute.co/mcp) | On your machine (@gpu-bridge/mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/liquid-compute/gcat | github.com/gpu-bridge/mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago, requires a key | no remote endpoint we check |
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
Liquid Compute GPU test
Run GPU acceptance tests on your NVIDIA GPU nodes over SSH: DCGM, GEMM, HBM/PCIe bandwidth, NCCL.
io.github.fjnunezp75/gpu-bridge
30 GPU-powered AI services as MCP tools. LLM, image, video, audio, embeddings & more.
How to run each
Liquid Compute GPU test As a remote MCP server
claude mcp add --transport http gcat https://api.liquidcompute.co/mcpio.github.fjnunezp75/gpu-bridge As a local MCP server: npm package
claude mcp add --env "GPUBRIDGE_API_KEY=<YOUR_GPUBRIDGE_API_KEY>" --transport stdio gpu-bridge -- npx -y @gpu-bridge/mcp-serverRequires: GPUBRIDGE_API_KEY (secret)
Commands 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
The marketplaces of Liquid Compute GPU test publish no settings it asks for, so we do not compare settings.
What it can do: Liquid Compute GPU test · What it can do: io.github.fjnunezp75/gpu-bridge · Compare two other plugins
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.