Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks vs Transloadit Media Processing
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). Transloadit Media Processing is an MCP server published by transloadit. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (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
| Marketplace |  Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks |   Transloadit Media Processing |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.7 No figure published Not marked · First seen |
Listed Version: 0.8.8 Downloads/month (npm): 12 074 Downloads/week (npm): 2 373 Forks (GitHub): 25 Stars (GitHub): 73 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.8.8 Downloads/month (npm): 12 074 Downloads/week (npm): 2 373 Forks (GitHub): 25 Stars (GitHub): 73 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 | Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks | Transloadit Media Processing |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 73 |
| Forks (GitHub) (differs) | No figure on GitHub | 25 |
| Last release (differs) | 2026-11-02 (worse) | 2026-11-14 (better) |
| Where it runs (differs) | Remote server (mcp.apify.com) | Remote server or your machine |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/transloadit/node-sdk |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-31 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 16 h ago, requires authentication | Responded 22 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
Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks
Remove EXIF, GPS location and camera serials from images without re-encoding the pixels
Transloadit Media Processing
Process video, audio, images and documents with Transloadit Robots. Connect by URL with OAuth.
How to run each
Image 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
Transloadit Media Processing As a remote MCP server
claude mcp add --transport http transloadit-media-processing https://api2.transloadit.com/mcpRequires: TRANSLOADIT_KEY, TRANSLOADIT_SECRET (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 Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks publish no settings it asks for, so we do not compare settings.
What it can do: Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks · What it can do: Transloadit Media Processing · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.