MCP.Market

Swiftsign MCP server

online · 100% uptime
by swiftsign.ca·ca.swiftsign/mcp·v0.5.2
No reviews yet

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

B76/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B76/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Swiftsign yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Swiftsign tools (10, 5 write)

write = sends, deletes, buys or posts
  • swiftsign_check_statusFree

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

  • swiftsign_confirm_sendwrite actionFree

    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_urlwrite actionFree

    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_pdfFree

    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_envelopesFree

    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_templatesFree

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

  • swiftsign_send_envelopewrite actionFree

    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_templatewrite actionFree

    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_upgradeFree

    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_envelopewrite actionFree

    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.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

1 high
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 367ms20/20
  • Tool poisoning10 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 5 write-action tools with no auth3/15
  • Maintenancelast push 61 days ago12/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace7/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 76/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Swiftsign compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
76/100
higher than 48% of 48,255 servers
Tools
10
the typical server has 7
Tools that change things
50%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
957 ms
faster than 12% of 30,031 servers

What its tools let an agent do: 5 read · 5 change

Install Swiftsign in Claude Code, Cursor or VS Code

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

What the publisher says

From the Swiftsign repository's README, as published. We do not edit it. Read it on GitHub

SwiftSign

AI-native e-signatures. Send, track, and seal contracts from your terminal: Claude Code, Cursor, Zed, or any MCP-aware agent. No drag handles. No per-seat fees.

Why

DocuSign assumes a person with a cursor, dragging signature boxes onto a PDF and paying per seat. SwiftSign assumes code. It is API-first and agent-native: a script or an AI agent can mint a key, send a legally binding contract, track it to completion, and pull back the sealed PDF and Certificate of Completion, end to end, without a browser.

What you get

  • REST API at /api/v1/envelopes, bearer-token auth, quota-enforced.
  • MCP server (swiftsign-mcp) with 11 tools so agents can sign documents directly, including agent self-signup and a confirm gate on live sends.
  • SDKs for JavaScript and Python.
  • Signer flow with no account required: a secure signing link, e-sign consent, and signature capture by draw, type, or upload.
  • Sealed PDFs with a SHA-256 hash, full audit trail, and a Certificate of Completion.
  • DocuSign importer so you can bring existing templates across.
  • Compliant under ESIGN, UETA (United States), PIPEDA, and the Ontario Electronic Commerce Act (Canada).

Use it from an agent

claude mcp add swiftsign -- npx -y swiftsign-mcp
"Send the MSA at ./contracts/Acme_MSA.pdf to john@acme.com for signing,
 with a signature field at the bottom."

The agent mints a sandbox key if it has none, places the fields, emails the signer a link, and reports back when it is sealed. See swiftsign-mcp for the full tool list.

Stack

  • Next.js 16.2 (App Router, Turbopack, React 19)
  • Prisma 7 + Neon PostgreSQL via @prisma/adapter-pg
  • Cloudflare R2 (S3-compatible) for PDFs and page images
  • Resend for transactional email
  • Stripe for billing (Free / Pro $15 / Team $79, monthly)
  • Upstash Redis for rate limiting, Sentry for error tracking

Architecture

  • /api/v1/envelopes: public REST API; bearer-token auth via Authorization: Bearer . Quota enforced (5/mo on Free, unlimited on Pro/Team).
  • /sign/[token] and /api/sign/[token]: recipient signing flow. No account; the signingToken is the only credential.
  • /dashboard/: sender UI. Cookie session via swiftsignsession. Envelopes, billing, settings (API key, sessions), webhooks.
  • /api/stripe/webhook: Stripe to DB sync (subscription and plan).
  • /api/cron/webhook-retry: runs every 5 minutes via vercel.json to retry failed outbound webhook deliveries.

Development

git clone https://github.com/shahdadk/swiftsign.git
cd swiftsign
./scripts/bootstrap.sh

The bootstrap script installs the Vercel CLI, logs you in, links the checkout to the SwiftSign Vercel project, pulls production env vars into .env.local, and runs npm install. Then npm run dev and you are operational.

Manual setup:

npm install                  # legacy-peer-deps is pinned in .npmrc (React 19 / Next 16)
npx prisma generate          # writes the Prisma client to src/generated/prisma/
npx prisma migrate deploy    # apply schema migrations to your dev DB
npm run dev                  # dev server on port 3000

Common commands:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Swiftsign: common questions

Is Swiftsign MCP server safe?
Mostly: it is graded B (76/100). Read the Swiftsign safety report
How do I install Swiftsign?
It runs remotely at swiftsign.ca. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Swiftsign need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Swiftsign maintained?
The last commit was 99 days ago (2026-07-28). The latest release is v0.5.2.
Is Swiftsign up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Swiftsign compare with other MCP servers?
safety score 76/100 (higher than 48% of 48,255 servers); tools 10 (the typical server has 7); tools that change things 50% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.