Vizro vs com.slickfast/mcp
Vizro is an MCP server published by mckinsey. Marketplaces we read that list it: 1 (Docker MCP Catalog). com.slickfast/mcp is an MCP server published by slickfast.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-12. 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 |  com.slickfast/mcp |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ddec90039ea1 Forks (GitHub): 308 Pulls (Docker Hub): 38 117 Stars (Docker Hub): 1 Stars (GitHub): 3 821 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.7.39 Downloads/month (npm): 1 217 Downloads/week (npm): 527 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.7.39 Downloads/month (npm): 1 217 Downloads/week (npm): 527 Forks (GitHub): 1 Stars (GitHub): 1 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 | com.slickfast/mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 3 821 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 38 117 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 308 (better) | 1 (worse) |
| Last release (differs) | Not published | 2026-11-10 |
| Where it runs (differs) | On your machine (mcp/vizro) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | AGPL-3.0-only |
| Repository (differs) | github.com/mckinsey/vizro | github.com/slickfast/slickfast |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 15 h ago, requires authentication |
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.
com.slickfast/mcp
Charts and dashboards as images for AI agents. No browser, same data same bytes. Local and free.
How to run each
Vizro As a local MCP server: Docker image
claude mcp add --transport stdio vizro -- docker run -i --rm mcp/vizrocom.slickfast/mcp As a remote MCP server
claude mcp add --transport http com-slickfast-mcp https://mcp.slickfast.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.slickfast/mcp has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of com.slickfast/mcp 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: com.slickfast/mcp · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.