Vizro vs VisualTorch
Vizro is an MCP server published by mckinsey. Marketplaces we read that list it: 1 (Docker MCP Catalog). VisualTorch is an MCP server published by willyfh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 |  Vizro |  VisualTorch |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ddec90039ea1 Forks (GitHub): 303 Pulls (Docker Hub): 37 329 Stars (Docker Hub): 1 Stars (GitHub): 3 806 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.4.1 Downloads/month (PyPI): 1 345 Downloads/week (PyPI): 260 Forks (GitHub): 20 Stars (GitHub): 338 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 | Vizro | VisualTorch |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 806 (better) | 338 (worse) |
| Pulls (Docker Hub) (differs) | 37 329 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 303 (better) | 20 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/vizro) | On your machine (visualtorch) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/mckinsey/vizro | github.com/willyfh/visualtorch |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
Vizro
provides tools and templates to create a functioning Vizro chart or dashboard step by step.
VisualTorch
Render PyTorch architecture diagrams and animated GIF reveals from trusted model source.
How to run each
Vizro As a local MCP server: Docker image
claude mcp add --transport stdio vizro -- docker run -i --rm mcp/vizroVisualTorch As a local MCP server: PyPI package
claude mcp add --transport stdio visualtorch -- uvx visualtorch --from "visualtorch[mcp]" visualtorch-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of VisualTorch 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: Vizro · What it can do: VisualTorch · 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.