Ext Ops Panel
Open dashboard
Comparison

Gyazo vs io.github.Walmes1/ocr-images

Gyazo is an MCP server published by nota. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.Walmes1/ocr-images is an MCP server published by Walmes1. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
MarketplaceGyazoio.github.Walmes1/ocr-images
Docker MCP Catalog Listed
Version: sha256:0e12dbdc7b62
Forks (GitHub): 12
Pulls (Docker Hub): 16 641
Stars (Docker Hub): 0
Stars (GitHub): 28
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

Gyazo vs io.github.Walmes1/ocr-images
FactGyazoio.github.Walmes1/ocr-images
Marketplaces that list it11
Stars (GitHub) (differs)28 (better)0 (worse)
Pulls (Docker Hub) (differs)16 641No figure on Docker Hub
Forks (GitHub) (differs)12 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/gyazo)Not stated
Transport (differs)stdioNot stated
Tools it declares (differs)4Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/nota/gyazo-mcp-servergithub.com/walmes1/connecteurs-ia
Changes in the last 7 days00
First seen2026-10-112026-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

Gyazo

In its own words, on Docker MCP Catalog:

Official Model Context Protocol server for Gyazo.

io.github.Walmes1/ocr-images

In its own words, on Official MCP Registry:

OCR local Windows : PDF scannes, photos et captures vers texte, plus allegement d'images

How to run each

Gyazo As a local MCP server: Docker image

Claude Code
claude mcp add --env "GYAZO_ACCESS_TOKEN=<YOUR_GYAZO_ACCESS_TOKEN>" --transport stdio gyazo -- docker run -i --rm -e GYAZO_ACCESS_TOKEN mcp/gyazo

Requires: GYAZO_ACCESS_TOKEN (secret)

io.github.Walmes1/ocr-images

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

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

Tools each declares

The marketplaces of io.github.Walmes1/ocr-images publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of io.github.Walmes1/ocr-images publish no settings it asks for, so we do not compare settings.

What it can do: Gyazo · What it can do: io.github.Walmes1/ocr-images · 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.

Where the data comes from: how the catalog is built