Opik vs Visual Memory MCP
Opik is an MCP server published by comet-ml. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, PyPI (MCP servers)). Visual Memory MCP is an MCP server published by putervision. 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 |  Opik |   Visual Memory MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 3.0.7 Downloads/month (PyPI): 3 591 Downloads/week (PyPI): 814 Forks (GitHub): 37 Stars (GitHub): 225 Not marked · First seen |
Listed Version: 1.4.2 Downloads/month (npm): 29 416 Downloads/week (npm): 4 132 Forks (GitHub): 2 Stars (GitHub): 49 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:0e0d7d33d5eb Forks (GitHub): 37 Pulls (Docker Hub): 17 157 Stars (Docker Hub): 1 Stars (GitHub): 225 Not marked · First seen |
Not listed |
| PyPI (MCP servers) | Listed Version: 3.0.7 Downloads/month (PyPI): 3 591 Downloads/week (PyPI): 814 Forks (GitHub): 37 Stars (GitHub): 225 Not marked · First seen |
Not listed |
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 | Opik | Visual Memory MCP |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 225 (better) | 49 (worse) |
| Pulls (Docker Hub) (differs) | 17 157 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 37 (better) | 2 (worse) |
| Last release (differs) | 2026-10-24 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (@putervision/vision-memory-mcp) |
| Transport (differs) | Streamable HTTP, stdio | stdio |
| Tools it declares (differs) | 13 | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/comet-ml/opik-mcp | github.com/putervision/vision-memory-mcp |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-21 | 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
Opik
Read and score Opik traces, experiments, datasets and prompts from your AI assistant.
Visual Memory MCP
Local visual UI cache for AI agents using perceptual hashing, CLIP, and 3D spatial grounding.
How to run each
Opik As a remote MCP server
claude mcp add --transport http opik-mcp https://www.comet.com/opik/api/v1/mcpRequires: OPIK_API_KEY (secret)
Visual Memory MCP As a local MCP server: npm package
claude mcp add --transport stdio vision-memory-mcp -- npx -y @putervision/vision-memory-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Opik has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Visual Memory MCP publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Visual Memory MCP publish no settings it asks for, so we do not compare settings.
What it can do: Opik · What it can do: Visual Memory MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.