About eContract
eContract provides contract e-signing and PDF verification for developers and AI agents. Agents can prepare and track agreements, while each signer must sign personally through an individual link.
Key features
- 01Create contracts from PDFs, DOCX files or templates
- 02Send signatures in sequence or in parallel
- 03Track signing and send reminders
- 04Download signed PDFs and audit trails
- 05Verify digital PDF signatures
- 06List templates and summarize contracts
Use cases
- 01Send an agreement for multiple parties to sign
- 02Check signing progress and follow up with signers
- 03Retrieve a signed PDF with its audit evidence
- 04Verify digital signatures in a PDF
MCP support
The Streamable HTTP MCP server exposes contract creation, signing management, document retrieval, template and analysis, and PDF verification tools. Clients authenticate with OAuth 2.1 or an API key; agents cannot sign or decline on behalf of people.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.econtract.online/mcpclaude mcp add --transport http online-econtract https://api.econtract.online/mcp{"mcpServers":{"online-econtract":{"type":"http","url":"https://api.econtract.online/mcp"}}}Open in Cursor{"servers":{"online-econtract":{"type":"http","url":"https://api.econtract.online/mcp"}}}Open in VS Code{"mcpServers":{"online-econtract":{"type":"http","url":"https://api.econtract.online/mcp"}}}{"mcpServers":{"online-econtract":{"serverUrl":"https://api.econtract.online/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEContractLayer
Contract infrastructure for developers and AI agents, by eContract.
Let an AI agent prepare a contract, send it for e-signature, follow up and archive the signed PDF, while every signature stays with a real person.
MCP server
https://api.econtract.online/mcp
Streamable HTTP. Sign in with your eContract account (OAuth 2.1) or send an API key as Authorization: Bearer cl_live_…. Listed in the official MCP Registry as online.econtract/mcp (server.json).
| Tool | What it does |
|---|---|
send_contract | Create a contract from a PDF/DOCX (inline, link or template) and send it to the signers, in order or in parallel; place each signature next to a text with signatureAnchor |
list_contracts, get_contract | What is waiting, who has signed, what comes next |
get_signing_links, send_reminder, void_contract | Share personal signing links, chase signers, cancel |
download_signed_document, get_audit_trail | The signed PDF and the signing evidence |
verify_pdf | Check the digital signatures in any PDF |
list_templates, get_template, analyze_contract | Templates and an AI summary of a contract |
Agents can prepare, send and follow up, but they can never sign or decline for someone: each signer signs through their own link.
Connect your client
Configs and steps for each client are in mcp/: Claude, Claude Code, ChatGPT, Codex, Cursor, VS Code, Gemini CLI, Muse Code, OpenClaw, Hermes Agent.
Repositories
| Repository | What it is |
|---|---|
| verify-pdf | Verify the digital signatures in any PDF with one API call, no API key |
| contract-manager | REST API examples (Node.js, Python): send a contract, place signatures, share links, download the signed PDF and audit trail |
| claude-agent-contracts | A contract-signing agent built with the Claude Agent SDK: plain-language requests, eContract tools only, no cancelling unless allowed |
More examples (agent SDKs, workflow tools) are added alongside the guides on the eContract blog.
Links
- eContract: free e-signatures with PAdES signatures, RFC 3161 timestamps and a hash-chained audit trail
- Developer docs and MCP reference
- OpenAPI document
- Verify a signed PDF
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.