Server data from the Official MCP Registry
E-signatures for agents: mint a sandbox key, send PDFs, track status, download the sealed result.
E-signatures for agents: mint a sandbox key, send PDFs, track status, download the sealed result.
Remote endpoints: streamable-http: https://swiftsign.ca/mcp
Remote MCP endpoint verified (232ms response). 3 trust signals: valid MCP protocol, requires auth, registry import. No security issues detected.
Endpoint verified · Requires authentication · 2 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Remote servers are capped at 8.0 because source code is not available for review. The score reflects endpoint verification only.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"ca-swiftsign-mcp": {
"url": "https://swiftsign.ca/mcp"
}
}
}From the project's GitHub README.
AI-native e-signatures. Send, track, and seal contracts from your terminal — Claude Code, Cursor, Zed, or any MCP-aware agent. ESIGN / UETA / PIPEDA compliant sealed PDFs with audit trail.
@prisma/adapter-pggit clone https://github.com/shahdadk/swiftsign.git
cd swiftsign
./scripts/bootstrap.sh
The bootstrap script installs Vercel CLI, logs you in (browser auth), links the
checkout to the SwiftSign Vercel project, pulls production env vars into
.env.local, and runs npm install. After it finishes, run npm run dev and
you're operational.
# Install (legacy-peer-deps is pinned in .npmrc, required for React 19 / Next 16)
npm install
# Generate the Prisma client (writes to src/generated/prisma/, gitignored)
npx prisma generate
# Apply schema migrations to your dev DB
npx prisma migrate deploy
# Run the dev server
npm run dev
Copy .env.local.example to .env.local and fill in the values, or run
./scripts/bootstrap.sh to pull them from Vercel.
npm run dev — start dev server on port 3000npm run build — production build (Turbopack)npm run start — run the built servernpm run lint — ESLintnpx prisma generate — regenerate the Prisma clientnpx prisma migrate dev --name <slug> — create a new migrationnpx tsx prisma/seed.ts — seed a local user (manual)Provision services:
DATABASE_URL.EMAIL_FROM domain) and an API key.https://swiftsign.ca/dashboard/billing and enable cancel + payment-method update.https://swiftsign.ca/api/stripe/webhook, listening for checkout.session.completed, customer.subscription.created/updated/deleted, invoice.paid, invoice.payment_failed. Copy the signing secret.CRON_SECRET (16+ random chars). Vercel cron will pass this as Authorization: Bearer <CRON_SECRET>.Set environment variables on the Vercel project (Production + Preview). See .env.local.example for the full list.
Deploy: connect the repo, push to main. Vercel runs npx prisma generate and next build from package.json.
Run schema migrations once via npx prisma migrate deploy — locally, or as part of a build hook. Subsequent deploys re-apply automatically if you wire it into the build command.
Verify: visit /api/healthcheck. Returns { status: "ok" } with DB and R2 checks green.
/api/v1/envelopes — public REST API; bearer-token auth via Authorization: Bearer <apiKey>. Quota enforced (5/mo on Free, unlimited on Pro/Team)./sign/[token] + /api/sign/[token] — recipient signing flow. No account; signingToken is the only credential./dashboard/* — sender UI. Cookie session via swiftsign_session. Pages: envelopes list, envelope detail, billing, settings (API key + sessions), webhooks./api/stripe/webhook — Stripe → DB sync (subscription + plan)./api/cron/webhook-retry — runs every 5 minutes via vercel.json to retry failed outbound webhook deliveries.Independent npm package at mcp/. Build + publish:
cd mcp
npm install
npm run build
npm publish
Users install with:
claude mcp add swiftsign -- npx -y swiftsign-mcp
Configure with SWIFTSIGN_API_KEY (and optionally SWIFTSIGN_API_URL for self-hosted instances).
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.