Loading…
Qualified and simple e-signatures: request signing, track ceremonies and download signed documents.
pro.tvarka/sign is an MCP server entry in ChatHome Skills, sourced from Official MCP Registry and scored 100/100. As a Model Context Protocol server, it exposes tools that MCP-compatible LLM clients such as Claude, Cursor, and Copilot can call directly, extending an agent's reach beyond its built-in capabilities. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding pro.tvarka/sign to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
mcp add pro.tvarka/sign https://sign-api.tvarka.pro/mcpReview the upstream source before running this command.
{
"_meta": {
"io.modelcontextprotocol.registry/official": {
"status": "active",
"isLatest": true,
"updatedAt": "2026-10-10T13:30:03.679905Z",
"publishedAt": "2026-10-10T13:30:03.679905Z",
"statusChangedAt": "2026-10-10T13:30:03.679905Z"
}
},
"server": {
"name": "pro.tvarka/sign",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://sign-api.tvarka.pro/mcp",
"type": "streamable-http",
"headers": [
{
"name": "Authorization",
"isSecret": true,
"description": "Optional. Clients with OAuth sign-in (Claude, ChatGPT, Copilot, VS Code, Gemini CLI) connect without it: the person confirms with their eID, picks the company and allows the connection. Otherwise send Bearer <your Tvarka Sign API key>. Every active, identified company member with Sign access can Show or Copy a production key in Settings: https://sign.tvarka.pro/sign/app/settings/#api-keys. API access is automatic; the secret is prepared on first use. Company administrators invite users by email and select Employee or Representative (all rights). The optional email checkbox requests a protected ZIP after identity confirmation. User rows have visible Change rights, Send API key and API settings actions. Existing integrations and sandbox keys remain supported. Deliberate revocations are not silently undone. Rotation allows at most 24 hours of overlap. See https://sign-api.tvarka.pro/docs#keys. A legacy sandbox key (tsk_test_) simulates without adding a signature; production (tsk_live_) uses normal workspace billing. ATK and Due Diligence credentials are separate."
}
]
}
],
"version": "1.12.0",
"websiteUrl": "https://sign-api.tvarka.pro/docs",
"description": "Qualified and simple e-signatures: request signing, track ceremonies and download signed documents."
}
}