Ext Ops Panel
Open dashboard
Comparison

FaceBlur Guidance vs io.github.AceDataCloud/mcp-face-transform

FaceBlur Guidance is an MCP server published by blurfaceinvideo.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.AceDataCloud/mcp-face-transform is an MCP server published by AceDataCloud. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-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
MarketplaceFaceBlur Guidanceio.github.AceDataCloud/mcp-face-transform
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 2026.11.1.0
Downloads/month (PyPI): 4 990
Downloads/week (PyPI): 198
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 2026.11.1.0
Downloads/month (PyPI): 4 990
Downloads/week (PyPI): 198
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

FaceBlur Guidance vs io.github.AceDataCloud/mcp-face-transform
FactFaceBlur Guidanceio.github.AceDataCloud/mcp-face-transform
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-11-01
Where it runs (differs)Remote server (blurfaceinvideo.com/mcp)Remote server or your machine
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/acedatacloud/facetransformmcp
Changes in the last 7 days00
First seen (differs)2026-11-022026-10-11
Endpoint at the last check (differs)Responded 4 h agoResponded 15 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

FaceBlur Guidance

In its own words, on Official MCP Registry:

Read-only guidance on blurring faces and removing metadata with FaceBlur's free browser tools.

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

FaceBlur Guidance As a remote MCP server

Claude Code
claude mcp add --transport http faceblur https://blurfaceinvideo.com/mcp

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.

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of FaceBlur Guidance publish no settings it asks for, so we do not compare settings.

What it can do: FaceBlur Guidance · What it can do: io.github.AceDataCloud/mcp-face-transform · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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