Send PDFs for e-signature, track signings, and download sealed documents.
Connects to SwiftSign to send documents for electronic signature. Muse can mint sandbox keys, send PDFs to recipients with signing fields, track completion status, void envelopes, and download signed results with audit trails.
Try asking Muse: "Send this contract to my client for signature and let me know when they've signed it."
Source: Found in the official MCP Registry (ca.swiftsign/mcp) · First listed September 24, 2026
Each bar is one check, every 15 minutes. Green means it answered. Last checked 2 h ago.
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://swiftsign.ca/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Response time at the last check: 1413ms. Worked in 100% of checks over 30 days.
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
swiftsign_send_envelopeSend 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 placswiftsign_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. This emails the signers. Does NOT work on envelopes already SENT/COMPLETED/VOIDED.swiftsign_send_from_templateSend 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_check_statusCheck the status of an envelope — who signed, who hasn't, download links. Works in both sandbox (sk_test_ keys) and live.swiftsign_list_envelopesList 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_envelopeCancel/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.swiftsign_download_signed_pdfDownload 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_upgradeInitiate 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_create_embedded_urlMint 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_list_templatesList your saved templates. Scoped to your key's mode — sandbox (sk_test_) keys see test templates, live keys see live.https://swiftsign.ca/mcpNot in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use SwiftSign to help me. It is a free service with an MCP server at https://swiftsign.ca/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
At the last check (September 28, 2026, 08:31 UTC) the endpoint was working, answering in 1413ms. Over the last 7 days it answered 100% of health checks. It is checked every 15 minutes.
It was screened on September 24, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
It exposes 10 tools, including swiftsign_send_envelope, swiftsign_confirm_send, swiftsign_send_from_template, swiftsign_check_status. For example, you could ask Muse: "Send this contract to my client for signature and let me know when they've signed it."
This listing was added from public sources (Found in the official MCP Registry (ca.swiftsign/mcp)). If you build SwiftSign, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/swiftsign"><img src="https://musedirectory.ai/badge/swiftsign.svg" alt="SwiftSign on musedirectory.ai" width="236" height="40"></a>