Docs

MCP server

sigillo speaks the Model Context Protocol over Streamable HTTP. Endpoint and authentication:

Endpoint:  POST https://sigillo.ch/mcp
Auth:      Authorization: Bearer sig_…
Protocol:  MCP 2025-06-18

Connect

Claude Desktop / Claude Code / ChatGPT

Server configuration with Streamable-HTTP transport:

{
  "mcpServers": {
    "sigillo": {
      "transport": "streamable-http",
      "url":  "https://sigillo.ch/mcp",
      "auth": { "type": "bearer", "token": "sig_…" }
    }
  }
}

stdio-only clients (bridge)

Clients without HTTP transport use the stdio bridge, which forwards to the HTTP endpoint:

docker run -i --rm \
  -e SIGILLO_TOKEN=sig_… \
  ghcr.io/kardungla/sigillo-mcp-stdio:latest

Optional: SIGILLO_URL (default https://sigillo.ch/mcp), SIGILLO_TRACE=1 for debug logs to stderr.

Tools

seal_pdfseal:write

Seals a PDF. Modes: timestamp (sync, 1 credit), on_demand (QES via Mobile-ID, 5), mab (multi-signer, 5/signer).

seal_statusseal:read

Status of an async operation (on_demand/mab).

seal_downloadseal:read

Sealed PDF of a completed operation (Base64).

seal_balanceseal:read

Credit balance + cost per mode.

Typical flow (QES)

1. seal_pdf   {mode:"on_demand", pdf_base64, filename, signer, msisdn}
              → {request_id, status:"pending"}
2. seal_status {request_id}   (wiederholen / repeat)
              → {status:"completed"}
3. seal_download {request_id}
              → {sealed_pdf_b64}

A read-only token (seal:read) can query status/download/balance but cannot seal. List tools anytime via the tools/list JSON-RPC call.