pro.tvarka/sign

Registre officiel Productivité

Qualified and simple e-signatures: request signing, track ceremonies and download signed documents.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http sign 'https://sign-api.tvarka.pro/mcp' --header 'Authorization: <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.>'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "sign": {
            "type": "http",
            "url": "https://sign-api.tvarka.pro/mcp",
            "headers": {
                "Authorization": "<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.>"
            }
        }
    }
}

Questions fréquentes

Qu'est-ce que pro.tvarka/sign ?

Qualified and simple e-signatures: request signing, track ceremonies and download signed documents.

Comment installer pro.tvarka/sign ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http sign 'https://sign-api.tvarka.pro/mcp' --header 'Authorization: <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.>'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour pro.tvarka/sign ?

Oui. Il attend Authorization, à renseigner dans sa configuration.

Qui maintient pro.tvarka/sign ?

Il est publié par pro.tvarka. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.