strip-ai-metadata-mcp
Related Servers
Alternatives to strip-ai-metadata-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables Claude Desktop to redact and count personal data in PDFs and images, strip hidden metadata from photos, anonymize Word and text files, prepare watermarked ID copies, and compare contract versions using only user-approved local folders. All processing runs offline on the user's computer, creating new copies instead of modifying or deleting the originals.Apache 2.0- AlicenseCqualityAmaintenanceIdentify and remove AI provenance metadata (C2PA, EXIF, IPTC, XMP, TC260), visible AI-generator labels and supported invisible watermarks from images and video you generated yourself. Runs locally over stdio with uvx.242,884 PyPI6,357Apache 2.0
- AlicenseAqualityCmaintenanceEnables local magic-byte file identification, Office document metadata and provenance inspection, and lossless removal of identifying image metadata. It performs bounded, local-only inspection without external dependencies.3MIT
- FlicenseNot gradedqualityBmaintenanceEnables Claude to work on documents containing personal data by pseudonymizing names, addresses, IBANs, health data and other GDPR categories locally before they are sent, then restoring the real values on your own machine. Supports Word, Excel, PowerPoint, PDF, CSV, Markdown, e-mail and other formats with consistent pseudonyms per project and no data leaving the computer.-
- AlicenseAqualityBmaintenanceEnables Claude Code, Cursor, Codex and other MCP clients to generate and edit images and videos directly in a project using AI subscriptions the user already pays for, without API keys or extra billing. Also provides local media tools such as background removal, video editing for social formats, and automatic resizing and optimization of results.25Apache 2.0
- FlicenseNot gradedqualityDmaintenanceAutomatically detects and obfuscates sensitive data (PII, secrets, etc.) before Claude processes it, with lossless restoration for client deliverables.6-
TDQS
Scored across 2 tools
The two tools are cleanly opposed: clean_files mutates files by stripping metadata, while inspect_files only reports metadata without changing anything. Descriptions explicitly cross-reference the pair (inspect to confirm a clean copy is clean), so an agent can never mistake one for the other.
Both names follow the same verb_noun snake_case convention (clean_files, inspect_files) and share the _files noun, giving a predictable, uniform pattern.
Two tools is on the thin side of the typical range, but for a focused local metadata-stripping utility the inspect+clean pairing is exactly the necessary surface with nothing extraneous. It is minimal rather than bloated.
The domain lifecycle is covered: inspect before sharing, clean, then inspect again to verify. Minor gaps exist, such as no selective per-tag removal or dry-run/batch summary report, but agents can work around these by re-inspecting cleaned output.