Swiftsign MCP Server

by swiftsign Your server? Claim it

not responding

Swiftsign is listed as active in the registry but did not answer our last check. It exposes 10 tools. Last commit 28 Jul 2026.

E-signatures for agents: mint a sandbox key, send PDFs, track status, download the sealed result.

Uptime history 91 days of history · worst day 1%

91 days agonow

10.9%

Uptime 24h

10 of 92 checks

Tools

read from the server

371 ms

Response time

average over 24h

Stars

last commit 28 Jul 2026

What the code does

We read the source, 1 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command mcp/src/docusign/oauth.ts:44

    const child = spawn(cmd, args, { stdio: "ignore", detached: true });

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://swiftsign.ca/mcp

Settings → Connectors → Add custom connector, then paste this address

https://swiftsign.ca/mcp

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://swiftsign.ca/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://swiftsign.ca/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://swiftsign.ca/mcp"
    }
  }
}

Available tools 10

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

swiftsign

swiftsign_check_status

Check the status of an envelope — who signed, who hasn't, download links. Works in both sandbox (sk_test_ keys) and live.

swiftsign_confirm_send

Dispatch a DRAFT envelope — use after a human has reviewed an envelope that swiftsign_send_envelope or swiftsign_send_from_template returned as draft_pending_confirmation. This emails the signers. Does NOT work on envelopes already SENT/COMPLETED/VOIDED.

swiftsign_create_embedded_url

Mint a short-lived embedded signing URL for a recipient (30-minute expiry). Returns a url to embed plus its expiresAt. The envelope must already be SENT. Works in both sandbox (sk_test_ keys) and live.

swiftsign_download_signed_pdf

Download the completed, sealed PDF (or its Certificate of Completion) for an envelope. Only works once status is COMPLETED — run swiftsign_check_status first. Does NOT work on DRAFT or SENT envelopes; nothing has been signed yet on those.

swiftsign_list_envelopes

List envelopes (sent documents) with their status. Scoped to your key's mode — sandbox (sk_test_) keys see test envelopes, live keys see live.

swiftsign_list_templates

List your saved templates. Scoped to your key's mode — sandbox (sk_test_) keys see test templates, live keys see live.

swiftsign_send_envelope

Send a document for e-signature. Accepts PDF as base64, recipients, and field placement. Sandbox keys (sk_test_) send immediately (watermarked test mail). LIVE keys create a DRAFT and return it for human review unless confirm: true — nothing is emailed until confirmed. Field placement: page+x+y (percent, top-left origin) OR an anchor string, not both. After everyone signs, retrieve the sealed PDF with swiftsign_download_signed_pdf.

swiftsign_send_from_template

Send an envelope from a saved template by assigning signers to roles. Sandbox keys (sk_test_) send immediately; LIVE keys create a DRAFT for human review unless confirm: true — nothing is emailed until confirmed.

swiftsign_upgrade

Initiate the upgrade to PRO ($15/mo flat). Returns a Stripe checkout_url that a human opens once to add a card — agents cannot complete the payment themselves. Moves the account from sandbox (sk_test_) to live sends. Returns status 'updated' if already on the plan.

swiftsign_void_envelope

Cancel/void an envelope that hasn't been completed yet. Signers can no longer sign a voided envelope. Works in both sandbox (sk_test_ keys) and live.

Endpoints

URL	Transport	State	Latency	Checked
https://swiftsign.ca/mcp	streamable-http	answering	103 ms	1 min ago

Alternatives to Swiftsign

same job, measured the same way

Signvoy

by signvoy

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

answering

Zsign

by zsign

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

answering

GoodSign

by goodsign

Send documents for e-signature, track and remind signers, and download signed PDFs.

10 tools answering

Signforge

by kumarprobeops

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

57 installs/wk local only

PenlyDoc

by orestklymko

Send documents for e-signature, track who signed and save sealed PDFs with PenlyDoc.

65 installs/wk local only

Sigil e-signatures

by signwithsigil

Send a PDF or DOCX for e-signature as a pact, track its signers and fetch the signed copy.

answering

Inkfree

by inkfree

E-signatures: send, track, remind, void and download envelopes; templates and reports.

answering

Assinafy

by assinafy

Send documents for legally valid e-signature in Brazil, track signers and download signed files.

29 tools answering

Swiftsign — questions

Answers built from our own checks of this server.

What can Swiftsign do?

It exposes 10 tools, read directly from the server on our last check. Among them: swiftsign_check_status, swiftsign_confirm_send, swiftsign_create_embedded_url, swiftsign_download_signed_pdf, swiftsign_list_envelopes, swiftsign_list_templates and 4 more. 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 Swiftsign working right now?

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

The registry lists Swiftsign as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Swiftsign?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Swiftsign need an API key?

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

How fast is Swiftsign?

It answers our handshake in 371 ms on average, which is faster than 35% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Swiftsign open source?

We cannot say either way: written in JavaScript and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.