Tool · TypeScript

sign-cli

sign-cli v1.1.1 0 26/wk on npm Latest from npm · checked Mon, 11 May 2026

A command-line e-signature tool for humans, ops teams, and AI agents. Send PDFs to multiple signers across multiple providers, capture every event in a hash-chained audit log, and prove what was signed and when with RFC 3161 timestamps.

TL;DR — npm i -g sign-cli — or npx sign-cli demo for an offline five-second walkthrough. Pick a provider (Dropbox Sign, DocuSign, SignWell, or the local test provider) and send a PDF with one command.

sign-cli — offline demo flow

Live demo

See sign-cli sending a real PDF

Read-only browser demo of the full send → sign → verify → receipt flow. Sandboxes reset every few hours.

Open the live demo →

What it does

Multi-provider sending. Dropbox Sign, DocuSign, and SignWell are wired in; the local provider runs offline for testing and CI.
Per-signer approval tokens with TTL. Every signer gets an explicit token tied to their email; agents can't impersonate humans, and tokens expire.
Hash-chained audit events. Every signing event hashes into the previous event. Tampering with any past entry breaks the chain and fails verification.
RFC 3161 timestamping. External timestamp authority anchors prove a signature existed by a given date — durable evidence that survives even if the provider disappears.
Bulk via CSV. Send the same document to many signers, or many documents to one signer, from a single CSV file.
PDF verification. Verify a signed PDF later, off-line, with the receipt bundle.
MCP server included. An LLM agent (Claude, Cursor, Codex, etc.) can drive the signing workflow with the same primitives you use from the shell.

Quickstart

install + send

# Install
npm i -g sign-cli

# Or run the offline demo without installing
npx sign-cli demo

# Send a single document to two signers
sign-cli send \
  --file contract.pdf \
  --signer "alice@acme.com:Alice Founder" \
  --signer "bob@beta.com:Bob Counsel" \
  --provider sign-well

Verify a signed PDF

Verification is offline and works on any signed PDF the tool produced. The receipt bundle contains the audit chain, the timestamp anchor, and metadata you can hand to opposing counsel or a court without further cooperation from the signing provider.

verify

sign-cli verify contract.signed.pdf
# OK · 2 signers · audit chain intact · timestamp anchor verified

MCP server for agents

Every CLI command is also exposed as an MCP tool over stdio. Wire it into Claude Code, Cursor, or any other MCP-aware client and your agent can drive the signing workflow with the same primitives — including the per-signer approval-token guardrail, so a runaway agent can't sign on a human's behalf.

npx sign-cli mcp        # start the MCP server on stdio

Where it fits in the workflow

sign-cli is the last step in the contract pipeline — after nda-review-cli produces the agreed text and docx2pdf-cli renders the PDF. See the full workflow page for the chained commands.

It also stands alone for any document that needs signing — vendor agreements, employment documents, board consents, anything PDF.

Repo

github.com/DrBaher/sign-cli · MIT licensed · TypeScript · MCP server included.