Enables AI assistants to create envelopes, manage templates, upload documents, and verify blockchain-anchored e-signatures via Solana.
Also known as SignaTrustDev/signatrust-mcp, signatrust-mcp, @signatrust/mcp-server
- Stars
- 1
- Tools
- 9
- Downloads, 30 days
- —
- Latest version
- 0.3.2
- Last commit
- Nov 13, 2026
- License
- MIT
What is SignaTrust MCP?
SignaTrust enables AI assistants to create envelopes, manage templates, upload documents, and verify blockchain-anchored e-signatures via Solana. It exposes 9 tools, such as list_envelopes, get_envelope, create_envelope.
Summary generated from the project's README
About SignaTrust MCP server
SignaTrust provides an MCP server that connects AI assistants to a document signing API. This tool allows developers to integrate e-signature workflows directly into environments like Claude Desktop, Cursor, or VS Code. By using natural language, users can manage the entire lifecycle of a document, from uploading local files to verifying signatures through Solana blockchain anchors.
To use this server, you must provide a SIGNATRUST_API_KEY via environment variables or an input prompt. The server supports various security levels, including STANDARD, VERIFIED with OTP, and CERTIFIED with WebAuthn biometrics. It offers specific tools for creating envelopes, managing templates, and downloading documents via time-limited URLs. Users can also perform AI-driven contract analysis or retrieve court-ready evidence bundles containing audit trails and cryptographic hashes.
What you can do with it
- 1Automate document signing workflowsYou can instruct an AI to upload a specific PDF and send it to a recipient using a verified security level.
- 2Verify cryptographic signature integrityAn AI can check the Solana blockchain anchor for a specific envelope to retrieve its composite hash.
- 3Perform automated contract risk reviewsDevelopers can use the AI analysis tool to identify risky clauses within an existing envelope.
- 4Manage document templatesYou can ask the assistant to list available templates and then generate a new agreement based on one.
Written from the project's README. Every use case is checked against a quote from it.
How to install SignaTrust MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall SignaTrust MCP in Claude Code
$ claude mcp add --env 'SIGNATRUST_API_KEY=<YOUR_SIGNATRUST_API_KEY>' signatrust-mcp -- npx -y @signatrust/mcp-serverInstall SignaTrust MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"signatrust-mcp": {
"command": "npx",
"args": [
"-y",
"@signatrust/mcp-server"
],
"env": {
"SIGNATRUST_API_KEY": "<YOUR_SIGNATRUST_API_KEY>"
}
}
}
}Install SignaTrust MCP in VS Code
.vscode/mcp.json
{
"servers": {
"signatrust-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@signatrust/mcp-server"
],
"env": {
"SIGNATRUST_API_KEY": "<YOUR_SIGNATRUST_API_KEY>"
}
}
}
}Install SignaTrust MCP in VS Code CLI
$ code --add-mcp '{"name":"signatrust-mcp","type":"stdio","command":"npx","args":["-y","@signatrust/mcp-server"],"env":{"SIGNATRUST_API_KEY":"<YOUR_SIGNATRUST_API_KEY>"}}'Install SignaTrust MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"signatrust-mcp": {
"command": "npx",
"args": [
"-y",
"@signatrust/mcp-server"
],
"env": {
"SIGNATRUST_API_KEY": "<YOUR_SIGNATRUST_API_KEY>"
}
}
}
}Install SignaTrust MCP in Codex
$ codex mcp add signatrust-mcp --env 'SIGNATRUST_API_KEY=<YOUR_SIGNATRUST_API_KEY>' -- npx -y @signatrust/mcp-serverInstall SignaTrust MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.signatrust-mcp] command = "npx" args = ["-y", "@signatrust/mcp-server"] [mcp_servers.signatrust-mcp.env] SIGNATRUST_API_KEY = "<YOUR_SIGNATRUST_API_KEY>"
Install SignaTrust MCP in Gemini CLI
$ gemini mcp add -s user -e 'SIGNATRUST_API_KEY=<YOUR_SIGNATRUST_API_KEY>' signatrust-mcp npx -- -y @signatrust/mcp-serverInstall SignaTrust MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"signatrust-mcp": {
"command": "npx",
"args": [
"-y",
"@signatrust/mcp-server"
],
"env": {
"SIGNATRUST_API_KEY": "<YOUR_SIGNATRUST_API_KEY>"
}
}
}
}SignaTrust MCP tools 9
Detected from the READMElist_envelopesget_envelopecreate_envelopelist_templatesupload_documentdownload_documentanalyze_documentverify_blockchainget_evidence
Configuration
SIGNATRUST_API_KEYRequiredSecretSignaTrust API key (starts with sk_live_). Create one at Settings -> API keys.
SIGNATRUST_API_URLOverride the API base URL. Defaults to https://app.signatrust.io; set for self-hosted or local development.
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablesignatrustdev/signatrust-mcp is public and reachablegithub.com/signatrustdev/signatrust-mcp ↗Pass
- Package names this repository as its source@signatrust/mcp-server names signatrustdev/signatrust-mcp as sourcenpmjs.com/package/@signatrust/mcp-server ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-13github.com/signatrustdev/signatrust-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @signatrust/mcp-serverPass
- No critical advisory in the package or its dependencies99 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model9 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub@signatrust/mcp-server
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.
Quick Start
Claude Code
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:
{
"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):
{
"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):
{
"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:
{
"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
# 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.
SignaTrust MCP questions
How do I add SignaTrust MCP to Claude Code?
Run claude mcp add --env 'SIGNATRUST_API_KEY=<YOUR_SIGNATRUST_API_KEY>' signatrust-mcp -- npx -y @signatrust/mcp-server in your terminal. Add --scope user to make it available in every project.
How do I add SignaTrust MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does SignaTrust MCP provide?
It exposes 9 tools, including list_envelopes, get_envelope, create_envelope, list_templates, upload_document.
Can I verify the authenticity of a signature on the blockchain?
Yes, you can use the verify_blockchain tool to check the Solana anchor and receive a composite hash, file hash, and explorer URL.
How do I manage API key permissions?
You can create API keys in your SignaTrust dashboard and assign specific scopes like envelopes:read, envelopes:write, or ai:analyze to control tool access.