Skip to main content

Tenzro Canton MCP

by network.tenzro

Overview Discussions Admin

Server Details

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

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status: Unhealthy
Last Tested: 2026-09-21 02:42
Transport: Streamable HTTP
URL
Repository: tenzro/tenzro-network
GitHub Stars: 0

TDQS

A3.7/5.0

Scored 2026-05-02 06:40 across 14 tools

Disambiguation4/5

Most tools have distinct purposes, but there is overlap between the general submit_command and specialized convenience tools like create_asset and transfer, which could cause confusion for an agent deciding which to use.

Naming Consistency4/5

All tools start with 'canton_' and mostly follow a verb_noun pattern. However, 'canton_transfer' is verb-only and 'canton_dvp_settle' has a noun_verb structure, introducing minor inconsistency.

Tool Count5/5

14 tools is well within the ideal 3-15 range. Each tool covers a specific aspect of Canton operations without being overwhelming or too sparse.

Completeness4/5

The tool set covers core operations like party management, asset creation, settlement, and queries. A minor gap is the lack of an explicit archive/delete tool, though it can be done via submit_command.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

15 tool updatesMay 16, 2026

Changedcanton_allocate_party1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedcanton_create_asset1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedcanton_dvp_settle1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedcanton_get_balance1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedcanton_get_events1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedcanton_get_fee_schedule1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedcanton_get_health1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedcanton_get_transaction1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedcanton_list_contracts1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedcanton_list_domains1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedcanton_list_parties1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedcanton_reconnect_synchronizer1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedcanton_submit_command1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedcanton_transfer1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedcanton_upload_dar1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

1 tool updateMay 6, 2026
- Addedcanton_reconnect_synchronizer
14 tool updatesMay 2, 2026
- First observedcanton_allocate_party
- First observedcanton_create_asset
- First observedcanton_dvp_settle
- First observedcanton_get_balance
- First observedcanton_get_events
- First observedcanton_get_fee_schedule
- First observedcanton_get_health
- First observedcanton_get_transaction
- First observedcanton_list_contracts
- First observedcanton_list_domains
- First observedcanton_list_parties
- First observedcanton_submit_command
- First observedcanton_transfer
- First observedcanton_upload_dar

Related MCP Connectors

tenzro-canton
xyz.tenzro
Canton ledger tools over MCP: DAML commands, CIP-56 assets, DvP settlement, party management.
Blockchain Cryptocurrency Web3 & Decentralized Tech
2
modern-treasury A
io.usefulapi
MCP server for Modern Treasury — payment orders, transactions, counterparties and ledgers.
Finance Payments & Billing
172
agentic-commerce A
io.bosonprotocol
MCP server for Boson Protocol — on-chain agentic commerce for physical & digital goods.
Blockchain E-commerce & Retail Autonomous Agents
632
MANDATE Credential Broker B
io.github.projetnanocorp
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Security
111

Related MCP Servers

Concordium MCP Server
Blockchain Web3 & Decentralized Tech
Developerayo
A
license
Not graded
quality
D
maintenance
Concordium mcp-sever for interacting with the concordium chain
Updated a year ago (2025-07-30 23:19 UTC)
2
TypeScript
MIT
canton-mcp
Blockchain Cryptocurrency Web3 & Decentralized Tech
Noves-Inc
A
license
A
quality
C
maintenance
An MCP server that enables AI agents to query the Canton Network for balances, rewards, classified transactions, CC prices, and directory information using natural language.
Updated 3 months ago (2026-06-05 20:37 UTC)
9
68 npm
MIT
UluCoreMCP
Blockchain Cryptocurrency
NautilusOSS
A
license
Not graded
quality
D
maintenance
Low-level blockchain interface MCP server for Algorand and Voi networks, providing account/asset/app inspection, transaction search, block retrieval, TEAL compilation, and transaction simulation.
Updated 6 months ago (2026-03-12 15:20 UTC)
MIT
Shodai Agreements
Blockchain Web3 & Decentralized Tech
CNSLabs
A
license
A
quality
B
maintenance
MCP server for defining, validating, deploying, and operating Shodai machine-readable agreements with EIP-712 permit preparation, signed participant inputs, state reads, and input history.
Updated a month ago (2026-08-23 18:07 UTC)
11
2
Apache 2.0

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources