Ext Ops Panel
Open dashboard
Comparison

Gyazo vs Content Credentials (C2PA)

Gyazo is an MCP server published by nota. Marketplaces we read that list it: 1 (Docker MCP Catalog). Content Credentials (C2PA) is an MCP server published by contentauth. 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
MarketplaceGyazoContent Credentials (C2PA)
Docker MCP Catalog Listed
Version: sha256:0e12dbdc7b62
Forks (GitHub): 12
Pulls (Docker Hub): 16 643
Stars (Docker Hub): 0
Stars (GitHub): 28
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.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

Gyazo vs Content Credentials (C2PA)
FactGyazoContent Credentials (C2PA)
Marketplaces that list it11
Stars (GitHub) (differs)28No figure on GitHub
Pulls (Docker Hub) (differs)16 643No figure on Docker Hub
Forks (GitHub) (differs)12No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/gyazo)On your machine (https://github.com/contentauth/c2pa-mcp/releases/download/v0.2.2/c2pa-mcp-aarch64-apple-darwin.mcpb)
Transportstdiostdio
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-serverNot stated
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.

Content Credentials (C2PA)

In its own words, on Official MCP Registry:

Read and verify Content Credentials (C2PA) from images and media using the c2pa Rust SDK

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)

Content Credentials (C2PA)

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 Content Credentials (C2PA) publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Content Credentials (C2PA) publish no settings it asks for, so we do not compare settings.

What it can do: Gyazo · What it can do: Content Credentials (C2PA) · 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