protogrid

Search / pro.tvarka/sign

sign

R2· OAuth, once

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

v1.12.0 · active · website · descriptor JSON · versions

An agent can connect after a one-time OAuth consent by a human.Remote endpoint behind OAuth 2. Tokens stay with the agent; the registry only exposes the authorization metadata.
Quality83good
Trust82of 100
Uptime, 30 days98%
Latency p50765 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "sign": {
      "type": "http",
      "url": "https://sign-api.tvarka.pro/mcp",
      "headers": {
        "Authorization": "Bearer ${SIGN_TOKEN}"
      }
    }
  }
}
claude mcp add --transport http sign https://sign-api.tvarka.pro/mcp --header "Authorization: Bearer ${SIGN_TOKEN}"
[mcp_servers.sign]
url = "https://sign-api.tvarka.pro/mcp"
bearer_token_env_var = "SIGN_TOKEN"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sign": {
      "type": "remote",
      "url": "https://sign-api.tvarka.pro/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer {env:SIGN_TOKEN}"
      }
    }
  }
}
{
  "mcpServers": {
    "sign": {
      "type": "http",
      "url": "https://sign-api.tvarka.pro/mcp",
      "headers": {
        "Authorization": "Bearer ${SIGN_TOKEN}"
      }
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=sign&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vc2lnbi1hcGkudHZhcmthLnByby9tY3AiLCJoZWFkZXJzIjp7IkF1dGhvcml6YXRpb24iOiJCZWFyZXIgJHtTSUdOX1RPS0VOfSJ9fQ%3D%3D"
}
{
  "servers": {
    "sign": {
      "type": "http",
      "url": "https://sign-api.tvarka.pro/mcp",
      "headers": {
        "Authorization": "Bearer ${SIGN_TOKEN}"
      }
    }
  }
}
{
  "mcpServers": {
    "sign": {
      "httpUrl": "https://sign-api.tvarka.pro/mcp",
      "headers": {
        "Authorization": "Bearer ${SIGN_TOKEN}"
      }
    }
  }
}
extensions:
  "sign":
    enabled: true
    name: "sign"
    type: streamable_http
    uri: "https://sign-api.tvarka.pro/mcp"
    headers:
      "Authorization": "Bearer ${SIGN_TOKEN}"
    timeout: 300

Placeholders to fill from your own secret store: ${SIGN_TOKEN}. The registry never accepts secret values.

Quality 83 / 100good

protocoln/a · weight 25
  • n/a
    protocol.modern, protocol.stateless, protocol.transport, protocol.list_ttlno remote answered a protocol handshake (not probed yet, unreachable, or local-only)
authorization83 · weight 15
  • pass
    auth.prmProtected Resource Metadata (RFC 9728) published
  • pass
    auth.as_metadataauthorization server metadata reachable
  • warn
    auth.cimdonly Dynamic Client Registration, deprecated in 2026-07-28 in favour of CIMD
  • n/a
    auth.secret_in_urlno templated URL
tool hygienen/a · weight 30
  • n/a
    tools.descriptions, tools.description_length, tools.schemas, tools.annotations, tools.directory_hints, tools.token_cost, tools.api_dumptool list unknown (behind auth, not probed, or empty)
stabilityn/a · weight 15
  • n/a
    stability.changes, stability.rug_pulltool list unknown
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

Tool list unknown · checked 2026-10-20 09:31 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 82 / 100

no-repository
provenance55
liveness99
freshness100
hygiene80

+dns-namespace +website +reachable +uptime-98% +updated-10d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://sign-api.tvarka.pro/mcp streamable-httpoauth2 AS: https://sign-api.tvarka.proyes98%765 ms–2026-10-20

Tools (0)

No tools observed. Tools appear once a credential-free probe can list them.

Schemas: list_tools.

Similar MCP servers

More from pro.tvarka

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