haruodev/tamperlens-mcp

MCP server for Tamperlens — ask whether a document was
edited, whether its redactions held, and whether it is safe for a model to read,
**before** it reaches your agent's context.
No key is required to try it — without one you get the anonymous allowance of
**10 documents an hour**. A free key at
tamperlens.com/account raises that to 50 a
month with no card.
Tools
| Tool | Answers |
|---|---|
| inspect_document | Was this edited after it was written? Revisions appended after the original save, metadata that disagrees with itself, editor fingerprints, signature coverage and integrity, hidden text, macros, AI-generator traces in images — **and** whether the file carries text addressed to a language model rather than to a reader. |
| triage_document | Is this worth ingesting, and what does it cost to open? The cheap pre-flight: structure, metadata, signatures and presence flags only — no per-page content walk — at a fraction of the I/O. Returns the risk band, the measured cost (bytes read, bytes expanded, expansion ratio) and a triage block naming the page-content families it did **not** check. A quiet triage is not a clean document — use it to route, then inspect_document for the full check. |
| check_redaction | Did the redaction actually remove anything? Covering text with a black box hides it from a person and removes nothing from the file. |
| compare_documents | Is this the same file as the original I already hold, unchanged? |
| inspect_case | Do these documents of one case (three months of statements, a payslip and its statement) disagree with each other? One report per document, plus what they share that independent documents should not: the same file twice, one base file's /ID or font subset tags, the same creation second. Inconsistencies to review, never verdicts. Needs a key; a case of N documents costs N. Takes paths and/or urls, 2 to 10 in all. |
Accepts PDF; Word, Excel and PowerPoint (.docx, .xlsx, .pptx and the
macro-enabled twins); and JPEG, PNG, WebP, HEIC/HEIF and AVIF.
A local path or a URL
inspect_document, check_redaction and compare_documents (as
originalUrl/candidateUrl) take **either** a local path **or** an http/https
url — not both. inspect_case takes lists of both (paths, urls). A url is fetched **by this server, on your own machine, over
your own network**, and only the bytes are sent on to Tamperlens. That is why the
option lives here and not on the REST API: a server-side fetch of a
caller-supplied URL is an SSRF risk on the API host, whereas fetching from your
machine reaches only what you can already reach. It is still guarded: http/https
only (re-checked at every redirect), a redirect cap, a 30s timeout
(TAMPERLENS_FETCH_TIMEOUT_MS to tune), and the same 10 MB cap, enforced on the
bytes received rather than a Content-Length that can lie.
It also **checks the destination IP, not just the scheme**: a url that points
at — or redirects to, or resolves by DNS to — a loopback, link-local/metadata
(169.254.169.254), private or otherwise non-routable address is refused, and
the address it connects to is pinned to the one it validated, so DNS rebinding
cannot slip an internal address past the check. The check re-runs at every
redirect hop. If you genuinely need to fetch from an internal host, allow-list
specific addresses with TAMPERLENS_FETCH_ALLOW_IPS (comma-separated; empty by
default, and the default reaches nothing internal).
> **The path argument reads any local file and sends its bytes to the API.**