swiftsign-mcp (shahdadk/swiftsign-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 11 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
74/100

swiftsign-mcp

E-signature for AI agents. An MCP server that lets Claude Code, Cursor, Zed, or any MCP-aware agent prepare, send, track, and seal legally binding documents without a human ever touching a mouse.

→ shahdadk/swiftsign-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

shahdadk

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Tool annotations don’t match behaviour
1 read-only tool performs write/delete/exec — swiftsign_download_signed_pdf (line 441: writeFile(target, buffer))
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: DOCUSIGN_INTEGRATION_KEY, SWIFTSIGN_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes11 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

swiftsign_signup

Create a sandbox SwiftSign account and get a test API key (no browser needed). Returns an sk_test_ key for sandbox sends — upgrade with swiftsign_upgrade for live. Set the returned key as SWIFTSIGN_API_KEY to use the other tools.

swiftsign_send_envelope

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 (per…

swiftsign_confirm_send

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.

swiftsign_send_from_template

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.

swiftsign_check_status

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

swiftsign_list_envelopes

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

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.

swiftsign_download_signed_pdf

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.

swiftsign_upgrade

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.

swiftsign_create_embedded_url

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.

swiftsign_list_templates

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

// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretDOCUSIGN_INTEGRATION_KEY
configDOCUSIGN_REDIRECT_PORT
🔐 secretSWIFTSIGN_API_KEY"env": { "": "sk_test_..." }
configSWIFTSIGN_API_URLno Override the API base for self-hosted SwiftSign instances.
configSWIFTSIGN_URL
// quality suggestions

All four hints declared on every tool

11/11 tools missing one or more hints — swiftsign_signup (missing: readOnlyHint, destructiveHint, idempotentHint); swiftsign_send_envelope (missing: readOnlyHint, idempotentHint); swiftsign_confirm_send (missing: readOnlyHint, idempotentHint), +8 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool annotations match behaviour

1 read-only tool performs write/delete/exec — swiftsign_download_signed_pdf (line 441: writeFile(target, buffer))

Either remove the readOnlyHint:true annotation, or remove the write/delete call from the tool handler.

Tool inputs are validated

9/11 tool handlers declare input schemas (82%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool test coverage

Only 0/11 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/shahdadk/swiftsign-mcp?variant=verified)](https://m8ven.ai/mcp/shahdadk/swiftsign-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 173627ef05fbb4af1dc2d50994f8de87516d7770
code hash: 4c6fa19f4b03b0f52ceabc8a7cc4b237e1a4476feec7c000ee3a00a4908e3621
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client