explaingit

kychee-com/kysigned

Analysis updated 2026-05-18

35TypeScriptAudience · developerComplexity · 3/5Setup · moderate

TLDR

A tool that turns a forwarded email into a legally verifiable e-signature, using the cryptographic DKIM seal your email provider already adds, checkable offline forever.

Mindmap

mindmap
  root((repo))
    What it does
      Email-based signatures
      DKIM as proof
      Offline verification
    Tech stack
      TypeScript
      run402
      MCP server
    Use cases
      No-account signing
      Self-hosted deployment
      AI-driven signing
    Audience
      Developers
      Small businesses

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Get a document signed by email with no account or app needed for the signer.

USE CASE 2

Deploy your own self-hosted signing service under your own domain using run402.

USE CASE 3

Verify a signed document's authenticity offline, even if the kysigned service disappears.

USE CASE 4

Let an AI assistant send documents for signature and check their status through the bundled MCP server.

What is it built with?

TypeScriptDKIMrun402MCP

How does it compare?

kychee-com/kysignedanandsaini18/deadskillskarminski/codevinci
Stars353535
LanguageTypeScriptTypeScriptTypeScript
Setup difficultymoderateeasymoderate
Complexity3/51/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 1h+

Self-hosting requires a run402 project, environment variable configuration, and mailbox setup, the hosted kysigned.com option needs none of that.

Not sufficiently specified in the provided material.

In plain English

kysigned is a way to get legally meaningful e-signatures on a document using nothing more than email, instead of a dedicated signing app or account. A signer receives an email with the document attached, forwards it back with the words I sign this document as the first line, and that is the entire signing process from their side. No account, no password, no separate app to install. The clever part is what makes that forwarded email trustworthy as proof. Every email provider already attaches a cryptographic seal called DKIM to outgoing messages, mainly to prevent spoofing. kysigned uses that existing seal as the actual signature: since only the real provider can produce that seal for that sender's address, nobody else could have forged the forward. The tool checks that the forwarded attachment is byte for byte identical to the original document, stamps the time it arrived twice for extra durability, and keeps a public timestamped record of the DKIM key used, so that even if an email provider later changes or exposes its keys, an old signature cannot be faked or denied afterward. Once everyone involved has signed, every party gets one PDF evidence bundle that anyone can check on their own computer, even with no internet connection and even if the kysigned service itself no longer exists. There are two ways to use it. The simplest is to sign documents directly at kysigned.com, paying a small fee per document with no setup required. The other is to deploy your own copy of the entire application, using a hosting platform called run402 that handles the email, database, and server pieces for you, so your instance runs under your own domain rather than the original one. A deployed instance can also be controlled through an MCP server, letting an AI assistant like Claude send a document for signature and check its status on your behalf. This is aimed at developers or small businesses who want low cost, verifiable signatures they can fully control and self-host, rather than a general consumer product. It requires comfort with the command line and environment variables to run your own instance, though using the hosted version needs none of that.

Copy-paste prompts

Prompt 1
Walk me through deploying my own kysigned instance on run402 with my own allowed sender list.
Prompt 2
Explain how kysigned uses DKIM email signatures as legal proof instead of a traditional e-signature app.
Prompt 3
Show me how to configure the kysigned-mcp server so Claude can send a PDF for signature.
Prompt 4
Help me customize the branding and home page of my kysigned deployment using VITE_OPERATOR_CONFIG.
Prompt 5
Explain the evidence bundle kysigned produces and how a signer would verify it themselves.

Frequently asked questions

What is kysigned?

A tool that turns a forwarded email into a legally verifiable e-signature, using the cryptographic DKIM seal your email provider already adds, checkable offline forever.

What language is kysigned written in?

Mainly TypeScript. The stack also includes TypeScript, DKIM, run402.

What license does kysigned use?

Not sufficiently specified in the provided material.

How hard is kysigned to set up?

Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.

Who is kysigned for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.