# FaintMark (pypi · faintmark)

Invisible per-recipient image watermarks. Mark one copy per recipient, then identify a leaked copy.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- pypi · `faintmark`: 68/100 (this document), [markdown](https://verifymcp.io/servers/matchalatteguy-faintmark/faintmark.md), [page](https://verifymcp.io/servers/matchalatteguy-faintmark/faintmark)

## Channel facts

- Registry: `pypi`
- Package: `faintmark`
- Version: `0.1.0`
- 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-10-17.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 42 of 43 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - Dependency health was assessed across the 42 of 43 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 763 tokens (~254/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

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

FaintMark runs locally as a PyPI package, launched with uvx faintmark. 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 matchalatteguy-faintmark -- uvx faintmark
```

### Cursor

```json
{
  "mcpServers": {
    "matchalatteguy-faintmark": {
      "command": "uvx",
      "args": [
        "faintmark"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "matchalatteguy-faintmark": {
      "command": "uvx",
      "args": [
        "faintmark"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add matchalatteguy-faintmark -- uvx faintmark
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "matchalatteguy-faintmark": {
      "type": "local",
      "command": [
        "uvx",
        "faintmark"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add matchalatteguy-faintmark --command uvx --arg faintmark
```

### Hermes

```yaml
mcp_servers:
  matchalatteguy-faintmark:
    command: "uvx"
    args: ["faintmark"]
```

### Netclaw

```json
{
  "McpServers": {
    "matchalatteguy-faintmark": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "faintmark"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add matchalatteguy-faintmark -t stdio -c uvx -a faintmark
```

### Other

```json
{
  "mcpServers": {
    "matchalatteguy-faintmark": {
      "command": "uvx",
      "args": [
        "faintmark"
      ]
    }
  }
}
```

## 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-10-17 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-14 (score 53, +14)

- [security regression] Malware scan: pass → unverified
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100
- [functional] First check of Tool coverage: 100

### 2026-10-13 (score 39, +10)

- [security improvement] Known CVEs: unverified → partial
- [functional improvement] Dependency health: unverified → partial

### 2026-10-12 (score 29)

First indexed and scored.

## MCP tools (3)

### `mark_image` (~274 tokens)

Create one invisibly watermarked copy of an image per recipient label and register them locally. Use before sharing a picture with several people so a copy that turns up later can be traced to the label it was issued under. Writes files only and sends nothing; keeps the source format (JPEG stays JPEG; HEIC becomes JPEG). Accepts JPEG, PNG, WebP or HEIC (HEIC only when the server runs with the heic extra) up to 25 megapixels, with no animation, transparency, CMYK or 16-bit grayscale, and 1 to 100 labels of 1 to 200 printable characters. Returns the output folder and each copy's path, id and warnings. A warning starting with 'may not survive' means the copy is fragile, so suggest sending it as a file rather than a photo; one starting with 'JPEG recompression not tested' means that check was skipped. Cancelling the call stops it at the next copy and removes the copies written so far; a batch already being registered completes.

Input parameters:

- `format`: default: the source format
- `image_path` (string, required): absolute path of the image to mark
- `output_dir`: default: a marked/ folder beside the image
- `recipients` (array, required): 1 to 100 labels, one copy each

Output parameters:

- `copies` (array)
- `original` (string)
- `output_dir` (string)

### `check_image` (~324 tokens)

Decode the id in an image (any format Pillow opens, up to 100 megapixels) and look it up in the local registry; designed to work after chat-app recompression or resizing. status is matched (the id is registered to the returned recipient), unregistered (an id was read but it is not in this registry) or not_detected (no readable mark, which says nothing about where the image came from). A match also reports same_image when a stored hash exists, a perceptual-hash comparison with the issued copy: false means they differ beyond the threshold, which cropping or an id copied into another picture can cause. same_image true is not authentication: a tuned forgery passed it in our measurements. deep=true also tries a flip and small rotations (transform names the one that recovered the result), and when nothing is detected lists the registered ids within 26 of 96 codeword bits of the raw decoder output as suspects (up to three, each with id, recipient and bit_errors, plus same_image when a stored hash exists; empty when none is that close) and registry_size. Suspects are uncalibrated candidates by codeword distance: they can be coincidental (more likely with a large registry) or forged, and they never mean a match. files=true adds the original file name and the issued copy's path.

Input parameters:

- `deep` (boolean): try flips and rotations, then list suspects
- `files` (boolean): include file names and paths
- `image_path` (string, required): absolute path of the image to check

Output parameters:

- `id` (string)
- `marked_at` (string)
- `original` (string)
- `path` (string)
- `recipient` (string)
- `registry_size` (integer)
- `same_image` (boolean)
- `status` (string)
- `suspects` (array)
- `transform` (string)

### `list_copies` (~46 tokens)

List registered copies, newest first. files=true adds file names and paths.

Input parameters:

- `files` (boolean): include file names and paths
- `limit` (integer): newest N copies

Output parameters:

- `copies` (array)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/matchalatteguy-faintmark/faintmark#diagnostics

## Score history

- 2026-10-17: 68
- 2026-10-16: 53
- 2026-10-15: 53
- 2026-10-14: 53
- 2026-10-13: 39
- 2026-10-12: 29

## Common questions

### What is the FaintMark MCP server?

FaintMark is an MCP server listed in the public MCP registry as io.github.matchalatteguy/faintmark. Invisible per-recipient image watermarks. Mark one copy per recipient, then identify a leaked copy. This page covers its PyPI package (faintmark).

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

FaintMark scores 68 out of 100 on VerifyMCP. 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 FaintMark MCP server expose?

FaintMark exposes 3 tools: mark_image, check_image, list_copies. Their descriptions and schemas cost roughly 644 tokens of context every time the server is loaded.

### Is the FaintMark MCP server still maintained?

FaintMark is still listed as active in the MCP registry. We last reached this channel on 17 October 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 FaintMark MCP server under?

FaintMark 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

- PyPI project: https://pypi.org/project/faintmark/
- Socket report: https://socket.dev/pypi/package/faintmark
- Repository: https://github.com/matchalatteguy/FaintMark
- Changelog RSS feed: https://verifymcp.io/servers/matchalatteguy-faintmark/faintmark.xml
- Changelog JSON feed: https://verifymcp.io/servers/matchalatteguy-faintmark/faintmark.json
- HTML version of this page: https://verifymcp.io/servers/matchalatteguy-faintmark/faintmark