Skip to content
SwiftSign logo

SwiftSign MCP server

Which servers in the official MCP registry are SwiftSign's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-12

← Back to SwiftSign

Whose server it is
  • Registry nameca.swiftsign/mcpverified in the MCP registry

The registry name sits under swiftsign.ca. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-12
  • Stateanswerschecked 2026-10-12
  • Tools10
  • Server calls itselfswiftsign
  • Server version0.5.1
  • Protocol version2025-06-18

On 2026-10-12 the server answered initialize and tools/list without a sign-in. First answer in 103 ms.

Tools it offers10 tools · read 2026-10-12
  • 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…

  • 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…

  • 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_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_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_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.

  • 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_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…

  • 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_list_templates

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

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

OpenAPI spec

8 paths, read 2026-10-12. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.