APISign
io.apisign由 apisign.io 發布官方發布者v1.0.0更新於 Oct 24, 2026
Send documents for legally binding e-signature and manage the reusable templates behind them.
概覽
託管的 APISign MCP 伺服器，讓助理依範本起草合約、送出進行具法律效力的電子簽署，並追蹤簽署人。
- 可以做什麼
- 列出、讀取、建立、更新、上傳（DOCX/DOC）與封存可重複使用的範本
- 從範本或原始內容建立合約，填入 Handlebars 風格變數並指定簽署人
- 編輯草稿合約的內容與簽署人
- 送出合約供簽署，取消草稿或已送出的合約
- 列出並讀取合約及其簽署人狀態
- 適用情境
- 適合讓助理在對話中直接依組織範本準備並送出協議（例如保密協議、合約、待簽文件），或查看哪些文件已由誰簽署。
- 執行需求
- 遠端 Streamable HTTP 端點 apisign.io/mcp，無需安裝或自行架設。需要 APISign 帳號及在 Account → API Keys 建立的 API 金鑰，透過 x-api-key 標頭傳送；金鑰僅顯示一次。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 APISign，將其新增到工作區。
- 連接 x-api-key 憑證。它們會被私密儲存，絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.apisign%2Fapisign/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"apisign": {
"type": "http",
"url": "https://apisign.io/mcp",
"headers": {
"x-api-key": "<YOUR_API_KEY>"
}
}
}
}README
APISign MCP Server
Send documents out for legally binding e-signature, and manage the templates they come from, directly from an AI agent.
APISign runs a hosted Model Context Protocol
server at https://apisign.io/mcp. There is nothing to install and nothing
to self-host — point your client at the URL, give it an API key, and your agent
can draft a contract from a template, fill its variables, send it to signers,
and watch the signatures come in.
This repository holds the connection metadata and client configuration. The service itself lives at apisign.io.
Connect
1. Get an API key. Sign in at apisign.io, then go to Account → API Keys and create one. Copy it — it is shown once.
Pick the permission deliberately:
A Read Only key does not merely refuse the write tools — they are left out of
the tools/list response entirely, so the agent never learns they exist. If
your agent only needs to look things up, use one.
2. Add the server. The quickest route, which works for Claude, Cursor, ChatGPT and most other clients:
Or configure it by hand:
Transport is Streamable HTTP. Authentication is the x-api-key header.
Tools
Twelve tools, in two families. Everything is scoped to the organization the API key belongs to.
Templates
Contracts
Templates are Markdown with Handlebars-style variables — {{client_name}},
{{effective_date}} — that contract_create fills in. Signature placeholders
work the same way: a one-signer document needs a {{signature}}, and a
multi-signer document gives each party their own, assigned through
signer_fields.
A worked example
Draft an NDA for Acme Corp from our standard mutual NDA template, effective the first of next month, and send it to [email protected] and to me.
The agent calls template_list to find the template, template_get to read
its variables, contract_create to fill them and attach both signers, then
contract_send. You get back a contract ID you can follow with
contract_get.
Discovery metadata
The server also serves its own card, without authentication, so directories can describe it without an API key:
https://apisign.io/.well-known/mcp.jsonhttps://apisign.io/.well-known/mcp/server-card.json
Docs and support
- MCP server documentation
- API reference
- Pricing — contracts are billed per document sent
Issues with the MCP integration are welcome here. Questions about your account belong at apisign.io.
License
MIT
來源：README.md，提交 c414e9d
工具
0版本歷史
1- v1.0.0最新Sep 16, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分