FreeSign — Free e-signature MCP Server

by free-sign Your server? Claim it

answering

FreeSign — Free e-signature is answering right now. Last checked 7 min ago. It exposes 5 tools.

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

Uptime history 48 days of history

48 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

120 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check FreeSign — Free e-signature every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add signing --transport http https://free-sign.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "signing": {
      "url": "https://free-sign.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.signing]
url = "https://free-sign.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "signing": {
      "url": "https://free-sign.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "signing": {
      "url": "https://free-sign.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify

verify_audit_chain

Return an envelope's append-only audit-event hash chain together with a server-computed integrity verdict: every event_hash is recomputed from its canonical material, and the prev_event_hash linkage and per-envelope seq contiguity are checked. Evidence only, never PDF bytes. The raw events are included verbatim so the caller can independently re-derive the verdict instead of trusting `chain.valid`.

verify_document_hash

Find FreeSign receipts matching a local document SHA-256 hash.

ots

get_ots_proof

Return the .ots proof (base64) for a given OpenTimestamps anchor on an envelope. Use the official `ots-cli` to verify offline against Bitcoin block headers. Each seal has two anchors: `kind: "byterange"` commits to the signed document, `kind: "signed_attrs"` commits to SHA-256 of the CMS SignedAttributes (which carry the post-quantum key commitment).

receipt

get_receipt

Return the envelope record (including final_pdf_sha256, final_signature_base64url, final_payload_json), per-signer signing receipts, and OpenTimestamps anchor metadata. Evidence only, never PDF bytes.

signing

create_signing_envelope

Create a FreeSign envelope from a PDF SHA-256 hash. Do not send PDF bytes. The created envelope is NOT yet session-bound — the browser that opens the returned signing_url generates an ECDSA P-256 keypair locally and POSTs the public JWK to /api/envelopes/{id}/session-bind before any protected request will succeed. AI agents calling this tool just hand the signing_url to a human, who continues in a browser.

Endpoints

URL	Transport	State	Latency	Checked
https://free-sign.com/mcp	streamable-http	answering	129 ms	7 min ago

Alternatives to FreeSign — Free e-signature

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

Zsign

by zsign

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

answering

ZapSign

by mcp-dir

ZapSign electronic document signing via the official API: create documents for signature (from PDF,

35 tools answering

InkSeal

by inkseal

Send documents for signature: upload, place fields, draft, and send once a human agrees.

answering

Pdfgate

by pdfgate

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

218 installs/wk answering

Groupdocs Signature MCP

by groupdocs-signature

MCP server for GroupDocs.Signature — sign, search and verify document signatures via AI agents.

local only

LayerOne (DocX + Sign)

by golayerone

MCP server for LayerOne DocX (documents & Factur-X) and Sign (e-signature) APIs.

33 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 — questions

Answers built from our own checks of this server.

What can FreeSign — Free e-signature do?

It exposes 5 tools, read directly from the server on our last check. Among them: create_signing_envelope, get_ots_proof, get_receipt, verify_audit_chain, verify_document_hash. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is FreeSign — Free e-signature working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 120 ms. The bar chart above shows every period we have measured.

How do I connect FreeSign — Free e-signature?

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.

Does FreeSign — Free e-signature need an API key?

No. FreeSign — Free e-signature completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is FreeSign — Free e-signature?

It answers our handshake in 120 ms on average, which is faster than 81% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.