Integration

Truvera integration

Truvera (formerly Dock Certs, by Dock Labs) issues, verifies and revokes W3C verifiable credentials. Create issuer DIDs and organization profiles, issue credentials (optionally emailed to the holder), manage JSON schemas, revocation registries and display templates, build proof templates and proof requests (QR or deep link) to verify holders, use OpenID4VCI issuers and credential offers, send DIDComm messages, manage sub-accounts and webhooks. On-chain operations (DIDs, registries, schemas, revocation) return a job id to check with get_job. In production, issuance and other writes count toward the plan's monthly transaction limit (HTTP 402 once reached). Not exposed: API key management, team administration, DID key export and import, account deletion, low-level DIDComm encrypt, decrypt, sign and verify, delegation rules, ecosystem (trust registry) tools and the OpenID wallet protocol endpoints. Authentication is a Truvera production API key sent as a Bearer token (create it in Truvera Workspace; test-mode keys only work on the testnet host, which this integration does not call).

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Truvera.Built from the 77 Truvera tools below, on the connection you add once.

What you can do with Truvera

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Profile, 7 operations

  • create_profileCreate profilePOSTCreates an organization profile for one of your DIDs; its name, description and logo appear as the issuer in credentials that DID issues.
  • delete_profileDelete profileDELETEDeletes the organization profile of a DID. Does NOT delete the DID nor revoke credentials it issued.
  • get_profileGet profileGETReturns the organization profile (name, logo) attached to one of your DIDs.
  • get_user_profileGet user profileGETReturns the signed-in user's profile: name and image URL.
  • list_profilesList profilesGETLists the organization profiles (issuer name and logo attached to a DID) of this account.
  • update_profileUpdate profilePATCHUpdates the organization profile of one of your DIDs. Change at least one of name, description or logo; leave a field out to keep its value.
  • update_user_profileUpdate user profilePATCHUpdates the user profile. Truvera requires both name and image on every update: read the current values with get_user_profile and send them back with your change.

Proof template, 5 operations

  • create_proof_templateCreate proof templatePOSTCreates a reusable proof (verification) template; then call create_proof_request_from_template each time you need to verify a holder.
  • delete_proof_templateDelete proof templateDELETEDeletes a proof template and its associated data. Irreversible.
  • get_proof_templateGet proof templateGETReturns one proof template with its request definition.
  • list_proof_templatesList proof templatesGETLists proof (verification) templates with their request definition and number of proof requests made from each.
  • update_proof_templateUpdate proof templatePATCHUpdates a proof template. name is required on every update (send the current one to keep it, as read with get_proof_template); leave the other fields out to keep their values.

Registry, 5 operations

  • create_registryCreate registryPOSTCreates a revocation registry on chain owned by one of your DIDs and returns a job id for get_job. Counts as a transaction. Use its id as a credential's status to make it revocable.
  • delete_registryDelete registryDELETEDeletes a revocation registry on chain together with all its revocation entries. Irreversible. Returns a job id for get_job.
  • get_registryGet registryGETReturns a revocation registry's policy, add-only flag and type.
  • list_registriesList registriesGETLists the revocation registries of this account with their type and policy.
  • revoke_or_unrevoke_in_registryRevoke or unrevoke in registryPOSTRevokes or unrevokes several credentials of one registry in a single on-chain update and returns a job id for get_job. Counts as a transaction.

Subaccount, 5 operations

  • create_subaccountCreate subaccountPOSTCreates a sub-account. Trial accounts are limited to 5; paid plans vary (HTTP 402 when the plan does not allow more).
  • delete_subaccountDelete subaccountDELETEDeletes a sub-account. Irreversible.
  • get_subaccountGet subaccountGETReturns one sub-account (id, name, email, image, creation date).
  • list_subaccountsList subaccountsGETLists the account's sub-accounts (id, name, email, image). Sub-accounts segregate data per end customer of an enterprise account.
  • update_subaccountUpdate subaccountPATCHUpdates a sub-account. name is required on every update (send the current one to keep it, as read with get_subaccount); leave image out to keep it.

Template, 5 operations

  • create_templateCreate templatePOSTCreates a credential display template from HTML and CSS, used for the PDF and web view of credentials. Pass its id as a credential's template.
  • delete_templateDelete templateDELETEDeletes a display template.
  • get_templateGet templateGETReturns one display template (name, HTML, CSS).
  • list_templatesList templatesGETLists the credential display templates (HTML and CSS used for PDF and web views).
  • update_templateUpdate templatePATCHReplaces a display template. Truvera requires name, html and css on every update: read the current values with get_template and send all three back with your change.

Webhook, 5 operations

  • create_webhookCreate webhookPOSTRegisters a webhook URL for Truvera events. Each delivery carries a secret token to validate; it is not returned here, see it in Truvera Workspace, Webhooks, after creation.
  • delete_webhookDelete webhookDELETEDeletes a webhook endpoint.
  • get_webhookGet webhookGETReturns one webhook endpoint (url, events, status, created). The signing secret is shown only in Truvera Workspace.
  • list_webhooksList webhooksGETLists webhook endpoints (url, events, status). The signing secret is not returned here; see it in Truvera Workspace, Webhooks.
  • update_webhookUpdate webhookPATCHUpdates a webhook. Truvera requires url and the full events list on every update (read them with get_webhook and send them back with your change); leave status or description out to keep them.

Credential, 4 operations

  • create_credentialCreate credentialPOSTIssues and signs a W3C verifiable credential and returns it. Counts as a transaction. With distribute=true and recipientEmail the credential is emailed to the holder for real. Only metadata is kept unless persist=true.
  • delete_credentialDelete credentialDELETEDeletes a credential's metadata and, if persisted, its stored contents. Cannot be undone. Does NOT revoke or invalidate the credential: use revoke_credential for that.
  • get_credentialGet credentialGETReturns one credential's metadata (issuer, type, revoked flag, dates). Decrypted contents of a persisted credential are not returned (Truvera deprecated password-based retrieval). May hold personal data about the holder.
  • list_credentialsList credentialsGETLists metadata of credentials issued by this account (id, issuer, type, revoked, dates). Contents are not returned unless the credential was persisted. Filter by subjectId (holder DID) or a free-text filter.

Did, 4 operations

  • create_didCreate didPOSTCreates a DID with an auto-generated keypair (on the cheqd network by default) and returns a job id: check get_job until finalized. Counts as a transaction.
  • delete_didDelete didDELETEDeletes a DID and its keypair. With fromBlockchain=true it is also deactivated on chain and can never be resolved or used again. Irreversible. Returns a job id for get_job.
  • get_didGet didGETResolves a DID into its DID document (keys, verification methods). Works for cheqd, key and other supported DID methods, not only your own DIDs.
  • list_didsList didsGETLists the DIDs this account controls, with type, controller, credential count, attached organization profile and trust registries.

Issuer, 4 operations

  • create_openid_issuerCreate openid issuerPOSTCreates an OpenID4VCI issuer: the credential template a holder claims through a credential offer. Create one per credential to issue, then call create_credential_offer.
  • delete_openid_issuerDelete openid issuerDELETEDeletes an OpenID issuer and its offers. Irreversible.
  • get_openid_issuerGet openid issuerGETReturns one OpenID issuer's configuration (credential options, auth provider, claim mapping, single use).
  • list_openid_issuersList openid issuersGETLists the OpenID4VCI issuers of this account with their credential options, auth provider and claim mapping.

Proof request, 4 operations

  • create_proof_requestCreate proof requestPOSTCreates a standalone proof request (no template). Returns qr and response_url to give the holder's wallet; then poll get_proof_request until verified is true or false.
  • delete_proof_requestDelete proof requestDELETEDeletes a proof request and its submitted presentation data. Irreversible.
  • get_proof_requestGet proof requestGETReturns a proof request: verified (true when the holder's presentation checked out), expired, and presentation with the disclosed attributes. Holds personal data disclosed by the holder.
  • list_proof_requestsList proof requestsGETLists proof requests with their verified and expired flags, QR and response URLs.

Schema, 4 operations

  • create_schemaCreate schemaPOSTPublishes a JSON schema describing a credential's subject and returns a job id for get_job. Counts as a transaction. Pass its id as a credential's schema.
  • delete_schemaDelete schemaDELETEDeletes a schema from your account's list.
  • get_schemaGet schemaGETReturns one credential schema (JSON schema body, URI, owner).
  • list_schemasList schemasGETLists the credential JSON schemas created by this account (id, schema body, owner).

Message, 3 operations

  • delete_didcomm_messageDelete didcomm messageDELETEDeletes one received DIDComm message. Irreversible.
  • get_didcomm_messageGet didcomm messageGETReturns one received DIDComm message with sender, type, receipt time and content. May contain personal data sent by the holder.
  • list_didcomm_messagesList didcomm messagesGETLists DIDComm messages received by your DIDs, newest first. Filter by recipient DID (to) or message type.

Credential offer, 2 operations

  • create_credential_offerCreate credential offerPOSTCreates an OpenID4VCI credential offer for an OpenID issuer and returns its offer URL, to show the holder as a QR code or deep link.
  • get_credential_offerGet credential offerGETReturns the credential offer object of an OpenID issuer, as an OpenID client reads it.

History, 2 operations

  • delete_proof_template_historyDelete proof template historyDELETEIrreversibly deletes the whole verification history (every proof request and presentation) of a proof template. The template itself is kept.
  • list_proof_template_historyList proof template historyGETLists the proof requests made from a template, with their verified flag and disclosed presentation. Use verified=true for successful verifications only. Holds personal data disclosed by holders.

Request claim, 2 operations

  • create_claim_requestCreate claim requestPOSTCreates a claim request: the holder scans the returned QR or deep link, enters the listed claims in a wallet, and the credential is then issued automatically. Use only for data you cannot obtain otherwise.
  • list_claim_requestsList claim requestsGETLists open claim requests created with create_claim_request whose holders have not yet submitted their claims.

Ecosystem, 1 operation

  • list_did_ecosystemsList did ecosystemsGETLists the ecosystems (trust registries) a DID participates in, with its role and status in each.

Job, 1 operation

  • get_jobGet jobGETReturns a background job's status (todo, in_progress, finalized or error) and its blockchain result. Use it after create_did, create_registry, create_schema or a revocation until status is finalized or error.

Limit, 1 operation

  • get_plan_limitsGet plan limitsGETReturns the plan limits of the account (transaction allowance and feature limits), as the vendor's raw object.

Mark read, 1 operation

  • mark_notifications_readMark notifications readPOSTMarks every pending notification of the account as read.

Metadata, 1 operation

  • get_did_metadataGet did metadataGETReturns the stored metadata of one of your DIDs, including the job id of its creation.

Notification, 1 operation

  • list_notificationsList notificationsGETLists account notifications (type, data, created), newest first. Filter read or unread with read.

Pex, 1 operation

  • get_proof_request_pexGet proof request pexGETReturns the Presentation Exchange (PEX) definition of a proof request, as a wallet reads it.

Request, 1 operation

  • create_proof_request_from_templateCreate proof request from templatePOSTCreates a proof request from a template. Returns qr and response_url for the holder's wallet; then poll get_proof_request until verified is true or false.

Request url, 1 operation

  • create_oid4vp_request_urlCreate oid4vp request urlPOSTReturns an OpenID4VP deep link or QR URL for an existing proof request, for an OID4VP-compatible wallet to scan.

Revoke, 1 operation

  • revoke_credentialRevoke credentialPOSTRevokes a revocable credential, recorded on chain; verifiers will then reject it. Counts as a transaction. Undo with unrevoke_credential.

Send, 1 operation

  • send_didcomm_messageSend didcomm messagePOSTSends a DIDComm message to a holder DID through Truvera's relay, delivered for real. In production it is refused with HTTP 402 once the plan's transaction limit is reached. Accepts plaintext, signed or encrypted DIDComm messages.

Send presentation, 1 operation

  • send_presentation_to_proof_requestSend presentation to proof requestPOSTSubmits a signed verifiable presentation to a proof request, as a holder wallet would; Truvera verifies it and updates the request. Rarely needed: wallets normally do this.

Stats, 1 operation

  • get_account_statsGet account statsGETReturns usage statistics of the account, as the vendor's raw object.

Transaction, 1 operation

  • list_transactionsList transactionsGETLists the account's billable transactions (paged): total count and the transaction records, as returned by Truvera.

Unrevoke, 1 operation

  • unrevoke_credentialUnrevoke credentialPOSTReinstates a previously revoked credential, recorded on chain. Counts as a transaction.

Verify, 1 operation

  • verify_credential_or_presentationVerify credential or presentationPOSTVerifies a signed verifiable credential or presentation: checks its proof and revocation status. Returns verified (boolean) and per-check results. In production it is refused with HTTP 402 once the plan's transaction limit is reached.

Use Truvera from Claude Code, Cursor or Codex

Connect Truvera in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Truvera operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Truvera

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Truvera once

    Add your Truvera connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Truvera integration FAQ

What can you do with the Truvera integration?

LiveContext exposes 77 operations on Truvera, covering profile, proof template, registry and subaccount.

Popular integrations

Browse the whole catalog