Mcp

Tenzro Canton MCP

Canton MCP: DAML submit, contracts, events, parties, domains, CIP-56 tokens, DvP, DAR upload.

Verified: 2026-05-13 (mcp-registry-ingest-2026-05-13+enrich-capability-skill)

When to use Tenzro Canton MCP

Choose if

Your agent operates inside a Canton-network deployment (Digital Asset's DAML enterprise ledger) and needs to submit transactions, query contracts, stream events, manage parties/domains, upload DARs, or run CIP-56 token / DvP settlement flows. The OAuth 2.1 + DPoP surface is appropriate for regulated environments where bearer- token replay protection matters.

Avoid if

You need a general blockchain MCP (Ethereum, Solana, Sui — use a chain-specific oracle). Also avoid for ad-hoc experimentation: the onboarding ritual (DPoP, RAR scopes, JWT minting via human or delegated-agent flows) is heavyweight, and pricing for mainnet operations is not documented. Best suited for teams already committed to Canton.

Risk Flags

  • HIGH auth Write operations require OAuth 2.1 + DPoP (RFC 9449) — bearer JWTs minted via `tenzro_onboardHuman` / `tenzro_onboardDelegatedAgent` with Rich Authorization Requests (RAR) scope constraints. Read-only public tools available without auth. Onboarding is non-trivial for autonomous agents.
  • HIGH scope Specialized for Canton/DAML enterprise ledgers — useful only for agents operating inside Canton-network deployments (tokenized assets, regulated settlement). Not a general blockchain MCP.
  • MEDIUM cost No explicit pricing for mainnet operations. Testnet faucet distributes 100 TNZO per request with 24h cooldown. Production cost structure undisclosed.
  • MEDIUM maturity Phase-1 implementation per README — "Byzantine-robust aggregation, multi-region scale, and TEE-resident data are roadmap." Limited production track record.

Cost

Type: Unknown

Distribution

MCP Registry
network.tenzro/tenzro-canton
Repository
https://github.com/tenzro/tenzro-network