SignaTrust MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIGNATRUST_API_KEY | Yes | API key starting with sk_live_ | |
| SIGNATRUST_API_URL | No | API base URL | https://app.signatrust.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_envelopesA | List signature envelopes with optional status filter and pagination. Returns envelope summaries including signers, documents, and blockchain anchoring status. |
| get_envelopeA | Get full details of a specific envelope including all signers, documents, status, security level, and blockchain anchoring info. |
| create_envelopeA | Create and send a new envelope for signing. Requires a name, at least one signer, and at least one document (pass document IDs from upload_document, or pass a templateId to create from a template). Signers are notified via their chosen delivery method. Use securityLevel to match the legal weight required: STANDARD for routine/internal approvals; VERIFIED (adds SMS/email OTP) for employment, vendor, or healthcare consent; CERTIFIED (adds WebAuthn biometric + device binding) for real estate, high-value, or regulatory signings. |
| list_templatesA | List available document templates. Templates provide pre-configured documents with defined signer roles and form-field placement. |
| upload_documentA | Upload a local file to SignaTrust and return a document ID suitable for passing to create_envelope. Reads the file from disk, requests a pre-signed S3 upload URL, streams the bytes, and returns metadata. Supported: PDF (recommended), DOCX, images. Max size is enforced by your plan's limits. |
| analyze_documentA | Run AI contract analysis (Google Gemini) on a completed envelope's document. Returns a structured report covering risk assessment, flagged clauses, and overall sentiment (SAFE / CAUTION / RISKY). Plan-gated: free accounts receive a 403; upgrade to Pro Lite or above to use this. Surface the 403 message to the user rather than retrying. |
| void_envelopeA | Void (cancel) an in-progress envelope. The envelope's status becomes VOIDED, all signers receive a cancellation notice, and the void is recorded in the audit trail. Use this when the sender needs to cancel a contract that has already been sent to signers. Fails if the envelope is already COMPLETED or already VOIDED — use get_envelope first to check status. After voiding, the envelope can be deleted via the dashboard or DELETE /api/v1/envelopes/{id}. |
| verify_blockchainA | Verify a completed envelope's Solana anchor. Returns the composite hash (SHA-256 binding the final PDF, signer metadata, and the hash-chained audit trail), the file hash, the Solana transaction ID, and an explorer URL. Because the composite hash is anchored to Solana, any modification to the document, signer records, or audit trail breaks the hash chain and fails verification. This is the proof that makes the envelope independently verifiable without SignaTrust. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct action and resource: envelope CRUD (list, get, create, void), document upload, template listing, AI analysis, and blockchain verification. There is no overlap or ambiguity in tool purposes, making misselection unlikely.
All tool names follow a consistent verb_noun pattern using lowercase with underscores, such as list_envelopes, create_envelope, upload_document, and verify_blockchain. The naming convention is uniform and predictable across the entire set.
Eight tools cover the core envelope lifecycle and supporting features without bloat. The count is well-scoped for a document signing server, with each tool serving a clear and necessary function.
The tool set covers the primary workflow: upload documents, create/list/get envelopes, void in-progress envelopes, analyze completed ones, and verify blockchain anchors. Minor gaps like an in-MCP update or delete tool are absent, but those are secondary and can be handled via dashboard or API as noted.