mcpbeat

Swiftsign MCP Server

ca.swiftsign/mcp
answering

Swiftsign is answering right now. Last checked 9 min ago. 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 41 hours of history · worst hour 0%
41 hours agonow
83.5%
Uptime 24h
76 of 91 checks
10
Tools
read from the server
394 ms
Response time
average over 24h
0
Stars
last commit 28 Jul 2026

Connect this server

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

run in your terminal
claude mcp add mcp --transport http https://swiftsign.ca/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "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
{
  "mcpServers": {
    "mcp": {
      "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

URLTransportStateLatencyChecked
https://swiftsign.ca/mcp streamable-http answering 3127 ms 9 min ago

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 76 of 91 checks got a reply (83.5%), average response time 394 ms. The bar chart above shows every period we have measured.
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 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 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 394 ms on average, which is faster than 34% 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?
Yes — written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.