# ca.swiftsign/mcp (remote · swiftsign.ca)

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

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `swiftsign.ca`: 70/100 (this document), [markdown](https://verifymcp.io/servers/ca-swiftsign-mcp/swiftsign.md), [page](https://verifymcp.io/servers/ca-swiftsign-mcp/swiftsign)

## Channel facts

- Endpoint: `https://swiftsign.ca/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (swiftsign_send_envelope).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1020 tokens (~102/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ca-swiftsign-mcp": {
      "type": "remote",
      "url": "https://swiftsign.ca/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ca-swiftsign-mcp --url https://swiftsign.ca/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ca-swiftsign-mcp:
    url: "https://swiftsign.ca/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (10)

### `swiftsign_send_envelope` (~229 tokens)

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.

Input parameters:

- `confirm` (boolean): 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_) alway…
- `documents` (array, required): PDF documents to send
- `fields` (array, required): Signing fields to place on documents
- `message` (string): Optional message to include
- `recipients` (array, required): People who need to sign or receive a copy
- `subject` (string, required): Email subject / document title

### `swiftsign_confirm_send` (~81 tokens)

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.

Input parameters:

- `envelopeId` (string, required): The DRAFT envelope ID to dispatch

### `swiftsign_send_from_template` (~170 tokens)

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.

Input parameters:

- `confirm` (boolean): 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_) alway…
- `message` (string): Optional message to include
- `roleAssignments` (object, required): Map of template role name → signer { name, email }
- `subject` (string): Email subject / document title
- `templateId` (string, required): The template ID to send from

### `swiftsign_check_status` (~53 tokens)

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

Input parameters:

- `envelopeId` (string, required): The envelope ID to check

### `swiftsign_list_envelopes` (~45 tokens)

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` (~60 tokens)

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.

Input parameters:

- `envelopeId` (string, required): The envelope ID to void

### `swiftsign_download_signed_pdf` (~163 tokens)

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.

Input parameters:

- `certificate` (boolean): If true, download the Certificate of Completion (audit trail) instead of the signed document
- `document` (number): Which document to download when an envelope has several (0-based, default 0)
- `envelopeId` (string, required): The envelope ID (must be COMPLETED)
- `outputPath` (string): Where to save the file (default: ./swiftsign-<id>.pdf). Ignored on the hosted endpoint, which returns base64.

### `swiftsign_upgrade` (~81 tokens)

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.

Input parameters:

- `plan` (string): Plan to upgrade to (default PRO)

### `swiftsign_create_embedded_url` (~100 tokens)

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.

Input parameters:

- `envelopeId` (string, required): The envelope ID
- `recipientId` (string, required): The recipient ID within that envelope
- `returnUrl` (string): URL to redirect the signer to after they finish

### `swiftsign_list_templates` (~38 tokens)

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ca-swiftsign-mcp/swiftsign#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 68
- 2026-07-30: 68
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 66
- 2026-07-26: 65

## Links

- Remote endpoint: https://swiftsign.ca/mcp
- Repository: https://github.com/shahdadk/swiftsign
- Website: https://swiftsign.ca/
- Changelog RSS feed: https://verifymcp.io/servers/ca-swiftsign-mcp/swiftsign/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ca-swiftsign-mcp/swiftsign/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ca-swiftsign-mcp/swiftsign