Bring Sproof
to Claude Code
Learn how to connect Sproof to Claude Code and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Sproof MCP Server?
Connect your Sproof account to any AI agent to automate your European-compliant digital signature workflows. Sproof provides a premier platform for qualified electronic signatures (QES), and this integration allows you to retrieve document metadata, monitor signature requests, and manage contacts through natural conversation.
What you can do
- Document Orchestration — List all managed documents and retrieve detailed profile metadata, including signature status programmatically.
- Signature Request Control — Create and monitor signature requests to ensure your legal documents are executed efficiently directly from the AI interface.
- Contact Management — Access and monitor your contact database to keep your signer records synchronized via natural language.
- Profile & Account Oversight — Retrieve detailed account profile metadata and monitor system usage to ensure your signature pipeline is optimized.
- Compliance Monitoring — Track document validity and signature authenticity using simple AI commands.
How it works
1. Subscribe to this server
2. Enter your Sproof API Key from your account settings
3. Start managing your digital signatures from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Legal & Compliance Officers — quickly retrieve document statuses and monitor signature requests without switching apps.
- HR Managers — automate the sending of employment contracts for signature via natural conversation.
- Administrative Leads — streamline the management of signed documents and monitor contact metadata directly within the chat.
Built-in capabilities (11)
Cancel a pending signature request
Create a new contact for signing
Pass data as a JSON string. Create a new signature request
Get document details
Get account profile details
Get details for a signature request
Get the audit trail for a signature request
List all contacts
List all documents
List all signature requests
List all signers for a signature request
Why Claude Code?
Claude Code registers Sproof as an MCP server in a single terminal command. Once connected, Claude Code discovers all 11 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Sproof data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using Sproof tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
Sproof in Claude Code
Sproof and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Sproof to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Sproof in Claude Code
The Sproof MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Sproof for Claude Code
Every tool call from Claude Code to the Sproof MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
How do I add an MCP server to Claude Code?
Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable