mcpbeat Sign in

Zsign MCP Server

answering

Zsign is answering right now. Last checked 15 min ago.

E-signature API for AI agents: send contracts, sign PDF documents, track and download signed files.

Uptime history 48 days of history · worst day 99%
48 days agonow
98.9%
Uptime 24h
90 of 91 checks
Tools
hidden behind auth
797 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Zsign missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add zsign --transport http https://zsign.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "zsign": {
      "url": "https://zsign.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.zsign]
url = "https://zsign.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "zsign": {
      "url": "https://zsign.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "zsign": {
      "url": "https://zsign.io/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://zsign.io/mcp streamable-http sign-in 732 ms 15 min ago

Alternatives to Zsign

same job, measured the same way
Signforge
by kumarprobeops

Send documents for e-signature from AI agents. Upload, sign, and download PDFs.

39 installs/wk local only
Addsign MCP
by rmindgh

Send documents for e-signature, track status, remind signers, and download signed PDFs via AddSign

32 installs/wk local only
Signvoy
by signvoy

Send documents for e-signature, track signing status, and download signed PDFs. No API key required.

answering
FreeSign — Free e-signature
by free-sign

Free e-signature for humans and AI agents — zero-document PDF signing from hashes only.

5 tools answering
Heu MCP
by lucavisconti211-debug

HEU Legal e-signature MCP: manage HEU documents and PDFs, prompt signers, download PDFs.

358 installs/wk local only
Heu MCP
by lucav21

HEU Legal e-signature MCP: manage HEU documents and PDFs, prompt signers, download PDFs.

local only
Pdfgate
by pdfgate

MCP server for the PDFGate API. Generate PDFs, manage documents and handle e-signatures.

218 installs/wk answering
blue·auth Document Signing
by ricdanyalgil

Send AI-created PDFs for signature, track signers, and return verifiable document evidence.

answering

Zsign — questions

Answers built from our own checks of this server.

Why is there no tool list for Zsign?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 98.9% of checks in the last 24 hours got a reply.
Is Zsign working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 797 ms. The bar chart above shows every period we have measured.
How do I connect Zsign?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Zsign?
No API key is involved. Zsign answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Zsign?
It answers our handshake in 797 ms on average, which is faster than 14% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.