Submit

#e-signature

6 results found

E

e签宝 MCP 工具

Mirror of

E

Esign MCP

基于 Model Context Protocol (MCP) 的 e签宝电子签署工具,支持文件上传、签署流程创建、签署状态查询等功能。

S

Signbee — Document Signing for AI Agents

Send, sign, and verify documents with a single tool call. Converts markdown to PDF, handles two-party signing via email, and delivers SHA-256 certified signed copies. No SDK, no browser — just npx signbee-mcp.

K

Kamy

The document layer for AI-native software. From your agent runtime, generate PDFs from templates, sign them with PAdES B-LT cryptographic signatures (own CA, RFC 3161 timestamps, embedded CRL), edit / fill / redact existing PDFs, and produce a tamper-evident audit trail anyone can verify at https://kamy.dev/verify — no Kamy account required. Tools exposed: render_pdf, sign_pdf, edit_pdf, verify_pdf, list_templates, install_sdk, ask_kamy. Free tier: 100 renders / month, signing included, no credit card. Get an API key at https://kamy.dev/dashboard/api-keys. Tagline: Generate, sign, prove. One API.

E

EAD Enterprise Suite MCP

EAD Enterprise Suite MCP bridges MCP clients (Claude, Cursor, etc.) to EAD Trust's complete enterprise platform. The 39 tools cover signature workflows (create → add docs → add participants → coordinate → activate → cancel → retrieve), certified evidence management with sealing and grouping plus multipart large-file uploads, certified notifications (create → add receivers → send → status → certificate retrieval), dossier lifecycle (create → list → get → templates), and session / authentication management (email/password or OpenID Connect refresh-token). Built by g-digital by Garrigues (J&A Garrigues, S.L.P.), an eIDAS-qualified trust services provider. Two transports: stdio for local clients, HTTP with Bearer OAuth2 for hosted deployments.

E

Ead Factory Mcp

EAD Factory MCP exposes EAD Trust's Evidence Manager and Signature Manager APIs to any MCP-compatible client (Claude Code, Claude Desktop, Cursor, etc.). The 9 tools cover full evidence generation — SHA-256 file hashing, S3 upload, Okta OAuth2 client_credentials authentication, and status polling until COMPLETED — and the complete signature-request lifecycle: create draft → add documents → add signatories / validators / observers → activate the request → retrieve status. Built by g-digital by Garrigues (J&A Garrigues, S.L.P.), an eIDAS-qualified trust services provider. Two transports: stdio for local desktop clients, HTTP with Bearer OAuth2 for hosted deployments.

© 2025 MCP.so. All rights reserved.

Build with ShipAny.