Integrations

Three ways to run Tamperlens without writing a parser: the verified n8n community node, the MCP server for agents, and the HTTP API. All three call the same engine and use the same key.

n8n: the community node

For a workflow that already receives documents: an inbox, a form, a watched folder.

In n8n, open Settings > Community nodes > Install and enter the package name: 

n8n-nodes-tamperlens

The node reads the document from the incoming item's binary data and has three operations:

  • Inspect Document: the full report, with summary.riskBand (low, elevated or high) and each signal with its evidence. One document.
  • Get Metadata: authors, tools, dates and device traces, without a full inspection. One document.
  • Compare Documents: a candidate PDF against the original you already trust. Two documents.

A typical flow routes on summary.riskBand with an IF node: low continues, anything else goes to a person with the signals attached. The credential test calls an unmetered endpoint, so checking your key spends nothing.

Route the failures too. In the node's Settings, set On Error to Continue (using error output) and send that output, with any attachment of a type Tamperlens does not read, to the same person marked as not checked. Otherwise a file that makes the inspection fail reaches no one, and that is the file a forger would send. Our n8n workflow templates are built this way: an unsupported file type or a failed inspection becomes a not checked alert, not silence.

MCP: the server for agents

For an agent that is about to read a document it did not write.

npx tamperlens-mcp

Published on npm and in the official MCP Registry as com.tamperlens/mcp. It gives the agent four tools: inspect_document, triage_document, check_redaction and compare_documents. Put your key in TAMPERLENS_API_KEY; without one it runs on the anonymous allowance of 10 documents an hour.

The tools take a local file path and send that file's bytes to the API. Set TAMPERLENS_ALLOWED_DIRS to the folder your documents arrive in, so an agent cannot be steered into reading anything else.

The HTTP API

For everything else: one POST, a JSON report back.

curl -s https://tamperlens.com/api/v1/inspect -F [email protected]

No key is needed to try it: 10 documents an hour per IP, full report. With a key, the calls count against your plan's monthly quota.

  • API quickstart

    A key, one call, and the fields to branch on.

  • API reference

    Authentication, both request forms, /compare and /metadata, errors and limits.

  • openapi.json

    The OpenAPI 3.0 document, for SDK generators and agents.

One key for all three

Create a key once. The n8n credential, the MCP server's TAMPERLENS_API_KEY and the API's Authorization: Bearer header all take it, and every call counts against the same quota on your usage dashboard.

Whichever way you call it, the report carries risk signals and their evidence, never an approve or reject verdict. The decision stays in your workflow.