# unmarking (npm · unmarking-mcp)

Inspect and remove C2PA content credentials from AI-generated images, video and audio. Free, no key.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.unmark.ing`: 72/100, [markdown](https://verifymcp.io/servers/ing-unmark-unmarking/api.md), [page](https://verifymcp.io/servers/ing-unmark-unmarking/api)
- npm · `unmarking-mcp`: 72/100 (this document), [markdown](https://verifymcp.io/servers/ing-unmark-unmarking/unmarking-mcp.md), [page](https://verifymcp.io/servers/ing-unmark-unmarking/unmarking-mcp)

## Channel facts

- Registry: `npm`
- Package: `unmarking-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 16 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 202 tokens (~101/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "strip_file" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the unmarking MCP server?

unmarking runs locally as an npm package, launched with npx -y unmarking-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add ing-unmark-unmarking -- npx -y unmarking-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ing-unmark-unmarking": {
      "command": "npx",
      "args": [
        "-y",
        "unmarking-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ing-unmark-unmarking": {
      "command": "npx",
      "args": [
        "-y",
        "unmarking-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ing-unmark-unmarking -- npx -y unmarking-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ing-unmark-unmarking": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "unmarking-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ing-unmark-unmarking --command npx --arg -y --arg unmarking-mcp
```

### Hermes

```yaml
mcp_servers:
  ing-unmark-unmarking:
    command: "npx"
    args: ["-y", "unmarking-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ing-unmark-unmarking": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "unmarking-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ing-unmark-unmarking -t stdio -c npx -a -y unmarking-mcp
```

### Other

```json
{
  "mcpServers": {
    "ing-unmark-unmarking": {
      "command": "npx",
      "args": [
        "-y",
        "unmarking-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 68, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-04 (score 64, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-03 (score 49)

First indexed and scored.

## MCP tools (2)

### `inspect_file` (~87 tokens)

Inspect content credential

Reads the C2PA content credential embedded in an image, video or audio file and reports its signer, including whether the file was made with Claude. Nothing is modified.

Input parameters:

- `path` (string): Path to a file on this machine, absolute or relative to the working directory
- `url` (string): http(s) URL of a file, for files that are not on this machine

### `strip_file` (~115 tokens)

Remove content credential

Removes the C2PA content credential from an image, video or audio file and writes the cleaned copy next to the original. Pixels, frames and samples stay untouched.

Input parameters:

- `output` (string): Where to write the cleaned file. Defaults to the original name with a -clean suffix, in the same directory
- `path` (string): Path to a file on this machine, absolute or relative to the working directory
- `url` (string): http(s) URL of a file, for files that are not on this machine

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ing-unmark-unmarking/unmarking-mcp#diagnostics

## Score history

- 2026-09-20: 72
- 2026-09-19: 72
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 69
- 2026-09-13: 69
- 2026-09-12: 68
- 2026-09-11: 68
- 2026-09-10: 64
- 2026-09-09: 64
- 2026-09-08: 64
- 2026-09-07: 64
- 2026-09-06: 64
- 2026-09-05: 64
- 2026-09-04: 64
- 2026-09-03: 49

## Common questions

### What is the unmarking MCP server?

unmarking is an MCP server listed in the public MCP registry as ing.unmark/unmarking. Inspect and remove C2PA content credentials from AI-generated images, video and audio. Free, no key. This page covers its npm package (unmarking-mcp).

### Is the unmarking MCP server safe to use?

unmarking scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the unmarking MCP server expose?

unmarking exposes 2 tools: inspect_file, strip_file. Their descriptions and schemas cost roughly 202 tokens of context every time the server is loaded.

### Is the unmarking MCP server still maintained?

unmarking is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the unmarking MCP server under?

unmarking declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/unmarking-mcp
- Socket report: https://socket.dev/npm/package/unmarking-mcp
- Website: https://unmark.ing/developers/
- Changelog RSS feed: https://verifymcp.io/servers/ing-unmark-unmarking/unmarking-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ing-unmark-unmarking/unmarking-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ing-unmark-unmarking/unmarking-mcp