# Sproof MCP

> Sproof. Manage European-compliant digital signatures, documents, and contacts directly through your AI agent. This server connects to Sproof's platform, letting you list documents, monitor signature requests, create new signers, and retrieve detailed account metadata using natural language conversation. It handles the full workflow of legal document signing.

## Overview
- **Category:** industry-titans
- **Price:** Free
- **Tags:** sproof, digital-signature, electronic-signature, document-management, qes, legal-tech, compliance-automation, mcp

## Description

You're connecting **Sproof** to your AI agent so you can handle digital signatures that meet European compliance standards—eIDAS. This whole server manages documents, keeps track of who signs what, and handles contact records; you do it all through natural language chat.

To get started, you don't need to jump between web portals. You just tell your agent what you need done. If you want a full roster of every file Sproof is tracking for compliance, use **list_documents**. Need the nitty-gritty details on one specific document? Run **get_document** to pull its metadata and current status.

When it comes time to get documents signed, your agent takes over the whole workflow. You can kick off a new signing process using **create_signature_request**, starting the chain for a document that needs multiple approvals. Want to see what requests are currently active or waiting for someone to sign? Just ask for a summary of all outstanding requests with **list_signature_requests**. If you realize a signature request is stalled and it shouldn't be, you can use **cancel_signature_request** to stop the process before it goes further.

To control the flow, your agent lets you define the signers. You retrieve the names of people who need to sign using **list_signers**, which shows exactly who needs to approve the document and in what order. It handles sequencing so you can make sure approvals come in the right way. If you find a specific request is confusing, you pull up all its details with **get_signature_request**. 

Before anyone can sign, your agent helps you manage contacts. You get a complete list of every person or company stored in the system with **list_contacts**. Need to add someone new who's going to be signing? Use **create_contact** to build out that new record right from the chat. This keeps all your signer information current.

For legal and compliance teams, this is where the server shines. When you need proof of validity, you run **list_audit_trail**. That gives you a step-by-step timeline of every action taken on a request, which is critical for proving document integrity. You also get your overall system context by calling **get_profile**, pulling general account data and usage metrics.

If you're dealing with complex workflows, the agent makes sure everything connects: it starts the signing process (**create_signature_request**), manages who signs it in sequence (**list_signers**), lets you stop things if they go sideways (**cancel_signature_request**), and then gives you all the historical proof of every single step with **list_audit_trail**. You can check the status of any document using **get_document**, review a deep dive on one request using **get_signature_request**, or simply pull up the whole roster of managed files with **list_documents**.

Your agent handles all this communication, pulling fresh data from your Sproof account so you never have to switch screens. You're managing compliance-grade document signing and contact records—all in one conversation.

## Tools

### cancel_signature_request
Stops a pending signature request from moving forward.

### create_contact
Adds a new person or company record to your signing contact list.

### create_signature_request
Starts the process for a new document requiring multiple signatures.

### get_document
Pulls detailed metadata and status information about a specific managed file.

### get_profile
Retrieves your account's overall profile details and system usage data.

### get_signature_request
Gets specific, detailed information on a single signature request by its ID.

### list_audit_trail
Provides the step-by-step record of actions taken during a signature process for compliance review.

### list_contacts
Shows a list of all contacts currently stored in your system.

### list_documents
Lists every document that Sproof has managed for you.

### list_signature_requests
Shows a summary of all signature requests currently active or pending completion.

### list_signers
Retrieves the list of people required to sign on a specific document.

## Prompt Examples

**Prompt:** 
```
List all pending signature requests in Sproof.
```

**Response:** 
```
I've retrieved your requests. You have 3 pending documents: 'Consulting Agreement', 'Employee Handbook', and 'Vendor Terms'. Would you like to check who still needs to sign them?
```

**Prompt:** 
```
Show me all pending signature requests with their signing progress and deadline status.
```

**Response:** 
```
12 pending signature requests. Urgent (3): "Service Agreement - Meridian" (2/4 signed, deadline tomorrow), "NDA - TechVentures" (0/2 signed, overdue 2 days), "Employment Contract - D. Kim" (1/1 signed, awaiting notarization). In Progress (5): avg 60% completion, deadlines within 2 weeks. Awaiting Review (4): documents uploaded, not yet sent. Total documents pending: 34 pages across 12 requests. Reminders sent today: 5 (auto). Average signing time: 1.4 days. Completion rate this month: 89%.
```

**Prompt:** 
```
Create a new signature request for the annual vendor agreement and add three signers.
```

**Response:** 
```
Signature request created: "Annual Vendor Agreement 2025-2026". Document: vendor_agreement_2025.pdf (12 pages). Signers added: 1) David Chen (Vendor, CEO) - david@vendor.com, 2) Sarah Williams (Procurement Manager) - sarah@yourcompany.com, 3) James Park (Legal Counsel) - james@yourcompany.com. Signing order: sequential (Vendor → Procurement → Legal). Signature fields placed: 6 (2 per signer). Deadline: June 1, 2025. Reminders: auto every 3 days. Audit trail: enabled. eIDAS qualified: yes. Invitation emails sent to all signers.
```

## Capabilities

### Track Document Status
Get metadata for any document to check its current signature status, audit trail, or ownership details.

### Orchestrate Signatures
Initiate new signature requests and control the flow by adding signers in a specific order (sequential).

### Manage Contacts
List all current contacts or create brand-new records for people who need to sign documents.

### View Request History
Pull a full list of all signature requests, including details on progress and deadlines.

### Audit Compliance Records
Retrieve the complete audit trail for any request to prove document validity and signing sequence.

## Use Cases

### Onboarding a new employee
The HR manager needs five different contracts signed (NDA, employment agreement). They ask their agent: 'Start the signature process for John Doe.' The agent uses `create_signature_request`, adds John's contact using `create_contact`, and sets up sequential signing fields across all necessary documents.

### Reviewing overdue agreements
The legal team needs to know which contracts are stuck. They prompt the agent: 'List all signature requests with pending signers.' The agent uses `list_signature_requests` and then, if a request is stalled, they run `list_signers` to identify exactly who hasn't responded.

### Checking document history for an audit
A compliance officer needs proof of when a specific agreement was signed. They ask the agent to 'Show me the full trail for the Q3 vendor contract.' The agent runs `list_audit_trail` and provides the detailed, verifiable timeline.

### Updating contact details
The admin lead knows a key vendor changed their address. They ask: 'Update Jane Smith's record for our signing database.' The agent uses `list_contacts` to confirm her existence and then updates the metadata, keeping the records current.

## Benefits

- Automate the signing process end-to-end. Instead of manually creating requests and adding signers in a separate dashboard, you can use `create_signature_request` and add multiple recipients sequentially—all from your chat agent.
- Eliminate status guesswork with granular tools. Use `get_document` or `get_signature_request` to check document metadata, signature progress, and expiry dates without logging into the main Sproof portal.
- Maintain a clean audit trail for compliance. The `list_audit_trail` tool instantly compiles every action taken on a request, giving you the proof needed for legal sign-off.
- Keep your records accurate. Run `list_contacts` or use `create_contact` to ensure that all necessary personnel are in the system and ready before initiating any agreement.
- Centralize oversight. By using `list_signature_requests`, you get a high-level view of every document needing action, allowing you to prioritize tasks across your entire legal department's workload.

## How It Works

The bottom line is: you manage complex legal document workflows using simple natural language prompts inside your existing AI client.

1. Subscribe to this server on Vinkius, then provide your Sproof API Key in the settings.
2. Tell your AI agent what you need. For example: 'List all pending signature requests' or 'Create a new request for the vendor agreement.'
3. The agent runs the necessary tool (like `list_signature_requests`) and presents the structured data, letting you continue managing the workflow right in the chat.

## Frequently Asked Questions

**How do I start a new signature request using create_signature_request?**
You initiate it by asking your agent to 'Create a new signature request for X document.' The server handles the setup, allowing you to specify signers and set the signing order without manual steps.

**Can I check if a contact exists before creating them? (list_contacts)**
Yes. Run `list_contacts` first. This shows all current records, allowing you to verify if the person is already in your database before calling `create_contact`. It prevents duplicate data.

**If a request stalls, how do I know who's responsible? (list_signers)**
Use `list_signers` with the specific request ID. This tool immediately tells you exactly which people are assigned to that document and if they have signed it yet.

**What is the difference between get_document and list_documents?**
`list_documents` gives you a summary of all files managed by Sproof. `get_document`, however, pulls deep metadata—like its specific signature status or audit details—for one document only.

**Can I cancel a request before it's finished? (cancel_signature_request)**
Yes. You can run `cancel_signature_request` and specify the ID. This stops the workflow immediately, which is useful if a contract needs renegotiation or if signers change.

**What does the `list_audit_trail` tool track regarding signature requests?**
It provides a complete, immutable history of actions taken on a request. You can see exactly who viewed the document, when specific signers accessed it, and any metadata changes throughout its lifecycle.

**How do I check my organization's settings using `get_profile`?**
The `get_profile` tool pulls your account's current operational metadata. This lets you verify system usage, confirm compliance settings, or track overall organizational parameters without logging into the web portal.

**What’s the functional difference between using `list_signature_requests` and `get_signature_request`?**
The list tool gives you a high-level overview of all your requests (status, document name). The single request tool pulls every specific detail—like current completion percentage or individual signer status.

**How do I find my Sproof API Key?**
Log in to your Sproof account, navigate to **Account Settings** > **API**, and you will find your unique secret API Key there.