Documentation

Use SignaTrust in Claude

Connect your SignaTrust account to Claude, then ask Claude to prepare agreements, send them once you confirm, follow their progress, and fetch the proof of what was signed.

What it does

With the SignaTrust connector, you can ask Claude to:

  • fill in an agreement from one of your templates;
  • stage a draft envelope with the document, the signers and the signature fields;
  • send the envelope when you tell it to, as a separate step from preparing it;
  • tell you who has signed and who has not;
  • retrieve the evidence for a completed envelope and check its blockchain anchor.
Claude cannot sign on anyone's behalf, including yours. Every signer signs personally, from a link SignaTrust sends them.

Connect

  1. In Claude, open the connector settings and add SignaTrust from the connector directory. If you prefer, add a custom connector with this URL:https://www.signatrust.io/api/mcp/mcp
  2. Click Connect.
  3. Sign in to SignaTrust, review the permissions Claude is asking for, and approve them.

You do not need an API key. The connector signs in as you and can do only what your SignaTrust account can do. It works on every plan, including Free, which includes 10 envelopes a month.

How sending works

  1. Draft first. Claude creates the envelope as a draft. Nobody is notified while it is a draft.
  2. Review. Claude shows you the recipients and fields, with a link to review the draft in SignaTrust.
  3. Confirm. Claude asks you to confirm before it sends. Sending also needs its own permission, separate from preparing drafts, which you approve when you connect.
  4. Send. SignaTrust then notifies the signers.

Signing can be sequential: each signer has a place in the signing order, and the next signer is asked to sign after the one before them finishes.

Security levels

  • Standard: the signer opens their signing link and signs.
  • Verified: Verified means the signer authenticated and signed within a 15-minute freshness window, with a one-time code.

Government-ID verification is a separate option you can require on any envelope, at any plan.

Evidence and retention

  • Audit trail. Every event in an envelope's life is recorded in an audit trail in which each entry is linked to the one before it by a hash, so changing an entry, or removing one from the middle, is detectable.
  • Trusted timestamp. Every audit event is submitted for an RFC 3161 timestamp from an independent timestamp authority after it is written.
  • Blockchain anchor. When signing completes, the SHA-256 hash of the final signed PDF is submitted to the Solana blockchain to be recorded.
  • Public verifier. Anyone can upload a signed PDF or an evidence bundle at /verify to check it, without an account.

Retention

SignaTrust does not keep signed documents long term. When an envelope is completed, SignaTrust schedules its copy for deletion 7 days later. After that point the copy is deleted once every party has confirmed receiving their own copy, or 90 days after the scheduled date if someone never confirms. There is one exception: if you connected your own storage and the copy sent there has not been confirmed, SignaTrust keeps its copy until it is, rather than destroy your only one.

The hashes, audit trail and blockchain proof are kept after the document is deleted. Download your copy, or connect your own storage in SignaTrust settings so signed documents are saved there.

The tools

These are the actions the connector gives Claude today. Claude picks the right one from your request; you do not need to name them.

list_envelopes
Lists your envelopes and their status.
get_envelope
Shows one envelope: its signers, fields and where signing stands.
list_organizations
Lists the organizations (workspaces) you belong to.
verify_blockchain
Checks the blockchain anchor of a completed envelope.
get_evidence
Retrieves an envelope's evidence: signers, the audit trail and the anchor details.
create_envelope
Creates a draft envelope from a document or template. Nobody is notified.
update_envelope
Changes a draft envelope's title or the message signers see.
require_identity_verification
Turns government-ID verification on or off for a draft envelope's signers.
get_verification_status
Shows each signer's government-ID verification status.
add_signer
Adds a signer to a draft envelope.
remove_signer
Removes a signer from a draft envelope.
update_signer
Changes a signer's details or signing order on a draft envelope.
send_envelope
Sends an envelope to its signers. The only tool that notifies them to sign.
void_envelope
Cancels an envelope in progress. Signers already invited get a cancellation notice.
list_templates
Lists your templates.
upload_document
Uploads a small document into your account.
upload_document_init
Starts a larger upload that is sent in parts.
upload_document_chunk
Sends one part of a larger upload.
upload_document_commit
Finishes a larger upload and creates the document.
list_documents
Lists the documents in your account.
download_document
Gets a short-lived download link for a document, including a signed PDF.
analyze_document
Runs an AI review of an envelope's document.
detect_signers
Suggests who needs to sign a document.
detect_fields
Suggests where signature and other fields go on a document.
storage_status
Reports whether signed documents are reaching your own connected storage.
storage_revalidate
Tests your connected storage by writing a temporary file, reading it back and deleting it.
support_diagnose
Explains what happened to an envelope and what to do next. Changes nothing.

Data handling

The connector reads and writes only what belongs to your SignaTrust account: your envelopes, documents and templates, plus those shared with you through an organization you belong to. It acts with the permissions you approved when you connected, and you can disconnect it in Claude at any time.

Read the privacy policy for how SignaTrust handles personal data.

Troubleshooting

Claude shows no SignaTrust tools, or behaves as it did before an update.

Claude keeps the tool list it received when you connected. In Claude's connector settings, disconnect SignaTrust and connect it again to fetch the current list.

An error says the connection is not authorized for an action.

The error contains: this connection is not authorized for this action

The message names the permission that is missing. Reconnect SignaTrust and approve that permission on the sign-in screen.

Creating an envelope from a template fails.

The error contains: One or more template variables are invalid

The error lists each value that is missing or wrong. Give Claude those values and ask it to try again.

A large file will not upload from the chat.

The error contains: content hash mismatch

Large files can be damaged in transit between Claude and SignaTrust; when that happens nothing is stored. Upload the file in your SignaTrust dashboard instead, then ask Claude to use it by name.

Claude cannot create another envelope this month.

The error contains: Plan limit exceeded:

You have reached your plan's monthly envelope limit. See pricing to send more.

Support

Email support@signatrust.io. Include the envelope name or ID if your question is about a specific envelope.