Ext Ops Panel
Open dashboard
Comparison

Handwriting OCR vs Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks

Handwriting OCR is an MCP server published by Handwriting-OCR. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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

Where each is published
MarketplaceHandwriting OCRImage Metadata Remover — EXIF/GPS Scrub with Pixel Checks
Docker MCP Catalog Listed
Version: sha256:141e2e00e706
Forks (GitHub): 7
Pulls (Docker Hub): 19 512
Stars (Docker Hub): 2
Stars (GitHub): 18
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

Handwriting OCR vs Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks
FactHandwriting OCRImage Metadata Remover — EXIF/GPS Scrub with Pixel Checks
Marketplaces that list it11
Stars (GitHub) (differs)18No figure on GitHub
Pulls (Docker Hub) (differs)19 512No figure on Docker Hub
Forks (GitHub) (differs)7No figure on GitHub
Last release (differs)Not published2026-11-02
Where it runs (differs)On your machine (mcp/handwriting-ocr)Remote server (mcp.apify.com)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)3Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/handwriting-ocr/handwriting-ocr-mcp-serverNot stated
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-31
Endpoint at the last check (differs)no remote endpoint we checkResponded 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

Handwriting OCR

In its own words, on Docker MCP Catalog:

Model Context Protocol (MCP) Server for Handwriting OCR.

Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks

In its own words, on Official MCP Registry:

Remove EXIF, GPS location and camera serials from images without re-encoding the pixels

How to run each

Handwriting OCR As a local MCP server: Docker image

Claude Code
claude mcp add --env "API_TOKEN=<YOUR_API_TOKEN>" --transport stdio handwriting-ocr -- docker run -i --rm -e API_TOKEN mcp/handwriting-ocr

Requires: API_TOKEN (secret)

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

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

The marketplaces of Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks publish no list of tools, so we do not compare tools.

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: Handwriting OCR · What it can do: Image Metadata Remover — EXIF/GPS Scrub with Pixel Checks · 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