The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the SignaTrust listing page.
Send and verify e-signatures from Claude — zero-custody, with independently verifiable cryptographic evidence for every signature.
Model Context Protocol (MCP) server for the SignaTrust document signing API. Enables AI assistants like Claude to create envelopes, manage templates, check signing status, and verify blockchain anchors via natural language.
Then set your API key in the MCP server environment.
Add to your claude_desktop_config.json:
Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):
Add to .vscode/mcp.json (note the top-level key is servers, not mcpServers):
To keep the key out of the file, use an input prompt instead of env:
| Tool | Description | Required Scope |
|---|---|---|
list_envelopes | List envelopes with status filter and pagination | envelopes:read |
get_envelope | Get full envelope details (signers, docs, blockchain) | envelopes:read |
create_envelope | Create and send envelope for signing. Accepts documentIds (after upload_document) or templateId (backend copies the template). Supports three-tier securityLevel. | envelopes:write |
list_templates | List available document templates | templates:read |
upload_document | Read a local file and upload it to SignaTrust, returning a document ID for create_envelope | documents:write |
download_document | Get a time-limited pre-signed URL to download a document (e.g. the executed PDF) | documents:read |
analyze_document | Run AI contract analysis on an envelope (Gemini-powered risk/sentiment review, plan-gated) | ai:analyze |
verify_blockchain | Verify Solana anchor and return composite hash + file hash + explorer URL | envelopes:read |
get_evidence | Get the full court-ready evidence bundle (envelope, signers, audit trail, blockchain verification) | envelopes:read |
Three-tier security. create_envelope accepts securityLevel: STANDARD (bearer token only), VERIFIED (adds SMS/email OTP — recommended for employment, vendor, or healthcare consent), or CERTIFIED (adds WebAuthn biometric + device binding — recommended for real estate, high-value, or regulatory signings).
Create an API key at Settings > API Keys in your SignaTrust dashboard. Assign scopes based on what tools you need:
| Scope | Tools Enabled |
|---|---|
envelopes:read | list_envelopes, get_envelope, verify_blockchain, get_evidence |
envelopes:write | create_envelope |
templates:read | list_templates |
documents:write | upload_document |
documents:read | download_document |
ai:analyze | analyze_document |
| Variable | Required | Default | Description |
|---|---|---|---|
SIGNATRUST_API_KEY | Yes | - | API key starting with sk_live_ |
SIGNATRUST_API_URL | No | https://app.signatrust.io | API base URL |
Once connected, you can ask your AI assistant things like:
The HTTP client and API types are vendored under src/vendor/signatrust-sdk/ so
this package has no external runtime dependencies beyond @modelcontextprotocol/sdk.