Ext Ops Panel
Open dashboard
Comparison

io.github.johnisanerd/google-lens vs Visual Memory MCP

io.github.johnisanerd/google-lens is an MCP server published by johnisanerd. Marketplaces we read that list it: 1 (Official MCP Registry). Visual Memory MCP is an MCP server published by putervision. 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

Where each is published
Marketplaceio.github.johnisanerd/google-lensVisual Memory MCP
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.4.2
Downloads/month (npm): 874
Downloads/week (npm): 216
Forks (GitHub): 1
Stars (GitHub): 40
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.4.2
Downloads/month (npm): 874
Downloads/week (npm): 216
Forks (GitHub): 1
Stars (GitHub): 40
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

io.github.johnisanerd/google-lens vs Visual Memory MCP
Factio.github.johnisanerd/google-lensVisual Memory MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)40 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.apify.com)On your machine (@putervision/vision-memory-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)github.com/johnisanerd/apify-google-lens-apigithub.com/putervision/vision-memory-mcp
Changes in the last 7 days00
First seen (differs)2026-11-042026-10-11
Endpoint at the last check (differs)Responded 16 h ago, requires authenticationno 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

io.github.johnisanerd/google-lens

In its own words, on Official MCP Registry:

Google Lens reverse image and visual product search, with similar and exact matches, hosted MCP.

Visual Memory MCP

In its own words, on Official MCP Registry:

Local visual UI cache for AI agents using perceptual hashing, CLIP, and 3D spatial grounding.

How to run each

io.github.johnisanerd/google-lens

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Visual Memory MCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio vision-memory-mcp -- npx -y @putervision/vision-memory-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.github.johnisanerd/google-lens 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: io.github.johnisanerd/google-lens · What it can do: Visual Memory MCP · Compare two other plugins

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.

Where the data comes from: how the catalog is built