Ext Ops Panel
Open dashboard
Comparison

EverArt (Archived) vs io.github.AceDataCloud/mcp-face-transform

EverArt (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.AceDataCloud/mcp-face-transform is an MCP server published by AceDataCloud. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
MarketplaceEverArt (Archived)io.github.AceDataCloud/mcp-face-transform
Docker MCP Catalog Listed
Version: sha256:98c2aa1b6231
Forks (GitHub): 11 787
Pulls (Docker Hub): 18 789
Stars (Docker Hub): 3
Stars (GitHub): 91 222
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2026.10.12.1
Downloads/month (PyPI): 4 990
Downloads/week (PyPI): 765
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

EverArt (Archived) vs io.github.AceDataCloud/mcp-face-transform
FactEverArt (Archived)io.github.AceDataCloud/mcp-face-transform
Marketplaces that list it11
Stars (GitHub) (differs)91 222 (better)1 (worse)
Pulls (Docker Hub) (differs)18 789No figure on Docker Hub
Forks (GitHub) (differs)11 787 (better)0 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)On your machine (mcp/everart)Remote server (face.mcp.acedata.cloud/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/acedatacloud/facetransformmcp
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

EverArt (Archived)

In its own words, on Docker MCP Catalog:

Image generation server using EverArt's API.

io.github.AceDataCloud/mcp-face-transform

In its own words, on Official MCP Registry:

AceDataCloud Face Transform MCP: keypoints, beautify, age/gender, swap, cartoon, liveness

How to run each

EverArt (Archived) As a local MCP server: Docker image

Claude Code
claude mcp add --env "EVERART_API_KEY=<YOUR_EVERART_API_KEY>" --transport stdio everart -- docker run -i --rm -e EVERART_API_KEY mcp/everart

Requires: EVERART_API_KEY (secret)

io.github.AceDataCloud/mcp-face-transform As a remote MCP server

Claude Code
claude mcp add --transport http mcp-face-transform https://face.mcp.acedata.cloud/mcp

Requires: ACEDATACLOUD_API_TOKEN (secret)

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.AceDataCloud/mcp-face-transform publish no list of tools, so we do not compare tools.

Settings each asks for

Only EverArt (Archived) asks for

  • EVERART_API_KEY (secret)

Only io.github.AceDataCloud/mcp-face-transform asks for

  • ACEDATACLOUD_API_TOKEN (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: EverArt (Archived) · What it can do: io.github.AceDataCloud/mcp-face-transform · 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