Signvoy
Server Details
Send documents for e-signature, track signing status, and download signed PDFs. No API key required.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 16 tools
Every tool targets a distinct resource+action pair (contact, document, template, workspace, audit trail, signed PDF, signing link). The only near-overlap — signvoy_remind_document vs signvoy_remind_recipient — is explicitly split as all-pending vs one-recipient, and status vs audit trail are clearly differentiated by purpose. An agent can select correctly from names plus descriptions.
All 16 tools use a uniform signvoy_ prefix followed by a verb_noun pattern (list_documents, get_template, send_document, void_document). No camelCase or style mixing; the create/get/list/update/send/void/remind verb set is used consistently.
At 16 tools it sits just above the ideal 3-15 band, but each tool maps to a real e-signature workflow step (contacts, templates, drafts, sending, reminders, audit, completion). Nothing looks redundant enough to cut outright, though a couple could theoretically be folded together.
The core lifecycle is well covered: create/update/send/void document, status, audit trail, signed PDF, signing links, reminders, plus contacts, templates, and workspaces. Minor gaps exist — no update/delete for contacts, no document detail fetch beyond status, and no template authoring — but none block the main signing workflows.
Available Tools
16 toolssignvoy_create_contactAInspect
Add someone to the workspace address book so they can be found by name later. Rarely needed on its own: sending a document files its recipients automatically, so call this only when the user asks to save a contact ahead of time or wants to record details (company, job title, phone) that a send would not capture. Fails with a conflict if the address is already in the book — call signvoy_list_contacts first if you are unsure.
Inputs: email (required), name, notes, phone, +3 more.
signvoy_create_documentAInspect
Create a new signing document (in 'draft' state) from a published template. PREREQUISITE: call signvoy_get_template first to retrieve the recipient role keys — each entry in 'recipients' must match a roleKey from the template. Call signvoy_send_document afterwards to email recipients. Keep create and send separate so a human can review the draft before real emails go to counterparties.
Inputs: recipients (required), template_id (required), name, message, +3 more.
signvoy_create_signing_linkAIdempotentInspect
Generate a short-lived embedded signing URL for a specific recipient of a sent document. The recipient can sign without logging in. Only available for sent documents with pending recipients. Default TTL is 1 h.
Inputs: document_id (required), document_recipient_id (required), workspace_id, expires_in_seconds.
signvoy_get_audit_trailARead-onlyInspect
Return the append-only audit trail for a document. Each entry records who did what and when (send, view, sign, decline, void, expire, remind). Useful for verifying chain of custody.
Inputs: document_id (required), workspace_id.
signvoy_get_document_statusARead-onlyInspect
Get the current status of a document and per-recipient signing state. Returns status, the signing deadline (expiresAt), when the automatic final pre-deadline reminder is due (finalReminderAt), and a row per recipient with their current signing state (pending / signed / declined). Each recipient includes lastRemindedAt (when they were last reminded, for rate limiting) and hasActiveSigningLink (whether they can currently sign - respects sequential workflow). Use recipients[].id as document_recipient_id when calling signvoy_create_signing_link or signvoy_remind_recipient.
Inputs: document_id (required), workspace_id.
signvoy_get_signed_pdf_urlARead-onlyInspect
Return a short-lived (10 min) presigned URL to download the certified signed PDF for a completed document. Only available when status is 'completed'. Do not cache — request a fresh URL each time.
Inputs: document_id (required), workspace_id.
signvoy_get_templateARead-onlyInspect
Get full details of a single template including its recipient role keys. Role keys (e.g. 'signer', 'witness', 'approver') are required when calling signvoy_create_document — each recipient must be matched to a roleKey from this template. Always call this before create_document.
Inputs: template_id (required), workspace_id.
signvoy_list_contactsARead-onlyInspect
Search the workspace address book. This is how you turn a name the user said into the email address a document needs — call it before signvoy_create_document whenever the user names a recipient rather than spelling out their address, instead of guessing an email. The book is shared by everyone in the workspace and fills up automatically from the recipients of every document sent. Archived contacts are excluded. Omit 'q' to browse the whole book.
Inputs: q, limit, offset, workspace_id.
signvoy_list_documentsARead-onlyInspect
List documents in the workspace, newest first. Returns a summary per document (id, name, status, recipient counts). Members only see their own documents; admins and owners see all.
Inputs: q, limit, offset, status, +1 more.
signvoy_list_templatesARead-onlyInspect
List templates in the workspace. Returns a summary per template (id, name, hasPublishedVersion). Only templates with hasPublishedVersion=true can be used to create documents. Call signvoy_get_template on the chosen template to retrieve recipient role keys before creating a document. Defaults to active (non-archived) templates.
Inputs: limit, status, workspace_id.
signvoy_list_workspacesARead-onlyInspect
List all workspaces the authenticated user belongs to. Returns id, name, slug, role, and personal flag. Use the returned id as workspace_id in other tools. Call this first when starting any workflow, unless you already know the user has a single workspace — every other tool refuses to guess between several and fails with an ambiguous-workspace error. When more than one comes back, ask the user which they mean rather than picking for them.
Inputs: no named parameters.
signvoy_remind_documentAInspect
Send an immediate reminder email to all pending recipients of a sent document. Only available for documents in 'sent' or 'in_progress' status. Use sparingly — do not spam recipients.
Inputs: document_id (required), workspace_id.
signvoy_remind_recipientAInspect
Send an immediate reminder email to a specific pending recipient. Use this when you want to remind only one person instead of all pending recipients. Only available for documents in 'sent' or 'in_progress' status. Rate limited to 1 reminder per recipient per 24 hours. Check recipients[].lastRemindedAt from signvoy_get_document_status to avoid rate limit errors. Only remind recipients where hasActiveSigningLink is true (respects sequential signing order). Use sparingly — do not spam recipients.
Inputs: document_id (required), document_recipient_id (required), workspace_id.
signvoy_send_documentAIdempotentInspect
Send a draft document to its recipients. Emails each recipient with a personalised signing link. Real emails will be sent to real counterparties — confirm with the user before calling. Idempotent: calling on an already-sent document is a no-op.
Inputs: document_id (required), workspace_id.
signvoy_update_documentAIdempotentInspect
Update a draft document before sending. Only allowed while the document is in 'draft' status. Use this to fix recipient names, email addresses, recipient types, the document name, the signing message, the email subject, routing mode, or reminder cadence. Replaces the entire recipients list when provided — include all recipients, not just the ones being changed.
Inputs: document_id (required), name, message, recipients, +4 more.
signvoy_void_documentADestructiveInspect
Void a document, revoking all outstanding signing links. This is irreversible — the document cannot be re-sent. Only appropriate when the document must be withdrawn before completion. ALWAYS confirm with the user before calling this tool.
Inputs: document_id (required), workspace_id.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Send documents for e-signature from templates, track status, remind signers, get signed PDFs.
Send PDFs for e-signature by email and SMS code. Check signing status. No document storage.
Send documents for e-signature, see who has signed, send reminders and get signed PDFs.
Get PDFs signed: prepare, send and track e-signature requests, then fetch the signed copy.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and developers to create, send, and follow up on contracts for e-signature, manage signers and templates, retrieve signed PDFs and audit trails, and verify PDF signatures. It keeps signing and declining in the hands of each signer through personal links.1MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to send documents for e-signature from templates or local files, track signers and history, send reminders, create signing links, and download or verify sealed PDFs.1351 npmMIT
- FlicenseNot gradedqualityDmaintenanceE-signature for AI agents. One unauthenticated call returns a sandbox API key (no account, no browser), then the agent can send documents for signature, check status, and download the sealed PDF plus Certificate of Completion.-
- AlicenseAqualityBmaintenanceLets AI agents send PDFs for e-signature (recognized under ESIGN and UETA), place fields, track signers, and pull an evidence package. Every signing event goes into a public hash chain, sealed daily, so anyone can verify a document without trusting the sender or the service. 100 documents a month free, no card.11MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.