Gyazo vs Logo & Favicon Extractor
Gyazo is an MCP server published by nota. Marketplaces we read that list it: 1 (Docker MCP Catalog). Logo & Favicon Extractor is an MCP server published by Nero-Engine. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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 |  Logo & Favicon Extractor |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:0e12dbdc7b62 Forks (GitHub): 12 Pulls (Docker Hub): 17 192 Stars (Docker Hub): 0 Stars (GitHub): 28 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 No figure published 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 | Logo & Favicon Extractor |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 28 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 17 192 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 12 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/gyazo) | Remote server (mcp.apify.com) |
| 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 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/nota/gyazo-mcp-server | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-28 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 23 h ago, requires authentication |
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.
Logo & Favicon Extractor
Company logo, best icon and favicon for a list of websites, with measured image size and format.
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)
Logo & Favicon Extractor
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Logo & Favicon Extractor has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Logo & Favicon Extractor publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Logo & Favicon Extractor publish no settings it asks for, so we do not compare settings.
What it can do: Gyazo · What it can do: Logo & Favicon Extractor · 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.