GoodSign

io.goodsign由 goodsign.io 发布官方发布者v1.0.0更新于 Oct 28, 2026

Send documents for e-signature, track and remind signers, and download signed PDFs.

已验证Streamable HTTP可网页运行效率与工作流商业与电商

概览

AI 生成的概览

GoodSign 电子签名服务器:让助手发送待签文件、跟踪签署进度、提醒签署人并下载已签 PDF。

可以做什么
  • 查看账户名称与剩余额度
  • 按状态列出模板和文件,并获取某个文件或模板的完整详情,包括签署人键与字段键
  • 把 PDF 上传到短期链接并转成 GoodSign 文件,依据文本标签自动生成字段
  • 用模板发送文件请求电子签名,或先存为草稿
  • 提醒未签署人、作废已发送文件,并获取 PDF 与审计证书的带鉴权下载链接
适用场景
适合需要在对话中发送合同、保密协议、工作说明书等文件请求签署并跟踪进度时使用,也适合回答“还有哪些文件待签”或获取已完成的签署 PDF。
运行要求
远程 streamable HTTP 端点 goodsign.io。需要 GoodSign 账户,并以 Authorization bearer 令牌形式提供 API 密钥;每发送一个信封消耗 1 个额度。上传 PDF 需另行向返回的上传链接发起 PUT,下载需在 shell 中用 curl 获取。
安装前请注意
用模板发送会向真实收件人发邮件并消耗额度,调用前应确认签署人姓名与邮箱,或使用草稿模式。提醒会发送真实邮件。作废不可撤销,且默认会通知签署人。API 密钥可访问账户内文件;下载链接同样需要该 bearer 密钥。

安装

在 SourceWeft 中

  1. 打开 控制台中的 GoodSign,将其添加到工作区。
  2. 连接 Authorization token 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.goodsign%2Fgoodsign/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "goodsign": {
      "type": "http",
      "url": "https://goodsign.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

工具

10

account_status

Account status and credits

Show the GoodSign account name and remaining credits. Each envelope sent costs 1 credit. Check this before bulk sending, or when the user asks "how many credits do I have?".

无需输入参数。

create_document_from_upload

Create a document from an uploaded PDF

Turn a PDF you PUT to a create_upload_url url into a GoodSign document. Call this only after the PUT has finished successfully. GoodSign discovers any text tags in the PDF (see create_upload_url for the full TAG REFERENCE and rules) and creates one field per tag plus one signer per distinct signer key automatically. This does NOT send anything or email anyone — the result behaves like a template: check it with get_document, then send it with send_from_template. The created document can only be sent once — to send the same PDF again, upload it again with create_upload_url and call this tool a second time. If the response includes warnings about unreadable tags, fix the tag text in the source document, re-export the PDF, call create_upload_url again and retry.

输入参数doc_nameupload_id必填

create_upload_url

Get a URL to upload a PDF

Get a short-lived URL to upload a PDF that GoodSign will turn into a document. Use this for a document that is NOT based on an existing GoodSign template — e.g. a Statement of Work, contract or NDA drafted for this specific deal. After the PUT succeeds, call create_document_from_upload with the upload_id this returns. The URL is valid for 15 minutes. If you are GENERATING the PDF yourself, embed text tags where fields should go — GoodSign places a real field at each tag's exact position, and each distinct KEY becomes one signer (reuse the same KEY on every tag that person fills). TAG REFERENCE — this is the complete list; any other tag type is discarded: - [sign|KEY] signature. [in|KEY] initials. Signature size variants: [signxs|KEY] [signsm|KEY] [signmd|KEY] [signlg|KEY] [signxl|KEY]. - [date|KEY] date of signing, filled in automatically. - [input|KEY] required text box. [input?|KEY] optional text box. [input|KEY|Some text] pre-filled, signer can edit. - [name|KEY] and [email|KEY] text boxes pre-filled with that signer's name / email address. - [c|KEY|Label] optional checkbox. [c*|KEY|Label] required checkbox. [c|KEY|x Label] pre-checked. [c1|KEY|Red] [c1|KEY|Blue] = radio group (same digit = one group, signer picks one). RULES — breaking any of these corrupts or silently drops fields: 1. KEY is the signer key: letters and digits ONLY (Client, signer1), identical spelling and case on every tag for that person. Keys differing only in case, spaces or punctuation collide into the wrong signer. Exception: trailing padding spaces before the closing ] (rule 4) are stripped before the key is matched, so [name|Client ] still keys to Client. 2. A tag must be one unbroken run of selectable text on a single line in a normal font — never an image, never wrapped across lines. 3. Do not use square brackets anywhere else in the document — prose like "[insert date]" gets parsed as a tag. Use parentheses instead. 4. The tag's printed size becomes the field's size: its font siz

无需输入参数。

download_document

Get download link for a document PDF

Get an authenticated download URL for a document's PDF (including the audit certificate once complete). The URL requires the same `Authorization: Bearer` API key this MCP connection uses — download it with curl in a shell, do not try to fetch the bytes into the conversation.

输入参数uuid必填

get_document

Get document / template detail

Fetch full detail for one document OR template by uuid. For a template: shows the signer keys ("key" on each signer) and field keys that send_from_template requires — always check this before sending. For a sent document: shows status and per-signer progress (who has signed, who is pending). Timestamps are unix epoch seconds. Field entries show structural info only (key, type, page, which signer); signer-entered field values are never returned.

输入参数uuid必填

list_documents

List documents by status

List this account's documents filtered by status. Use status "sent" (default) to see envelopes still waiting on signatures, "complete" for fully signed ones. Use this to answer questions like "what is still waiting to be signed?" — then get_document on a uuid for per-signer detail.

输入参数status

list_templates

List templates

List the reusable document templates in this GoodSign account. Call this first whenever the user wants to send a document — send_from_template needs a template uuid from here. Each template defines signer keys; call get_document with the template uuid to see exactly which signer keys and field keys it requires before sending.

无需输入参数。

remind_signers

Remind pending signers

Re-send the signing invitation email to signers who have not completed yet. Omit signer_email to remind ALL pending signers of the document; pass signer_email to remind one specific person. Sends real email — do not call repeatedly; once per day per signer is plenty.

输入参数uuid必填signer_email

send_from_template

Send document for e-signature

Send a document for e-signature using a template. THIS EMAILS REAL PEOPLE and spends 1 credit — confirm each signer's name and email with the user before calling, or set draft=true to stage without emailing anyone. Requires one signers[] entry per signer key on the template (get_document on the template uuid lists the keys). For sequential signing set send_in_order=true: signers are emailed one at a time, in the order of the signers array (or explicit send_order values, lower first). Pre-fill text fields with fields[] using the field keys from get_document.

输入参数draftfieldssigners必填cc_emaildoc_nameemail_messageemail_subjectsend_in_ordertemplate_uuid必填

void_document

Void (cancel) a sent document

Cancel a sent document so nobody can sign it anymore. This cannot be undone — to re-send, use send_from_template again. By default signers are notified the document was voided; set notify=false to void silently. Confirm with the user before voiding.

输入参数uuid必填notifymessage

版本历史

1
  1. v1.0.0最新Sep 21, 2026

评分

已满足适用检查项的 83%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分

    请声明包含 README 的 GitHub 仓库,或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证不适用

    托管服务按其提供方的条款使用,因此这里不要求许可证。此检查项不计入百分比。