Gyazo vs Supericons
Gyazo is an MCP server published by nota. Marketplaces we read that list it: 1 (Docker MCP Catalog). Supericons is an MCP server published by curlymolelabs. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-20. 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 |  Gyazo |  Supericons |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:0e12dbdc7b62 Forks (GitHub): 12 Pulls (Docker Hub): 16 699 Stars (Docker Hub): 0 Stars (GitHub): 28 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.22 Downloads/month (npm): 2 620 Downloads/week (npm): 702 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 2.0.0 Forks (GitHub): 0 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 | Gyazo | Supericons |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 28 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 16 699 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 12 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/gyazo) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 4 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/nota/gyazo-mcp-server | github.com/curlymolelabs/supericons |
| 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 3 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
Official Model Context Protocol server for Gyazo.
Supericons
Multilingual semantic SVG icon search with previews for AI coding agents. 20,000+ icons.
How to run each
Gyazo As a local MCP server: Docker image
claude mcp add --env "GYAZO_ACCESS_TOKEN=<YOUR_GYAZO_ACCESS_TOKEN>" --transport stdio gyazo -- docker run -i --rm -e GYAZO_ACCESS_TOKEN mcp/gyazoRequires: GYAZO_ACCESS_TOKEN (secret)
Supericons As a remote MCP server
claude mcp add --transport http supericons https://mcp.supericons.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Supericons has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Supericons publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Supericons publish no settings it asks for, so we do not compare settings.
What it can do: Gyazo · What it can do: Supericons · 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. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.