io.zsign/zsign (/mcp/open)
MCP server · zsign.io · found in a public list · checked since 2026-11-11
Live, handshake completed · latest check
Sends documents for e-signature, tracks signers and downloads sealed signed PDFs.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/7). What this means
Placed in E-signatures: Send documents for electronic signature, track signers and retrieve signed copies.
https://zsign.io/mcp/open MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person. See 2 endpoints from zsign.io.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-11-11 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-11-11 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-11-11 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
add_document_to_draftbuy_creditscheck_balancecorrect_recipient_emailcreate_accountcreate_templatedelete_draftdownload_certificatedownload_signed_documentget_accountget_audit_trailget_envelope_statusget_pricingget_referral_linkget_signing_linksget_usagelist_commentslist_envelopeslist_templatesprepare_documentremind_envelopereply_commentresolve_commentrevise_envelopesend_draftsend_envelopesend_from_templateupdate_draftvoid_envelope
- Tools
- 29
- This list since
- 2026-11-11
- First listed to us
- 2026-11-11
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- promptsresourcestools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
Calls it declares
create_account email name source → resultget_pricing → resultget_account → resultcheck_balance → resultget_usage start_date* end_date* → resultget_referral_link → resultbuy_credits pack* → resultsend_envelope recipients document_base64 document_url filename name metadata send_invite send_completion_email sequential auto_send draft fields documents prefill → resultprepare_document document_base64 document_url signers prepare_id approve → resultupdate_draft document_id* fields* → resultadd_document_to_draft document_id* filename document_base64 document_url template_id name role_mapping → resultsend_draft document_id* recipients metadata send_invite send_completion_email sequential prefill → result
From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Links
What it states about itself, from its registry entry or package:
- Website: zsign.io
Pages we read:
- llms.txt: zsign.io/llms.txt, read
Its own links, from its llms.txt, under its own headings and names. These are its words, not ours:
Docs (17)
- Full API reference (plain text)
- OpenAPI spec (JSON)
- API reference (HTML)
- CLI guide (HTML)
- MCP setup (HTML)
- Embed SDKs (HTML)
- Connect your agent (HTML)
- Quickstart (HTML)
- Pricing (HTML)
- zSign vs DocuSign MCP
- zSign vs BoldSign for AI agents: MCP, API pricing and signup
- zSign vs Portant Sign PDF for AI agents
- zSign vs Signbee for AI agents
- zSign vs GoodSign for AI agents
- zSign vs DocuSign: e-signatures for developers and AI agents
- DocuSign alternative for AI agents
- Agent-sent envelopes
Pricing
Field syntax
Referrals
Blog
- Product notes
- Build vs buy e-signatures: should you build your own?
- zSign on Zapier: send, track, and file signed envelopes from your Zaps
- Signers can now ask for changes instead of just saying no
- Five Zap templates that file, post and send your zsign envelopes for you
Convex component
Legal
Links only (links/3): we follow none of them when showing this page, and a link is not a recommendation. How links are chosen.
Listing
In the capability tree: Documents and media / Documents and PDFs / E-signatures (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/7, tree/3) on 2026-11-11. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, handshake completed HTTP 200 | 1028 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_068eb16b5abfcd89