mcp
connectsswiftsign.ca
E-signatures for agents: mint a sandbox key, send PDFs, track status, download the sealed result.
https://swiftsign.ca/mcpWebsiteOAuthMCP 2025-11-25v0.5.1last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 245 msHow to authenticate
Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://swiftsign.ca |
| Dynamic client registration | ✓Advertised (RFC 7591) |
| Client ID Metadata Document | ✕Not advertised |
| PKCE | ✓S256 |
| Grant types | authorization_code, refresh_token |
| Scopes | envelopes:read, envelopes:write |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Handshake succeeds; 10 tools listable |
What the probe found
A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.
The server exposes a public surface before authorization: swiftsign_send_envelope, swiftsign_confirm_send, swiftsign_send_from_template, swiftsign_check_status, swiftsign_list_envelopes, swiftsign_void_envelope, swiftsign_download_signed_pdf, swiftsign_upgrade, swiftsign_create_embedded_url, swiftsign_list_templates.
Tools
Contract history
Get alerted when this contract changes
Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.
Prefer a feed reader? This page's contract changes are also an Atom feed.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/ca-swiftsign-mcp)Own this server?
Sign in to claim this listing by proving control of the endpoint.