ca.swiftsign/mcp

Name: ca.swiftsign/mcp
Rating: 60 (1 reviews)
Author: ca.swiftsign

MCPcommunity

v0.5.2ca.swiftsignUnknownUpdated 23d agoGitHub

E-signatures for agents: mint a sandbox key, send PDFs, track status, download the sealed result.

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. Next.js 16.2 (App Router, Turbopack, React 19) Prisma 7 (preview) + Neon PostgreSQL via Cloudflare R2 (S3-compatible) for PDFs + page images Resend for transactional email Stripe for billing (Free / Pro $15 /…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

23d agoLast update

Package

Authorca.swiftsign

LicenseUnknown

Version0.5.2

Sourcemcp-registry

GitHubshahdadk/swiftsign

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—CVE scan · not run+0/30

→ Not yet scanned — package must be on npm

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

DependenciesNot audited

Tool surface—

Security scan✓ CleanvHEAD · 19d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp