FreeSign — Claude Code MCP server: what it does, how to install
FreeSign — a remote MCP server for e-signing PDFs: the agent builds a signing envelope from a document hash, then pulls receipts, OpenTimestamps proofs and an audit-chain verdict.
no license 750 installs updated 2026-06-15
claude mcp add --transport http freesign https://sign.run.toolsWhat FreeSign does
FreeSign wraps an e-signature service that runs in the browser. The agent never handles the PDF itself: create_signing_envelope takes a SHA-256 hash and returns a signing link. Whoever opens that link gets an ECDSA P-256 keypair generated on their side, and the public JWK is posted to /api/envelopes/{id}/session-bind. Until that bind happens the envelope accepts no protected calls.
Four more tools read evidence. verify_document_hash matches a local hash against stored receipts. get_receipt returns the envelope record with the final hash and signature, plus per-signer receipts. get_ots_proof hands back a base64 .ots file you check offline with ots-cli against Bitcoin block headers. verify_audit_chain recomputes every event hash, follows the prev_event_hash links and checks seq contiguity.
Output is a PAdES-B-T signature, cited against US ESIGN/UETA and EU eIDAS as an advanced electronic signature. No PDF bytes cross the server in either direction. Signing itself is a browser step, so a headless agent run alone will not finish an envelope.
What it helps with
- create a signing envelope from a PDF hash without uploading the file
- match stored receipts to a local document hash
- check that an envelope's audit log has not been tampered with
- pull an OpenTimestamps proof and verify it offline
- export the final signature and payload into your own archive
Example prompts for the agent
- Create a signing envelope for
contract.pdffrom its SHA-256 and give me the signing link - Verify the audit chain on that envelope and tell me the verdict
- Fetch the receipt and the
.otsproof for the last signed document
How to install FreeSign
Platform CLI: remote server
claude mcp add --transport http freesign https://sign.run.toolsPlatform CLI: remote server
codex mcp add freesign --url https://sign.run.toolsConfig file
{
"mcpServers": {
"freesign": {
"url": "https://sign.run.tools"
}
}
}Config file
{
"servers": {
"freesign": {
"type": "http",
"url": "https://sign.run.tools"
}
}
}Platform CLI: remote server
gemini mcp add -t http freesign https://sign.run.toolsStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about FreeSign
How do I install FreeSign in Claude Code?
Run claude mcp add --transport http freesign https://sign.run.tools. That registers the remote http server under the name freesign.
What does FreeSign do?
It handles the signing side of a PDF workflow: builds an envelope from the document hash, then returns signing receipts, the final signature, an OpenTimestamps proof and a verdict on the audit chain.
Why does an envelope need a session bind?
The keypair is generated in the browser that opens the signing link, and only its public half is sent to /api/envelopes/{id}/session-bind. Without that step protected calls to the envelope fail.