# com.tamperlens/mcp (npm · tamperlens-mcp)

Was this document edited, did its redactions hold, is it safe for a model to read — Tamperlens API.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- npm · `tamperlens-mcp`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-tamperlens-mcp/tamperlens-mcp.md), [page](https://verifymcp.io/servers/com-tamperlens-mcp/tamperlens-mcp)

## Channel facts

- Registry: `npm`
- Package: `tamperlens-mcp`
- Version: `1.30.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-08-20.

- **Supply Chain Security**: 100/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.
  - 0 of 3 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 587 tokens (~195/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.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (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

### Claude

```bash
claude mcp add com-tamperlens-mcp -- npx -y tamperlens-mcp
```

### Codex

```bash
codex mcp add com-tamperlens-mcp -- npx -y tamperlens-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-tamperlens-mcp --command npx --arg -y --arg tamperlens-mcp
```

### Hermes

```yaml
mcp_servers:
  com-tamperlens-mcp:
    command: "npx"
    args: ["-y", "tamperlens-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "com-tamperlens-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tamperlens-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-08-19 (score 63, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-08-18 (score 48)

First indexed and scored.

## MCP tools (3)

### `inspect_document` (~361 tokens)

Inspect a document or image for fraud and tamper signals: revisions appended after the original save, metadata that disagrees with itself, editor fingerprints, signature coverage gaps, text still readable under a redaction box, unaccepted tracked changes whose deleted text is still recoverable, hidden text, hidden spreadsheet sheets, macros, and AI-generator or editor traces in images. Returns risk signals with the raw evidence behind each one — never a verdict on authenticity. Accepts PDF; Word, Excel and PowerPoint documents (.docx, .xlsx, .pptx and macro-enabled twins); and JPEG, PNG, WebP, HEIC/HEIF and AVIF images.

ALSO ANSWERS: is this file safe for a model to read? Document properties, XMP, annotations, attachment names, docProps, comments and hidden Word runs are checked for text written to be read by a language model rather than by a person — the prompt-injection carriers an extraction pipeline surfaces and a human reader never sees. Call this BEFORE the document reaches your own context. The recovered text itself is never returned through this tool: you get the cue categories, the counts and which kind of field carried it, because reading the payload is the attack.

Input parameters:

- `issuer` (string): Optional issuer slug (e.g. 'chase') to additionally compare the document against a structural baseline of genuine documents from that institution. PDFs only — ignored for Office documents and images.
- `path` (string, required): Absolute path to the document on this machine — PDF, Office document or image. Max 10 MB.
- `policy` (object): Optional. Your own risk thresholds and signal rules; the response gains a verdict of accept/review/reject computed from them. Nothing about the report changes.

### `check_redaction` (~117 tokens)

Check whether a PDF's redactions actually removed anything. Covering text with a black box hides it from a reader and removes nothing from the file, so the words stay extractable. This reads paint order to catch a plain drawn rectangle — which carries no redaction annotation at all and is the failure behind most published redaction leaks — and separately catches redaction marks that were never applied. Use this before a document is filed or released.

Input parameters:

- `path` (string, required): Absolute path to the PDF on this machine. Max 10 MB.

### `compare_documents` (~109 tokens)

Compare a candidate document against the original you already hold, and answer the question a single-file check cannot: is this the same file, unchanged? Reports byte identity (the only proof), revision ancestry when the candidate contains the original as a byte prefix, or a field-by-field structural diff when both were rewritten whole. Renders nothing and compares no pixels.

Input parameters:

- `candidatePath` (string, required): Absolute path to the document being checked.
- `originalPath` (string, required): Absolute path to the document you trust.

## Diagnostics

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

## Score history

- 2026-08-20: 63
- 2026-08-19: 63
- 2026-08-18: 48

## Links

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