FreeSign — Free e-signature

com.free-signPublished by free-sign.comOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

FreeSign is a remote e-signature service whose MCP server lets an assistant create signing envelopes from PDF hashes and retrieve verifiable signing evidence.

What you can do
Create signing envelopes from a PDF SHA-256 hash and get a signing URL for the browser to bind a session keypair, without sending PDF bytes to the server (create_signing_envelope). Look up FreeSign receipts that match a local document hash (verify_document_hash). Read an envelope record with final document hash, signature, per-signer receipts and OpenTimestamps anchor metadata (get_receipt). Fetch the base64 .ots proof for an anchor so it can be checked offline with ots-cli against Bitcoin block headers (get_ots_proof). Retrieve an envelope's append-only audit-event hash chain with a server-computed integrity verdict (verify_audit_chain).
When to use it
Use it when you want an assistant to start a PDF signing flow from a hash you already hold, or to pull back receipts, OpenTimestamps proofs and audit-chain verdicts to confirm a document was signed and not altered. It suits evidence and verification work rather than editing or storing documents.
Requirements
A remote MCP endpoint at free-sign.com over streamable HTTP; no authentication, environment variables or headers are declared. The signing step needs a browser to open the returned signing URL and generate a session keypair. Verifying .ots proofs offline requires the official ots-cli and Bitcoin block headers.
Before you install
The server handles signing evidence, not documents: it asks for a PDF SHA-256 hash and explicitly should not receive PDF bytes. A newly created envelope is not yet session-bound until a browser opens the signing URL and binds a public key, so treat the returned URL as sensitive. Receipts, proofs and audit chains are evidence only; confirm them independently before relying on them.

Installation

In SourceWeft

  1. Open FreeSign — Free e-signature in the dashboard and add it to a workspace.
  2. 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/com.free-sign%2Fsigning/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.

{
  "mcpServers": {
    "freesign-free-e-signature": {
      "type": "http",
      "url": "https://free-sign.com/mcp"
    }
  }
}

Tools

5

create_signing_envelope

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.

Parametersdocument_sha256required

verify_document_hash

Verify document hash

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

Parametersdocument_sha256required

get_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.

Parametersenvelope_idrequired

get_ots_proof

Get OpenTimestamps 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).

Parametersanchor_idrequiredenvelope_idrequired

verify_audit_chain

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`.

Parametersenvelope_idrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • 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.