AI Metadata Cleaner

com.aimetadatacleanerPublished by aimetadatacleaner.comOfficial publisherv0.1.3Updated Oct 25, 2026

Remove GPS, device details, dates and AI labels from video, PDF, RAW and photo files.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

A remote or local MCP server that lets an assistant strip GPS, device details, dates and AI labels from video, PDF, RAW and photo files.

What you can do
Clean metadata from media files: remove GPS location, device details, dates and AI labels from video, PDF, RAW and photo files. Work through a hosted remote endpoint or a local npm package over stdio. Access is tied to a paid Business plan API key.
When to use it
Useful when you want an assistant to prepare photos, videos, PDFs or RAW files for sharing by removing embedded location, device and date information and AI provenance labels before publishing.
Requirements
A remote endpoint or the local npm package (Node.js for stdio). OAuth authentication is required, plus an AI Metadata Cleaner API key supplied in the AMC_API_KEY environment variable; the key comes from a Business plan account.
Before you install
Requires an account API key (AMC_API_KEY) tied to a paid Business plan, so check cost and plan terms first. The server modifies files by removing metadata, so keep originals and verify results before sharing. Files are processed by a third-party service when using the remote endpoint.

Installation

In SourceWeft

  1. Open AI Metadata Cleaner in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.aimetadatacleaner%2Fmetadata-cleaner/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ai-metadata-cleaner": {
      "type": "http",
      "url": "https://api.aimetadatacleaner.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.3LatestSep 27, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.