Ext Ops Panel
Open dashboard
Comparison

Gyazo vs io.github.onepunchtechnology/glassypic

Gyazo is an MCP server published by nota. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.onepunchtechnology/glassypic is an MCP server published by onepunchtechnology. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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.onepunchtechnology/glassypic
Docker MCP Catalog Listed
Version: sha256:0e12dbdc7b62
Forks (GitHub): 12
Pulls (Docker Hub): 16 650
Stars (Docker Hub): 0
Stars (GitHub): 28
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.1.3
Downloads/month (npm): 408
Downloads/week (npm): 48
Forks (GitHub): 1
Stars (GitHub): 2
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.onepunchtechnology/glassypic
FactGyazoio.github.onepunchtechnology/glassypic
Marketplaces that list it11
Stars (GitHub) (differs)28 (better)2 (worse)
Pulls (Docker Hub) (differs)16 650No figure on Docker Hub
Forks (GitHub) (differs)12 (better)1 (worse)
Last release (differs)Not published2026-10-16
Where it runs (differs)On your machine (mcp/gyazo)Remote server (app.glassypic.com/mcp)
Transport (differs)stdioStreamable HTTP
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/onepunchtechnology/glassypic-mcp-server
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago

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.onepunchtechnology/glassypic

In its own words, on Official MCP Registry:

Production-ready images in one pass: resize, crop, compress, convert format, upscale, tag for SEO

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.onepunchtechnology/glassypic As a remote MCP server

Claude Code
claude mcp add --transport http glassypic https://app.glassypic.com/mcp

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

Only io.github.onepunchtechnology/glassypic has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of io.github.onepunchtechnology/glassypic publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of io.github.onepunchtechnology/glassypic publish no settings it asks for, so we do not compare settings.

What it can do: Gyazo · What it can do: io.github.onepunchtechnology/glassypic · 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