Zsign

io.zsignPublished by zsign.ioOfficial publisherv1.0.3Updated Oct 30, 2026

Send documents for e-signature from AI assistants, track signers, and download sealed, signed PDFs.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server that lets an AI assistant send documents for e-signature, track signers, and download sealed, signed PDFs.

What you can do
  • Send documents out for e-signature from the assistant.
  • Track the status of signers on sent documents.
  • Download sealed, signed PDFs once signing is complete.
When to use it
Useful when you want an assistant to start signature requests, follow who has signed, and retrieve completed signed PDFs without leaving the chat.
Requirements
A remote MCP endpoint at zsign.io over streamable HTTP. OAuth 2.1 is required and discovered automatically via the protected-resource and authorization-server metadata; an Authorization header is used for authentication. No local runtime or packages needed.
Before you install
The server handles signature workflows and signed documents, so actions may send documents to third parties and create legally binding signature requests. Access is granted through OAuth credentials in the Authorization header; review the scopes granted before connecting.

Installation

In SourceWeft

  1. Open Zsign in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.zsign%2Fzsign/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "zsign": {
      "type": "http",
      "url": "https://zsign.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.3LatestOct 30, 2026
  2. v1.0.2Sep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.