Ext Ops Panel
Open dashboard
Comparison

Remove AI Watermarks vs TruthScan

Remove AI Watermarks is a plugin bundle for AI coding tools published by wiltodelta. Marketplaces we read that list it: 1 (Community GitHub marketplaces). TruthScan is an MCP server published by truthscan.com. 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
MarketplaceRemove AI WatermarksTruthScan
Community marketplace wiltodelta/remove-ai-watermarks Listed
Version: 1.0.19
Forks (GitHub): 597
Stars (GitHub): 6 384
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

Remove AI Watermarks vs TruthScan
FactRemove AI WatermarksTruthScan
Marketplaces that list it11
Stars (GitHub) (differs)6 384No figure on GitHub
Forks (GitHub) (differs)597No figure on GitHub
Last release (differs)2026-11-11Not published
Where it runs (differs)Installs as a plugin bundleRemote server (truthscan.com/api/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/wiltodelta/remove-ai-watermarksNot stated
Changes in the last 7 days (differs)40
First seen (differs)2026-11-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 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

Remove AI Watermarks

In its own words, on Community GitHub marketplaces:

Identify and remove AI provenance marks from images, video, and text the user generated or edited. Use when the user asks to strip Gemini sparkles, SynthID, Microsoft InvisMark, Meta Content Seal, C2PA, EXIF/XMP AI metadata, Sora/Veo/Seedance/Doubao/Dola/Hailuo/Kling labels, or other AI watermarks, or asks whether a file was AI-generated. Do not use for stock-agency, marketplace, classifieds, or other third-party paid-asset watermarks.

TruthScan

In its own words, on Official MCP Registry:

Detect whether an image is AI-generated or real, with an AI-probability score and confidence.

How to run each

Remove AI Watermarks As a Claude Code plugin

Claude Code
/plugin marketplace add wiltodelta/remove-ai-watermarks
/plugin install remove-ai-watermarks@remove-ai-watermarks

TruthScan As a remote MCP server

Claude Code
claude mcp add --transport http truthscan https://truthscan.com/api/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only TruthScan 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: Remove AI Watermarks · What it can do: TruthScan · 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.

Where the data comes from: how the catalog is built