io.github.treza-labs/treza
NPM · @TREZA/MCP · SCANNED AUG 3
Manage secure enclaves (TEEs) with attestation, payments, and signing for AI agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (108 of 109), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (108 of 109), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 44 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1239 tokens (~61/item across 20 items; 16 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @treza/mcp
claude mcp add treza-labs-treza -- npx -y @treza/mcp
codex mcp add treza-labs-treza -- npx -y @treza/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"treza-labs-treza": {
"type": "local",
"command": [
"npx",
"-y",
"@treza/mcp"
],
"enabled": true
}
}
} openclaw mcp add treza-labs-treza --command npx --arg -y --arg @treza/mcp
mcp_servers:
treza-labs-treza:
command: "npx"
args: ["-y", "@treza/mcp"] {
"mcpServers": {
"treza-labs-treza": {
"command": "npx",
"args": [
"-y",
"@treza/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +44
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 31 Jul 26 −27
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 53
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/@treza/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 108 packages
108 packages in the resolved dependency tree · 108 deprecated · 32 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
treza_create_api_key ~71
Create a new scoped API key for programmatic access to the Treza platform. Returns the key only once — store it securely.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Human-readable key name |
| permissions | array | yes | Array of permission scopes |
| walletAddress | string | yes | Wallet address for authorization |
No output schema declared.
No examples provided.
treza_create_enclave ~216
Create a new AWS Nitro Enclave with hardware-isolated TEE. The enclave will generate and manage private keys internally — keys never leave the enclave boundary. Deployment takes 2-5 minutes via Step Functions.
| Name | Type | Req | Description |
|---|---|---|---|
| cpuCount | string | — | Number of vCPUs |
| description | string | yes | Description of the enclave purpose |
| dockerImage | string | — | Docker image to run inside the enclave |
| enableDebug | boolean | — | Enable debug mode |
| exposePorts | string | — | Comma-separated ports to expose |
| memoryMiB | string | — | Memory in MiB |
| name | string | yes | Human-readable name for the enclave |
| providerId | string | — | Provider ID (default: "aws-nitro-enclave") |
| region | string | yes | AWS region to deploy in (e.g. "us-east-1", "eu-west-1") |
| walletAddress | string | yes | Ethereum wallet address of the owner |
| workloadType | string | — | Workload type |
No output schema declared.
No examples provided.
treza_create_task ~90
Create a new scheduled task to run inside an enclave on a cron schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Task description |
| enclaveId | string | yes | Enclave to run the task on |
| name | string | yes | Task name |
| schedule | string | yes | Cron expression (e.g. "0 */6 * * *") |
| walletAddress | string | yes | Wallet address for authorization |
No output schema declared.
No examples provided.
treza_delete_enclave ~55
Permanently delete a terminated enclave. The enclave must be in DESTROYED status before deletion.
| Name | Type | Req | Description |
|---|---|---|---|
| enclaveId | string | yes | Enclave ID to delete |
| walletAddress | string | yes | Wallet address for authorization |
No output schema declared.
No examples provided.
treza_enclave_action ~74
Perform a lifecycle action on an enclave: pause (stop billing), resume (restart), or terminate (destroy infrastructure). Terminate is irreversible.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Lifecycle action |
| enclaveId | string | yes | Enclave ID to act on |
| walletAddress | string | yes | Wallet address for authorization |
No output schema declared.
No examples provided.
treza_get_attestation ~76
Get the attestation document for a deployed enclave. Returns PCR measurements (enclave image hash, kernel hash, application hash, signing cert), certificate chain, and verification endpoints. Use this to cryptographically verify an enclave is running the expected code.
| Name | Type | Req | Description |
|---|---|---|---|
| enclaveId | string | yes | Enclave ID to get attestation for |
No output schema declared.
No examples provided.
treza_get_enclave ~54
Get detailed information about a specific Treza enclave including its status, configuration, provider settings, and GitHub connection.
| Name | Type | Req | Description |
|---|---|---|---|
| enclaveId | string | yes | Unique enclave identifier (e.g. "enc_abc123") |
No output schema declared.
No examples provided.
treza_get_enclave_logs ~76
Retrieve logs from an enclave. Supports filtering by source: ECS deployment, Step Functions workflow, Lambda triggers, application stdout/stderr, or errors only.
| Name | Type | Req | Description |
|---|---|---|---|
| enclaveId | string | yes | Enclave ID |
| limit | number | — | Max log entries to return |
| logType | string | — | Type of logs |
No output schema declared.
No examples provided.
treza_get_provider ~46
Get detailed information about a specific enclave provider including supported regions and configuration options.
| Name | Type | Req | Description |
|---|---|---|---|
| providerId | string | yes | Provider ID (e.g. "aws-nitro-enclave") |
No output schema declared.
No examples provided.
treza_get_verification_status ~41
Quick check of an enclave's verification status and trust level without performing full verification.
| Name | Type | Req | Description |
|---|---|---|---|
| enclaveId | string | yes | Enclave ID to check |
No output schema declared.
No examples provided.
treza_list_api_keys ~63
List all API keys for a wallet address. Keys have scoped permissions (enclaves:read, enclaves:write, tasks:read, tasks:write, logs:read).
| Name | Type | Req | Description |
|---|---|---|---|
| walletAddress | string | yes | Wallet address that owns the API keys |
No output schema declared.
No examples provided.
treza_list_enclaves ~55
List all Treza Nitro Enclaves owned by a wallet address. Returns enclave IDs, names, statuses, regions, and configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| walletAddress | string | yes | Ethereum wallet address that owns the enclaves |
No output schema declared.
No examples provided.
treza_list_providers ~33
List all available enclave providers (e.g., AWS Nitro Enclave) with their supported regions and configuration schemas.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
treza_list_tasks ~44
List all scheduled tasks for a wallet. Tasks are cron-scheduled operations that run inside enclaves.
| Name | Type | Req | Description |
|---|---|---|---|
| walletAddress | string | yes | Wallet address that owns the tasks |
No output schema declared.
No examples provided.
treza_update_enclave ~65
Update an existing enclave's name, description, or configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | New description |
| id | string | yes | Enclave ID to update |
| name | string | — | New name |
| walletAddress | string | yes | Wallet address for authorization |
No output schema declared.
No examples provided.
treza_verify_attestation ~103
Perform comprehensive cryptographic verification of an enclave's attestation. Checks PCR measurements, certificate chain, timestamp validity, nonce matching, and signature. Returns trust level (HIGH/MEDIUM/LOW), compliance status (SOC2, HIPAA, FIPS), and risk score.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge | string | — | Challenge string for additional verification |
| enclaveId | string | yes | Enclave ID to verify |
| nonce | string | — | Nonce for replay protection |
No output schema declared.
No examples provided.