Treza

You can use the Treza MCP Server to expose and orchestrate Treza’s enclave management, KYC, attestation, and x402 payment capabilities to AI agents and other MCP clients. It enables you to discover, authenticate, and invoke a rich set of Treza operations through MCP-compatible tooling while keeping sensitive signing keys securely inside trusted secure enclaves. This server focuses on practical actions you can perform via MCP endpoints and tooling, from enclave lifecycle to KYC checks and on-chain interactions.

How to use

To integrate with the Treza MCP Server, you typically use an MCP client that can load and run MCP tools exposed by the server. The recommended approach is to run the MCP client bundled with Treza tooling, which provides a collection of enclave management, attestation, task scheduling, API key management, and KYC-related tools. You connect to the MCP configuration that points to the Treza MCP server and start issuing tools as you would with any other MCP-enabled service.

Key benefits you gain include secure signing inside enclaves, automatic handling of 402 payments for API calls, and simple KYC verifications that can be used to gate access to resources. With MCP you can discover payable services, manage enclaves, view attestation data, and generate integration snippets for rapid development.

How to install

Prerequisites: ensure you have Node.js and npm installed, and you can access the Treza MCP server configuration. You should also have a supported MCP client ready to consume Treza MCP tools.

# Install the MCP client package and Treza SDK tooling
npm install @treza/sdk ethers

# If using the MCP server tooling package, install it as well
npm install @treza/mcp

Additional setup and usage notes

Configure the MCP client to load the Treza MCP server by providing the MCP configuration that references Treza’s MCP tools. One common pattern is to declare a server named treza in your MCP config, using npx to launch the MCP tooling for Treza.

{
  "mcpServers": {
    "treza": {
      "command": "npx",
      "args": ["@treza/mcp"],
      "env": {
        "TREZA_BASE_URL": "https://app.trezalabs.com"
      }
    }
  }
}

Security and signing considerations

Treasuring private keys inside a secure enclave is central to the Treza approach. When you enable enclave signing, signing requests flow from your app through the Treza MCP Server to the Nitro Enclave, ensuring keys never leave the hardware boundary. If you are in development, you may temporarily use a local signer, but you should switch to a proper enclave signer for production workloads.

Examples of common workflows

Use the MCP server to access enclave lifecycle actions, attestation data, and KYC endpoints, and to generate code snippets for quick integration into your apps. You can also discover payable services and programmatic wallets for x402 payments.

Available tools

getEnclaves

Retrieve all enclaves for a given wallet address.

getEnclave

Fetch details for a specific enclave by ID.

createEnclave

Create and configure a new secure enclave on a chosen provider.

updateEnclave

Update enclave configuration or metadata.

deleteEnclave

Delete an existing enclave.

pauseEnclave

Pause an active enclave to stop compute without destruction.

resumeEnclave

Resume a paused enclave to continue operations.

terminateEnclave

Completely destroy an enclave and associated resources.

getEnclaveLogs

Fetch logs across ECS, Step Functions, Lambda, and applications.

getAttestation

Retrieve the full attestation document with PCR measurements.

getVerificationStatus

Provide a quick verification status for an enclave.

verifyAttestation

Perform comprehensive verification including compliance checks.

generateIntegrationSnippet

Produce ready-to-use code snippets for integration in multiple languages.

getProviders

List available infrastructure providers and configurations.

getProvider

Fetch details about a specific provider.

getTasks

List scheduled tasks associated with a wallet.

createTask

Create a new scheduled task for enclave automation.

updateTask

Update an existing scheduled task.

deleteTask

Remove a scheduled task.

getApiKeys

List all API keys for a wallet.

createApiKey

Create an API key with fine-grained permissions.

updateApiKey

Update API key permissions or status.

deleteApiKey

Revoke an API key.

getGitHubAuthUrl

Generate a GitHub OAuth authorization URL.

exchangeGitHubCode

Exchange OAuth code for an access token.

getGitHubRepositories

List user repositories from GitHub.

getRepositoryBranches

List branches for a GitHub repository.

searchDockerImages

Search Docker Hub for images.

getDockerTags

Fetch available tags for a Docker image.

isAdult

KYC convenience: check if the proven identity is an adult.

getCountry

KYC convenience: retrieve the country of the user.

hasValidDocument

KYC convenience: verify document validity.

getDocumentType

KYC convenience: obtain document type.

getClaims

Retrieve all public KYC claims for a given proof ID.

meetsRequirements

Check if a user meets a set of KYC requirements.

submitProof

Submit a proof to the API for verification.

verifyProof

Verify a proof via API.

getProof

Get proof details from the API.

hasValidKYC

Check on-chain KYC validity for a user address.

getProofFromChain

Fetch on-chain proof details from the KYC verifier contract.

getUserProofId

Retrieve the latest on-chain proof ID for a user.

submitProofOnChain

Submit proof data to the blockchain.

verifyProofOnChain

Verify a proof on the blockchain.