Docuflex e-signature
Server Details
E-signature envelopes on Docuflex: create, send, track, verify; US e-sign law lookup.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 13 tools
Most tools map to a distinct resource+action, and the descriptions carefully distinguish e.g. verify_envelope (keyless hash/chain check) from get_envelope (authenticated status). Minor overlap remains: create_envelope with status 'sent' duplicates send_envelope, and docuflex_overview vs docuflex_api_reference are two similar help/meta tools.
The core envelope surface follows a clean verb_noun pattern (create/get/list/send/void/verify_envelope, get_audit_trail, get_signing_url). Three outliers break the pattern with prefixes or non-verb forms: whoami, docuflex_overview/docuflex_api_reference, esign_law_lookup.
13 tools is squarely in the sweet spot for an e-signature API: a compact envelope lifecycle plus a few meta/help utilities. Nothing appears redundant enough to remove.
The envelope lifecycle is well covered end to end — create, draft-to-sent, list, get, void, audit trail, embedded signing URL, and public verification. Gaps exist around templates, document/PDF download, resend/reminders, and draft/recipient updates, which are only reachable by consulting the API reference rather than through dedicated tools.
Available Tools
13 toolscreate_envelopeCreate (and optionally send) an envelopeAInspect
Create a Docuflex envelope. documents: inline base64 PDFs or staged uploadIds. recipients: name, email, routingOrder (1 = first), optional type (signer default, cc, certified_delivery, in_person_signer...). tabs: type (signature, initial, date_signed, text, checkbox...), page (1-based), x/y/width/height as fractions of the page from the top-left, documentIndex and recipientIndex into this request's arrays. status 'sent' sends now; omit for a draft.
Inputs: subject (required), documents (required), recipients (required), tabs, +6 more.
docuflex_api_referenceAPI reference for a resourceAInspect
List the operations (method, path, summary) for one resource group from the OpenAPI spec: envelopes, signing, verify, templates, bulk-send, connect, uploads, api-keys, oauth, accounts, library, admin.
Inputs: resource (required).
docuflex_overviewWhat Docuflex isBInspect
Product summary, how to get an API key, base URLs, auth, limits and links.
Inputs: no named parameters.
esign_law_lookupE-signature law for a US stateAInspect
High-level ESIGN / UETA / ESRA summary for a US state, the document types the federal act excludes, and what Docuflex records. Not legal advice.
Inputs: state (required).
get_audit_trailAudit trailBInspect
Hash-chained audit events for an envelope, oldest first.
Inputs: envelope_id (required), api_key, account_id.
get_envelopeGet an envelopeDInspect
Envelope status, recipients, documents.
Inputs: envelope_id (required), api_key, account_id.
get_signing_urlEmbedded signing URLBInspect
Short-lived signing URL for a current-tier recipient (embedded signing). Provide the recipient's email or clientUserId as used on the envelope and a returnUrl.
Inputs: envelope_id (required), email, api_key, userName, +3 more.
list_envelopesList envelopesCInspect
Most recent envelopes for the account.
Inputs: limit, status, api_key, account_id.
request_accessContact the Docuflex teamAInspect
Send a message to the Docuflex team (commercial terms, higher limits, questions). Only when the user explicitly asks and provides their own email. Limited to 5 per hour per IP.
Inputs: name (required), email (required), message (required), company.
send_envelopeSend a draft envelopeCInspect
Transition a draft to sent.
Inputs: envelope_id (required), api_key, account_id.
verify_envelopeVerify envelope integrity (public)AInspect
No key needed. Returns status, sealed-document hashes, certificate hash and audit-chain verification for an envelope id. Never returns document content.
Inputs: envelope_id (required).
void_envelopeVoid an envelopeCInspect
Void a sent envelope with a reason.
Inputs: reason (required), envelope_id (required), api_key, account_id.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
E-signatures: send, track, remind, void and download envelopes; templates and reports.
Send documents for legally binding e-signature and manage the reusable templates behind them.
Send contracts for e-signature, track signing, get signed PDFs and audit trails, verify any PDF.
Send agreements for e-signing, use templates, track signatures, send reminders, get signed documents
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

kysigned-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables management of e-signature envelopes — create, check status, list, send reminders, and void — through natural language.15 npm37Apache 2.0- FlicenseNot gradedqualityBmaintenanceEnables users to manage e-signature workflows through a hosted MCP connection, including sending envelopes from templates, tracking signer status, sending reminders, voiding envelopes, retrieving audit trails, downloading documents, organizing folders, sharing access, and viewing reports.-
- AlicenseNot gradedqualityCmaintenanceBlockchain-anchored e-signatures. Create, send, negotiate, and verify legally binding agreements — every signature anchored to XRPL + Bitcoin with public verification. Agents can pay autonomously.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.