0 Fork 0

mirror of https://github.com/wiltodelta/remove-ai-watermarks.git synced 2026-10-20 07:57:21 +02:00

Files

T

Victor KuznetsovandClaude Opus 5.5 7e167c3c76 Fail closed on unreadable inputs, empty batches and failed strips

The metadata scanners read raw bytes, so random bytes, an empty file or a
truncated PNG or MP4 printed the same "No AI metadata found" or "AI metadata
stripped" a real file gets, with exit 0. `metadata.unreadable_reason` is now
the one readability probe: `identify`, `metadata` and every `video` command
exit 1 on such input, and `batch` and `video batch` fail its row.
`strip_and_verify` refuses it before writing anything.

A `batch` or `video batch` directory with no supported file exits 2 and
creates no output directory. `visible` and `erase` strip and verify on a
staged sibling and publish nothing when a marker survives, as the library
`remove_visible` now does; the diffusion writer raises on a surviving
marker. An invisible engine that cannot start exits 1 without a traceback,
and the MCP server reports a child that could not start.

NotebookLM and Gemini slide-deck templates are recorded as not planned.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-19 11:23:59 -07:00

4.2 KiB

Raw Blame History

MCP server

remove-ai-watermarks mcp runs a Model Context Protocol server on stdin and stdout, so an agent client can identify and clean the user's own images and video without a shell. It is a thin wrapper: each tool runs one command of this CLI in a child process and returns that command's exit code, output path and text.

The subcommand ships since 0.46.0. The server uses only the Python standard library, so the default package runs it. The commands behind a tool need the same extras they need on the command line (CLI guide). A missing extra comes back as a tool error carrying the CLI's install hint.

Client configuration

Most clients take a command and arguments. With uv:

{
  "mcpServers": {
    "remove-ai-watermarks": {
      "command": "uvx",
      "args": ["remove-ai-watermarks", "mcp"]
    }
  }
}

To make visible-mark removal and pixel detectors available, name the extras:

{
  "mcpServers": {
    "remove-ai-watermarks": {
      "command": "uvx",
      "args": ["--from", "remove-ai-watermarks[visible,video]", "remove-ai-watermarks", "mcp"]
    }
  }
}

An existing installation can be started directly as remove-ai-watermarks mcp. Paths in tool calls are read and written on the machine that runs the server.

Tools

Tool	Runs	Writes
`identify`	`identify --json`, or `video identify --json` for a video suffix; `check_visible: false` adds `--no-visible`	Nothing
`remove`	`metadata --remove`, `visible` or `all` for an image; `video metadata --remove`, `video visible` or `video all` for a video	One output file, `<name>_clean` beside the source unless `output` is given
`batch`	`batch --mode` for images or `video batch --mode` for video	A separate output directory, `<dir>_clean` unless `output_dir` is given

mode is metadata (the default), visible or all. For an image, all adds the invisible-watermark scrub where the installed extras and a CUDA GPU allow it; video all removes visible marks and metadata only. The server never writes over an input: an output equal to the source, or an output_dir equal to the input directory, is refused before anything runs.

Exit codes keep their CLI meaning. 0 and 2 are results, not tool errors, and 2 means no supported signal was found, or a batch directory held nothing to process, which is unknown rather than clean. An input that is not a readable image or video exits 1, so identify on it is a tool error even though the command still printed a report. Click also exits 2 on a usage error such as a missing file; its Usage: line on stderr marks that case as a tool error. Every other nonzero exit code is returned with isError: true and the command's stderr.

Scope

The server carries the project's intended-use boundary in its instructions: it is for content the user generated or edited themselves, and not for stock, agency, marketplace or other marks that protect a third party's asset. See legal and safety.

Protocol

The server answers the initialize handshake for protocol versions 2025-11-25, 2025-06-18, 2025-03-26 and 2024-11-05, and lists its tools with input schemas and annotations: identify is read-only, and remove and batch write new files without destroying inputs. It does not implement server/discover. A client that probes it first, such as the official Python SDK's Client in its default mode, receives method-not-found and falls back to the handshake. tests/test_mcp_server.py runs that client against the real subcommand.

Registry listing

server.json describes the PyPI package for the official MCP registry under io.github.wiltodelta/remove-ai-watermarks. The registry verifies ownership by the mcp-name: marker in README.md, which becomes the PyPI description, so it can only verify a release whose README carries that marker. glama.json names the maintainer for Glama. Each release is published automatically; the workflow is described in release and distribution.

4.2 KiB Raw Blame History