SignaTrust MCP Server
Official# @signatrust/mcp-server
> Send and verify e-signatures from Claude — zero-custody, with independently verifiable cryptographic evidence for every signature.
[](https://www.npmjs.com/package/@signatrust/mcp-server)
[](https://www.npmjs.com/package/@signatrust/mcp-server)
[](https://registry.modelcontextprotocol.io)
[](https://opensource.org/licenses/MIT)
<!-- Demo slot: record a ~10s GIF of Claude sending an envelope end-to-end (use the
Natural Language Examples below), save it to docs/demo.gif, and add here:
 -->
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.
## Quick Start
### Claude Code
```bash
claude mcp add signatrust -- npx -y @signatrust/mcp-server
```
Then set your API key in the MCP server environment.
### Claude Desktop
Add to your `claude_desktop_config.json`:
```json
{
"mcpServers": {
"signatrust": {
"command": "npx",
"args": ["-y", "@signatrust/mcp-server"],
"env": {
"SIGNATRUST_API_KEY": "sk_live_your_key_here"
}
}
}
}
```
### Cursor
Add to `~/.cursor/mcp.json` (global) or `.cursor/mcp.json` (per-project):
```json
{
"mcpServers": {
"signatrust": {
"command": "npx",
"args": ["-y", "@signatrust/mcp-server"],
"env": {
"SIGNATRUST_API_KEY": "sk_live_your_key_here"
}
}
}
}
```
### VS Code
Add to `.vscode/mcp.json` (note the top-level key is `servers`, not `mcpServers`):
```json
{
"servers": {
"signatrust": {
"command": "npx",
"args": ["-y", "@signatrust/mcp-server"],
"env": {
"SIGNATRUST_API_KEY": "sk_live_your_key_here"
}
}
}
}
```
To keep the key out of the file, use an input prompt instead of `env`:
```json
{
"inputs": [
{ "id": "signatrust-key", "type": "promptString", "description": "SignaTrust API key", "password": true }
],
"servers": {
"signatrust": {
"command": "npx",
"args": ["-y", "@signatrust/mcp-server"],
"env": { "SIGNATRUST_API_KEY": "${input:signatrust-key}" }
}
}
}
```
## Available Tools
| 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).
## API Key Scopes
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 |
## Environment Variables
| 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 |
## Natural Language Examples
Once connected, you can ask your AI assistant things like:
- "List all my pending envelopes"
- "Upload ~/Documents/nda.pdf and send it to alice@example.com with VERIFIED security"
- "Show me available templates, then create a lease agreement from the residential template for John Doe"
- "Check the blockchain verification for envelope env_abc123 and show me the composite hash"
- "Run AI analysis on envelope env_xyz — I want to know if there are any risky clauses before the signer reviews it"
## Development
```bash
# Install dependencies
npm install
# Build
npm run build
# Run tests
npm test
# Run tests with coverage
npm run test:coverage
# Type check
npm run typecheck
# Local smoke test
SIGNATRUST_API_KEY=sk_live_xxx SIGNATRUST_API_URL=http://localhost:3000 node dist/server.js
```
## Architecture
```
src/
server.ts # Entry point — env validation, MCP server setup, stdio transport
handlers.ts # Tool definitions and handler dispatch (testable)
errors.ts # RFC 7807 ProblemDetails -> MCP tool error mapping
vendor/signatrust-sdk/ # Vendored HTTP client + types (zero external runtime deps)
*.test.ts # Co-located test files
```
The HTTP client and API types are vendored under `src/vendor/signatrust-sdk/` so
this package has no external runtime dependencies beyond `@modelcontextprotocol/sdk`.
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.