pro.tvarka/sign

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.>'

{
    "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.>"
            }
        }
    }
}