{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"github-dottedsign-official--dottedsign-mcp","slug":"dottedsign-official--dottedsign-mcp","name":"dottedsign-mcp","type":"mcp","url":"https://www.dottedsign.com/","page_url":"https://unfragile.ai/dottedsign-official--dottedsign-mcp","categories":["mcp-servers","documentation"],"tags":["ai-automation","ai-automation-claude","ai-automation-gpt","digital-signature","dottedsign","electronic-signature","esignature","llm-tools","mcp","model-context-protocol","workflow-automation","workflow-automation-ai","workflow-automation-github","workflow-automation-mac","workflow-automation-windows"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"github-dottedsign-official--dottedsign-mcp__cap_0","uri":"capability://tool.use.integration.natural.language.signing.task.management.via.mcp.protocol","name":"natural language signing task management via mcp protocol","description":"Exposes DottedSign signing operations through the Model Context Protocol (MCP), allowing Claude and ChatGPT to interpret natural language requests and translate them into structured API calls to create, retrieve, and manage signing tasks. Uses MCP's tool-calling schema to define signing operations as callable functions with parameter validation, enabling LLMs to understand signing workflows without direct API knowledge.","intents":["I want Claude to create a signing request when I describe it in plain English","I need an AI assistant to check the status of pending signatures without me writing code","I want to automate repetitive signing workflows by describing them to ChatGPT"],"best_for":["Teams using Claude or ChatGPT who want to integrate DottedSign without custom backend code","Non-technical users who want AI-driven document signing automation","Developers building LLM-powered document workflows"],"limitations":["Requires active DottedSign account with API credentials — no offline operation","MCP protocol latency adds ~200-500ms per request due to context window serialization","Limited to operations exposed by DottedSign API — cannot customize signing logic beyond platform capabilities","No built-in request queuing or retry logic — relies on LLM's error handling"],"requires":["DottedSign API key and account credentials","Claude or ChatGPT with MCP client support (Claude Desktop 0.3.0+, or compatible ChatGPT plugin framework)","Network connectivity to DottedSign API endpoints"],"input_types":["natural language instructions","structured signing parameters (recipient email, document ID, etc.)"],"output_types":["signing task metadata (task ID, status, recipient info)","natural language summaries of signing status"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-dottedsign-official--dottedsign-mcp__cap_1","uri":"capability://automation.workflow.template.based.document.signing.request.generation","name":"template-based document signing request generation","description":"Enables creation of signing requests from DottedSign templates via natural language, mapping user intent (e.g., 'send this contract to john@example.com') to template IDs and recipient configurations. The MCP server translates template references into API calls that populate signing workflows with pre-configured document layouts, field positions, and signing logic.","intents":["I want to send a standard NDA template to a new vendor without manually configuring fields","Create a signing request using our company's contract template and auto-fill recipient details","Generate multiple signing requests from the same template for different recipients"],"best_for":["Organizations with standardized document templates (NDAs, contracts, agreements)","Teams automating high-volume signing workflows with consistent document structures","Non-technical staff who need to initiate signing without understanding document configuration"],"limitations":["Requires pre-existing templates in DottedSign account — cannot create new templates via MCP","Template field mapping is static — dynamic field injection requires manual template updates in DottedSign UI","No template versioning support — changes to templates affect all future requests using that template ID"],"requires":["DottedSign account with at least one pre-configured template","Template IDs and field names documented or discoverable via DottedSign API","LLM context window large enough to store template metadata (typically <5KB per template)"],"input_types":["natural language template references ('our standard NDA', 'vendor agreement')","recipient email addresses and metadata","optional field overrides as key-value pairs"],"output_types":["signing request ID","recipient invitation link","template application confirmation with field mappings"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-dottedsign-official--dottedsign-mcp__cap_2","uri":"capability://search.retrieval.signing.task.status.polling.and.retrieval","name":"signing task status polling and retrieval","description":"Provides real-time querying of signing request status (pending, signed, rejected, expired) by task ID or recipient email, using DottedSign's status API endpoints. The MCP server wraps status queries in a natural language interface, allowing users to ask 'has John signed yet?' and receive interpreted status updates without parsing raw API responses.","intents":["Check if a specific recipient has signed a document","Get a summary of all pending signatures for a given task","Monitor signing progress and identify bottlenecks in the workflow"],"best_for":["Teams managing multiple concurrent signing workflows who need visibility without logging into DottedSign UI","Developers building LLM-driven document automation who need status checks in agent loops","Non-technical users who want AI-powered status summaries instead of dashboard navigation"],"limitations":["Status polling is eventual-consistent — may lag 30-60 seconds behind actual DottedSign state","No webhook support for real-time notifications — requires active polling or periodic checks","Cannot filter by date range or custom metadata — only supports task ID or email-based queries","Rate-limited by DottedSign API (typically 100 requests/minute) — high-volume polling may hit limits"],"requires":["Valid signing task ID or recipient email address","DottedSign API credentials with read permissions","Network connectivity to DottedSign API"],"input_types":["signing task ID (UUID)","recipient email address","optional date range or status filter"],"output_types":["structured status object (status, timestamp, recipient details)","natural language status summary ('John signed on Tuesday at 2pm')"],"categories":["search-retrieval","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-dottedsign-official--dottedsign-mcp__cap_3","uri":"capability://automation.workflow.batch.signing.request.creation.with.recipient.list.expansion","name":"batch signing request creation with recipient list expansion","description":"Enables creation of multiple signing requests from a single natural language instruction by expanding recipient lists (e.g., 'send to all vendors in this spreadsheet'). The MCP server iterates over recipients and creates individual signing tasks, optionally applying template-based configurations to each. Handles recipient deduplication and validation before submission to DottedSign API.","intents":["Send a contract to 50 vendors at once without creating 50 individual requests manually","Create signing requests for all team members from a CSV list","Batch-generate signing tasks with different templates based on recipient type"],"best_for":["Organizations with high-volume signing needs (10+ recipients per batch)","Teams managing multi-party agreements or consent workflows","Developers automating bulk document distribution"],"limitations":["Recipient list must be provided as structured data (CSV, JSON, or extracted from context) — no unstructured text parsing","No built-in deduplication across multiple batches — requires manual tracking of previously-sent recipients","DottedSign API rate limits apply per request — batch creation may be throttled if >100 recipients","No transaction semantics — partial failures leave some recipients without signing requests while others succeed"],"requires":["Recipient list in structured format (email addresses minimum, optional: name, company, custom fields)","DottedSign API credentials with write permissions","Template ID if using template-based batch creation"],"input_types":["recipient list (array of email addresses or objects with email + metadata)","template ID or document configuration","optional custom field mappings per recipient"],"output_types":["array of created signing task IDs","summary report (success count, failure count, error details)","batch operation ID for tracking"],"categories":["automation-workflow","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-dottedsign-official--dottedsign-mcp__cap_4","uri":"capability://planning.reasoning.signing.workflow.state.machine.management","name":"signing workflow state machine management","description":"Tracks and enforces signing workflow state transitions (e.g., draft → sent → signed → completed) by maintaining state context and validating operations against current workflow state. The MCP server prevents invalid transitions (e.g., cannot mark as signed if not yet sent) and provides state-aware suggestions for next actions based on current task status.","intents":["Ensure signing requests follow a valid workflow sequence without manual state tracking","Get AI-suggested next steps based on current signing task status","Prevent accidental operations like resending to already-signed recipients"],"best_for":["Teams with complex multi-step signing workflows (e.g., sequential signers, approval chains)","Developers building LLM agents that need to enforce business logic constraints","Organizations with compliance requirements for audit trails and state validation"],"limitations":["State machine is defined statically in MCP server code — cannot customize workflows without code changes","No persistence of state history — state is inferred from DottedSign API responses, not stored locally","Cannot handle concurrent state changes from multiple LLM instances — no distributed locking","Limited to DottedSign's native state model — cannot implement custom intermediate states"],"requires":["MCP server with state machine logic implemented","Real-time access to DottedSign API for current task state","LLM context window to store state transition rules (typically <2KB)"],"input_types":["current signing task ID","proposed action (send, resend, cancel, mark complete)","optional state override (for admin operations)"],"output_types":["validation result (allowed/denied with reason)","suggested next actions","state transition confirmation"],"categories":["planning-reasoning","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-dottedsign-official--dottedsign-mcp__cap_5","uri":"capability://automation.workflow.recipient.notification.and.reminder.management","name":"recipient notification and reminder management","description":"Enables sending reminder notifications to signing recipients and tracking notification history via DottedSign's notification API. The MCP server abstracts notification scheduling (immediate, delayed, recurring) and allows the LLM to determine optimal reminder timing based on signing status and deadline context.","intents":["Send a reminder to John about the pending signature without manually logging into DottedSign","Automatically remind all unsigned recipients 24 hours before deadline","Track which recipients have been reminded to avoid duplicate notifications"],"best_for":["Teams managing time-sensitive signing workflows with tight deadlines","Developers building LLM agents that need to proactively manage signing progress","Organizations with high signing abandonment rates who need reminder strategies"],"limitations":["Notification scheduling is limited to DottedSign's supported intervals — cannot implement custom schedules","No guarantee of delivery — notifications may be filtered as spam or blocked by email providers","Reminder history is stored in DottedSign, not locally — requires API calls to retrieve full history","Cannot customize notification content — uses DottedSign's default templates"],"requires":["DottedSign API credentials with notification permissions","Valid signing task ID and recipient email","Optional: deadline timestamp for context-aware reminder scheduling"],"input_types":["signing task ID","recipient email address","reminder type (immediate, scheduled, recurring)","optional: delay duration or cron-like schedule"],"output_types":["notification send confirmation","notification history (timestamp, recipient, status)","next scheduled reminder time"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-dottedsign-official--dottedsign-mcp__cap_6","uri":"capability://data.processing.analysis.document.metadata.extraction.and.signing.field.mapping","name":"document metadata extraction and signing field mapping","description":"Extracts metadata from uploaded documents (field names, positions, required signatures) and maps them to signing configurations in DottedSign. The MCP server parses document structure and provides the LLM with a semantic understanding of where signatures are needed, enabling intelligent field assignment and validation.","intents":["Automatically detect signature fields in a PDF and configure them for signing","Map document fields to recipient roles (e.g., 'Authorized Signatory' field → CEO)","Validate that all required signature fields are configured before sending"],"best_for":["Organizations with diverse document types that need flexible field mapping","Developers building document automation pipelines with variable document structures","Teams that want to reduce manual field configuration in DottedSign UI"],"limitations":["Field detection relies on document structure (PDF form fields, text anchors) — unstructured documents require manual field definition","No OCR-based field detection — cannot identify signature locations from scanned documents","Field mapping is heuristic-based — may require manual correction for ambiguous field names","Limited to PDF documents — other formats (Word, images) require conversion first"],"requires":["Document file (PDF format preferred)","DottedSign API credentials with document analysis permissions","Optional: field mapping rules or templates for common document types"],"input_types":["PDF document file","optional: field mapping hints or templates","optional: recipient role definitions"],"output_types":["extracted field list with positions and types","field-to-recipient mapping suggestions","validation report (required fields, conflicts)"],"categories":["data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-dottedsign-official--dottedsign-mcp__cap_7","uri":"capability://planning.reasoning.signing.deadline.enforcement.and.escalation","name":"signing deadline enforcement and escalation","description":"Monitors signing task deadlines and triggers escalation actions (reminders, notifications to managers, task reassignment) when deadlines approach or are missed. The MCP server maintains deadline context and allows the LLM to implement custom escalation logic based on organizational policies.","intents":["Automatically escalate to the manager if a signature isn't obtained 24 hours before deadline","Send urgent reminders to recipients with <12 hours until deadline","Track overdue signing tasks and generate compliance reports"],"best_for":["Organizations with strict compliance requirements and deadline-driven workflows","Teams managing high-stakes agreements where missed deadlines have business impact","Developers building LLM agents that need to enforce SLA-like constraints"],"limitations":["Deadline enforcement is client-side (in MCP server) — requires periodic polling to detect deadline breaches","No native escalation API in DottedSign — escalation actions must be implemented via external integrations (email, Slack, etc.)","Cannot reassign signing tasks to different recipients — only supports reminders and notifications","Timezone handling is complex — requires explicit timezone configuration for deadline calculations"],"requires":["Signing task with deadline timestamp","MCP server with polling or scheduled task capability","Optional: external notification system (email, Slack) for escalation actions","Timezone configuration for deadline calculations"],"input_types":["signing task ID","deadline timestamp","escalation policy (thresholds, actions)","optional: escalation recipient (manager email, Slack channel)"],"output_types":["deadline status (on-track, at-risk, overdue)","escalation action confirmation","compliance report with deadline metrics"],"categories":["planning-reasoning","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-dottedsign-official--dottedsign-mcp__cap_8","uri":"capability://planning.reasoning.multi.party.signing.workflow.orchestration","name":"multi-party signing workflow orchestration","description":"Coordinates signing workflows with multiple signers, enforcing signer order (sequential vs. parallel) and managing dependencies between signing steps. The MCP server tracks which signers have completed their signatures and determines when subsequent signers can begin, enabling complex approval chains and multi-party agreements.","intents":["Create a contract that requires CEO signature first, then CFO, then legal review","Manage parallel signing where multiple departments sign simultaneously","Enforce that all signers complete before document is finalized"],"best_for":["Organizations with complex approval hierarchies and multi-party agreements","Teams managing contracts that require sequential sign-offs from multiple roles","Developers building LLM agents for enterprise document workflows"],"limitations":["Signer order must be pre-defined — cannot dynamically adjust order based on runtime conditions","No conditional branching — cannot route to different signers based on document content or previous signatures","DottedSign API has limited native support for sequential signing — may require custom logic in MCP server","No built-in escalation if a signer in the chain is unavailable — requires manual intervention"],"requires":["DottedSign API with multi-signer support","Signer list with defined order and dependencies","MCP server with workflow orchestration logic"],"input_types":["signer list with email addresses and order","signing type (sequential or parallel)","optional: conditional routing rules"],"output_types":["workflow execution plan with signer sequence","current signer status and next signer in queue","completion percentage and estimated time to completion"],"categories":["planning-reasoning","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-dottedsign-official--dottedsign-mcp__cap_9","uri":"capability://data.processing.analysis.audit.trail.generation.and.compliance.reporting","name":"audit trail generation and compliance reporting","description":"Generates comprehensive audit trails of signing activities (who signed, when, IP address, device info) and produces compliance reports for regulatory requirements. The MCP server aggregates signing metadata from DottedSign and formats it for audit purposes, enabling the LLM to answer compliance questions and generate reports on demand.","intents":["Generate an audit report for a signed contract for compliance verification","Verify that all signers completed signing and retrieve their signing timestamps","Create a compliance report showing all signing activities for a given time period"],"best_for":["Organizations in regulated industries (finance, healthcare, legal) with strict audit requirements","Teams managing high-value contracts that require detailed signing records","Compliance officers and auditors who need to verify signing authenticity"],"limitations":["Audit data is limited to what DottedSign API exposes — may not include all metadata (e.g., device fingerprints)","Report generation is manual (via MCP calls) — no automated scheduled reporting","Audit trail immutability depends on DottedSign's backend — no cryptographic verification in MCP server","Cannot modify or redact audit records — all data is read-only from DottedSign"],"requires":["DottedSign API credentials with audit log access","Signing task ID or date range for report generation","Optional: compliance framework specification (SOC 2, HIPAA, etc.)"],"input_types":["signing task ID or date range","optional: compliance framework or report template","optional: filter criteria (signer, document type)"],"output_types":["structured audit trail (JSON or CSV)","formatted compliance report (PDF or HTML)","audit summary with key metrics (signing time, signer count, etc.)"],"categories":["data-processing-analysis","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":42,"verified":false,"data_access_risk":"high","permissions":["DottedSign API key and account credentials","Claude or ChatGPT with MCP client support (Claude Desktop 0.3.0+, or compatible ChatGPT plugin framework)","Network connectivity to DottedSign API endpoints","DottedSign account with at least one pre-configured template","Template IDs and field names documented or discoverable via DottedSign API","LLM context window large enough to store template metadata (typically <5KB per template)","Valid signing task ID or recipient email address","DottedSign API credentials with read permissions","Network connectivity to DottedSign API","Recipient list in structured format (email addresses minimum, optional: name, company, custom fields)"],"failure_modes":["Requires active DottedSign account with API credentials — no offline operation","MCP protocol latency adds ~200-500ms per request due to context window serialization","Limited to operations exposed by DottedSign API — cannot customize signing logic beyond platform capabilities","No built-in request queuing or retry logic — relies on LLM's error handling","Requires pre-existing templates in DottedSign account — cannot create new templates via MCP","Template field mapping is static — dynamic field injection requires manual template updates in DottedSign UI","No template versioning support — changes to templates affect all future requests using that template ID","Status polling is eventual-consistent — may lag 30-60 seconds behind actual DottedSign state","No webhook support for real-time notifications — requires active polling or periodic checks","Cannot filter by date range or custom metadata — only supports task ID or email-based queries","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.21549684491229837,"quality":0.45,"ecosystem":0.7000000000000001,"match_graph":0.25,"freshness":0.75,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:21.550Z","last_scraped_at":"2026-05-03T13:59:57.743Z","last_commit":"2026-04-15T03:41:46Z"},"community":{"stars":114,"forks":19,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=dottedsign-official--dottedsign-mcp","compare_url":"https://unfragile.ai/compare?artifact=dottedsign-official--dottedsign-mcp"}},"signature":"JZmWrOJX6l83fmkdBAvgvu11FMRNP4UWQCJqfzAEPQM6GVdD7K5AM8mEsO7XBQdgo9caEZy7XWRzWOmTLm9uDg==","signedAt":"2026-06-21T19:23:13.908Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/dottedsign-official--dottedsign-mcp","artifact":"https://unfragile.ai/dottedsign-official--dottedsign-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=dottedsign-official--dottedsign-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}