eContract
Send contracts for e-signature, track signing, get signed PDFs and audit trails, verify any PDF.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http econtract 'https://api.econtract.online/mcp'{
"mcpServers": {
"econtract": {
"type": "http",
"url": "https://api.econtract.online/mcp"
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
ContractLayer
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/mcpStreamable 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
Frequently asked questions
What is eContract?
Send contracts for e-signature, track signing, get signed PDFs and audit trails, verify any PDF.
How do I install eContract?
It runs as a remote server. In Claude Code: claude mcp add --transport http econtract 'https://api.econtract.online/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does eContract need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is eContract open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains eContract?
It is published by contractlayer. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.