3 #signing MCP Servers & Clients
Every MCP server and client below is tagged #signing — install one to give Claude, Cursor, VS Code, or any other MCP-compatible client access to signing tools.
All
Kamy
Kamy-Development
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 ca
Lumin
luminpdf
This is an MCP (Model Context Protocol) server for integrating with Lumin's API services. It allows AI assistants (MCP clients, e.g Claude Desktop, Cursor) to interact with Lumin features such as document management, signature requests, and user information.
Agent Receipts
webaesbyamin
Cryptographic accountability for AI agents. Ed25519-signed receipts for every MCP tool call — constraints, chains, AI judgment, invoicing, local dashboard.
Frequently asked questions
What is a #signing MCP server?
- An MCP server tagged #signing implements the Model Context Protocol so AI assistants like Claude, Cursor, and VS Code can access signing-related tools, data, or APIs.
How many #signing MCP servers and clients are there?
- mcp.so currently lists 3 MCP servers and clients tagged #signing.
How do I install a #signing MCP server?
- Open any server below and copy its install snippet into Claude Desktop, Cursor, VS Code, or another MCP client's configuration — remote servers need no separate download.