emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Two companies' assistants put a standard mutual NDA in place over three sealed emails.
作者提供的原文
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
用 NDA Handshake 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 NDA Handshake,或回答中出现 NDA Handshake 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 NDA Handshake
NDA Handshake 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 NDA Handshake 的应用
B · 聊天与邮件 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
Claude Code 暂时无法连接 NDA Handshake
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 NDA Handshake 的应用
Cursor 暂时无法连接 NDA Handshake
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 NDA Handshake 的应用
VS Code 暂时无法连接 NDA Handshake
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 NDA Handshake 的应用
NDA_HANDSHAKE_STORAGE env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 Ivolver 验证,该账户拥有此仓库
代码最后更新于昨天
使用 Apache-2.0
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/ivolver-nda-handshake)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于昨天,最新版本(0.14.3)于昨天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Build and fix Discord bots from a chat. Kite hosts them 24/7, with no code to deploy.
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.
CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.
| 本项 NDA Handshake | emailmd | Kite Discord Bot Builder | e2a — email for AI agents | Infobip MCP | kernelCAD | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 3/3 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | Apache-2.0 | MIT | AGPL-3.0 | Apache-2.0 | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Two companies' AI assistants put a standard mutual NDA in place over three emails, with no redlines and no signature round.
Protocol v0.7. This is not legal advice.
Most NDAs between companies say nearly the same thing, yet each one still costs days of back and forth. NDA Handshake removes that step for the routine case.
Each company writes down, once, the NDA terms it is willing to accept, and a person with authority approves them in advance. When two companies need an NDA, their assistants exchange three short emails and both arrive at the same agreement, built on the Common Paper Mutual NDA. If the two sets of positions meet, the NDA is in place when the third email is sent. Nobody opens a document to sign it. People still decide to start, and people set every position.
You tell your assistant:
Start an NDA handshake with jane@acme.example about a possible partnership.
| Who | What the person does | What the assistant does |
|---|---|---|
| You | Say that one sentence | Seals your positions and sends the invitation |
| Acme | Answers one question: reply to this invitation? | Sends Acme's positions |
| You | Nothing | Works out the NDA and sends the result. The NDA is now in place. Tells you the terms |
| Acme | Nothing | Checks the result independently within one business day, tells Acme the terms |
The emails are written for the people who receive them, with a short block at the end for the assistants:
Hello,
Before we get into the details, Harbor Example LLC would like to put a mutual NDA in place. We use NDA Handshake, an open protocol that lets our assistants settle a standard NDA so nobody has to trade redlines.
What we would like to discuss: Evaluating a possible partnership
Neither side sees the other's positions first, so there is no peeking and no haggling. If the positions meet, the NDA is in place right then. Nobody has to sign anything, because each company approves its positions in advance. If your assistant already knows NDA Handshake, just ask it to handle this email.
New to it? The page below shows how to add it. It takes a few minutes, and your assistant can work out your positions from NDAs you have already signed. Or simply reply and we will send a draft the old-fashioned way.
--- for the assistants (please leave this part as it is) --- nda-handshake: invitation ...
When a company sets up, a person with authority to bind it to NDAs reads one fixed confirmation and types their name and title. It says, in short: any NDA a handshake produces inside the positions in this file is approved for the company and is executed when the exchange completes, and I have authority to say so. That is the only approval. From then on:
A company that would rather sign each NDA by hand does not give the confirmation. It cannot use a handshake, and gets an ordinary draft on the same standard form instead. The full text of the confirmation is in forms/confirmation/confirmation.md, and SPEC.md explains the legal basis and its limits. Have your own counsel read it before you confirm.
It has been run end to end between two different AI assistants on separate machines, each verifying the other's result.
The length of the NDA, the confidentiality period and when it starts, governing law, venue, whether confidential material must be marked, a residuals clause, sharing with affiliates, and the standard form itself. A company can take the protocol's balanced default positions with one line, or set its own. GUIDE.md walks through each choice in plain English.
If two companies' positions do not meet, there is no NDA from the handshake. Each assistant tells its own person which terms failed, with a suggestion, and the people take it from there. Assistants do not bargain with each other. If a company needs something the protocol leaves out, such as a non-solicit or a one-way NDA, the handshake says so and steps aside.
nda-handshake- .mcpb from the latest release and open it in Claude Desktop. It asks where to keep your files and installs itself. Other assistants can run it from the source; see "Install by hand" below.If you received an invitation and do not have NDA Handshake yet, do those three steps and then ask your assistant to handle the invitation.
Install it only from the project's Releases page or a connector directory you already trust, never from a link in an email.
GUIDE.md: writing your company's file, one choice at a time.SPEC.md: the protocol. The file format, the nine terms, what is excluded, the matching rules and the sealed exchange.The rest of this page is for people who want to run the pieces directly or build their own implementation.
Requires Python 3.10 or newer. To install everything the project uses:
pip install -r requirements.txt
The matcher alone needs only PyYAML.
python3 match.py examples/harbor-fictional/nda-handshake.md examples/lakeside-fictional/nda-handshake.md \ --purpose "Evaluating a potential business relationship" \ --out out/harbor-lakeside
Outputs in the --out folder:
result.json: status, agreed terms, conflicts, missing info, open items, terms hash and file fingerprintscover-page.md: draft cover page (not written unless terms are agreed)To see the conflict path (expected status CONFLICTS, four conflicts):
python3 match.py examples/harbor-fictional/nda-handshake.md examples/northwind-fictional/nda-handshake.md \ --purpose "Evaluating a potential business relationship" \ --out out/harbor-northwind
To see the out-of-protocol path (expected status OUT_OF_PROTOCOL):
python3 match.py examples/harbor-fictional/nda-handshake.md examples/outlier-fictional/nda-handshake.md \ --purpose "Evaluating a potential business relationship" \ --out out/harbor-outlier
To see what happens when a company has not given its confirmation (expected status AGREED_PENDING_INFO, with the confirmation listed as missing):
python3 match.py examples/harbor-fictional/nda-handshake.md examples/tidewater-fictional/nda-handshake.md \ --purpose "Evaluating a potential business relationship" \ --out out/harbor-tidewater
Running the matcher by hand executes nothing. An NDA is executed only through the sealed exchange.
To see a principled tie-break (two New York companies tie between Delaware and New York, and the result is New York because both are formed there):
python3 match.py examples/lakeside-fictional/nda-handshake.md examples/midtown-fictional/nda-handshake.md \ --purpose "Evaluating a potential business relationship" \ --out out/lakeside-midtown
To see the default positions (two companies that state no positions of their own and simply set profile: default):
python3 match.py examples/pioneer-fictional/nda-handshake.md examples/quarry-fictional/nda-handshake.md \ --purpose "Evaluating a potential business relationship" \ --out out/pioneer-quarry
Every result includes a summary showing, term by term, both sides' positions, the outcome and the rule that produced it.
To print a file's fingerprint, for exchanging before the files themselves:
python3 match.py --fingerprint examples/harbor-fictional/nda-handshake.md
A handshake writes the executed NDA into each company's deal folder. To turn a bare AGREED match result into a Word document by hand (requires pip install python-docx):
python3 make_cover_page.py out/harbor-lakeside/result.json
This writes the document next to the result, named for both companies (for example MNDA_Harbor-Example-LLC_and_Lakeside-Example-LLC.docx; an executed NDA starts with its date, as in 2026-11-14_MNDA_...). It holds the Common Paper Cover Page filled in with the agreed terms, the Standard Terms attached for convenience, and a one-page handshake record that is not part of the agreement. The record shows how each term was reached. A copy made this way, outside a completed handshake, is marked "Not executed". Any other status produces no document.
The schema/ folder holds JSON Schemas for the two data formats: nda-handshake.schema.json for the fields at the top of an nda-handshake.md, and result.schema.json for a matcher's result.json. Use them to validate a file or a result in any language. SPEC.md remains the authority.
The Word document carries its terms hash and protocol version in its document properties, so software that receives only the document can find the matching result.
examples/expected-results.json lists each example pair with its expected status, terms hash and conflicts, plus each example file's fingerprint. To check this matcher against it:
python3 check_examples.py
Anyone building another implementation of the protocol can r