ENDPOINT 1
https://swiftsign.ca/mcp
MCP server metadata
- Name
- swiftsign
- Version
- 0.5.1
Known tools 10
swiftsign_confirm_sendDispatch 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.
Inferred read-onlyswiftsign_send_from_templateSend an envelope from a saved template by assigning signers to roles.
Potential side effectsswiftsign_check_statusCheck the status of an envelope — who signed, who hasn't, download links.
Inferred read-onlyswiftsign_download_signed_pdfDownload the completed, sealed PDF (or its Certificate of Completion) for an envelope.
Inferred read-onlyswiftsign_create_embedded_urlMint a short-lived embedded signing URL for a recipient (30-minute expiry).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.swiftsign]
url = "https://swiftsign.ca/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"swiftsign": {
"type": "http",
"url": "https://swiftsign.ca/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: swiftsign
Remote MCP URL: https://swiftsign.ca/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"swiftsign": {
"url": "https://swiftsign.ca/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"swiftsign": {
"type": "http",
"url": "https://swiftsign.ca/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "swiftsign",
"transport": "streamable-http",
"url": "https://swiftsign.ca/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.