Truvera MCP integration

No. The toolkit covers verification and lifecycle - Verify Credential or Presentation, Retrieve Credential, Retrieve Revocation Registries, and Delete Credential - but exposes no issue action, so minting a credential stays in Truvera. Ayro handles the questions that come after issuance.

Only when it is entitled to. Retrieve Credential returns metadata by default; if a password was used to persist the credential, that same password must be supplied to decrypt and return the full credential, so a protected credential stays closed without it.

Create API Key accepts an optional alias and an IP allowlist, so a key it provisions can be restricted to the addresses that should use it, and Delete API Key revokes it once the request is done. Retrieve API Keys lists what already exists before anything new is created.

Retrieve Revocation Registries lists the registries created by the authenticated account, with pagination and filtering, and Verify Credential or Presentation performs the check itself. Ayro can run both so a stale credential is caught rather than accepted on its face.