MCP server for terminal commands, file operations, and process management
Nothing to run from here
Swiftsign Ca MCP is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
10
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
E-signatures for agents: mint a sandbox key, send PDFs, track status, download the sealed result.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http swiftsign-ca-mcp https://swiftsign.ca/mcp
# 2 — ask your agent for something these tools do
# swiftsign_send_envelope, swiftsign_confirm_send, swiftsign_send_from_template and 7 more
Swiftsign Ca MCP costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SCAll 1 server
swiftsign.ca1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http swiftsign-ca-mcp https://swiftsign.ca/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | string | yes | Email subject / document title |
| message | string | no | Optional message to include |
| documents | array | yes | PDF documents to send |
| recipients | array | yes | People who need to sign or receive a copy |
| fields | array | yes | Signing fields to place on documents |
| confirm | boolean | no | Set true to dispatch immediately on a LIVE key (sk_live_/sk_oat_). Without it, live envelopes are created as DRAFT and returned for human review before anything is emailed. Test keys (sk_test_) always |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| envelopeId | string | yes | The DRAFT envelope ID to dispatch |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| templateId | string | yes | The template ID to send from |
| roleAssignments | object | yes | Map of template role name → signer { name, email } |
| subject | string | no | Email subject / document title |
| message | string | no | Optional message to include |
| confirm | boolean | no | Set true to dispatch immediately on a LIVE key (sk_live_/sk_oat_). Without it, live envelopes are created as DRAFT and returned for human review before anything is emailed. Test keys (sk_test_) always |
Check the status of an envelope — who signed, who hasn't, download links. Works in both sandbox (sk_test_ keys) and live.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| envelopeId | string | yes | The envelope ID to check |
List envelopes (sent documents) with their status. Scoped to your key's mode — sandbox (sk_test_) keys see test envelopes, live keys see live.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| envelopeId | string | yes | The envelope ID to void |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| envelopeId | string | yes | The envelope ID (must be COMPLETED) |
| outputPath | string | no | Where to save the file (default: ./swiftsign-<id>.pdf). Ignored on the hosted endpoint, which returns base64. |
| document | number | no | Which document to download when an envelope has several (0-based, default 0) |
| certificate | boolean | no | If true, download the Certificate of Completion (audit trail) instead of the signed document |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan | string | no | Plan to upgrade to (default PRO) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| envelopeId | string | yes | The envelope ID |
| recipientId | string | yes | The recipient ID within that envelope |
| returnUrl | string | no | URL to redirect the signer to after they finish |
List your saved templates. Scoped to your key's mode — sandbox (sk_test_) keys see test templates, live keys see live.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Swiftsign Ca MCP or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.5.1.
0.5.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Swiftsign Ca MCP can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.