Watermarks Remover vs Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks
Watermarks Remover is a plugin bundle for AI coding tools published by watermarks-remover contributors. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks is an MCP server published by kriton-dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks | |
|---|---|---|
| Community marketplace guillaumemeyer/watermarks-remover | Listed Version: 0.7.0 Forks (GitHub): 3 107 Stars (GitHub): 27 413 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.7 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 | Watermarks Remover | Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 27 413 | No figure on GitHub |
| Forks (GitHub) (differs) | 3 107 | No figure on GitHub |
| Last release (differs) | Not published | 2026-11-02 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.apify.com) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/guillaumemeyer/watermarks-remover | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-20 | 2026-10-31 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 16 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
Watermarks Remover
Remove multi-vendor AI provenance marks from text, images, documents, and media. Bundles the remove-ai-marks and clean-user-facing-text skills.
Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks
Remove EXIF, GPS location and camera serials from images without re-encoding the pixels
How to run each
Watermarks Remover As a Claude Code plugin
/plugin marketplace add guillaumemeyer/watermarks-remover
/plugin install watermarks-remover@watermarks-removerImage Metadata Remover — EXIF/GPS Scrub with Pixel Checks
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 Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks has a remote endpoint we 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Watermarks Remover · What it can do: Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.