Tenzro Canton MCP

Tenzro Canton MCP is a remote MCP server published at canton-mcp.tenzro.network. It has been probed 35 times since 9/4/2026. It answered in only 0 of them (0.0%), indicating low availability. Median response time is 654 ms, a delay an agent will notice. Its tool list could not be read; the server is closed to direct calls.

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

UnreachableSpec: unknownVersion: —First probe: 2026-09-04 15:47:51Last probe: 2026-09-07 07:55:38

Agent readability score

Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.

Agent readability score

We could not read this server's tool schema, so an AI evaluation cannot be generated. It will be retried automatically once the server is measured again.

Event narrative

Raw observations

Run	Era	Modern	ms	Legacy	ms	Versions
2026-09-07 07:55:38	Unreachable *	—	1137	—	1136	—
2026-09-07 05:25:31	Unreachable *	—	3304	—	3304	—
2026-09-07 02:57:58	Unreachable *	—	2437	—	2436	—
2026-09-07 00:27:42	Unreachable *	—	2545	—	2543	—
2026-09-06 22:36:06	Unreachable *	—	2490	—	2488	—
2026-09-06 20:44:13	Unreachable *	—	2142	—	2141	—
2026-09-06 18:49:47	Unreachable *	—	616	—	615	—
2026-09-06 16:56:18	Unreachable *	—	822	—	819	—
2026-09-06 15:42:25	Unreachable *	—	3930	—	3927	—
2026-09-06 13:49:02	Unreachable *	—	1346	—	1344	—

Supported versions

—

as declared by server/discover + initialize

Capabilities

—

not readable

Schema score

—

not measurable

Era history

Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.

Era distribution

Unreachable100%

Unreachable07.09 07:55 · Incomplete probe — one leg did not answer, era result not counted

04.09 15:47Measurements: 3507.09 07:55

Unreachable

Response time history

The two probe legs separately: modern server/discover and legacy initialize.

server/discoverinitialize

Event log

Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.

2 hours agoIncomplete probe — one leg did not answer, era result not counted
5 hours agoIncomplete probe — one leg did not answer, era result not counted
7 hours agoIncomplete probe — one leg did not answer, era result not counted
10 hours agoIncomplete probe — one leg did not answer, era result not counted
12 hours agoIncomplete probe — one leg did not answer, era result not counted
14 hours agoIncomplete probe — one leg did not answer, era result not counted
15 hours agoIncomplete probe — one leg did not answer, era result not counted
17 hours agoIncomplete probe — one leg did not answer, era result not counted
19 hours agoIncomplete probe — one leg did not answer, era result not counted
20 hours agoIncomplete probe — one leg did not answer, era result not counted

Get your badge

Add this badge to your README — it updates automatically as measurements change.

Markdown

[![mcpmetrics](https://mcpmetrics.io/badge/network.tenzro/tenzro-canton/era.svg)](https://mcpmetrics.io/servers/network-tenzro-tenzro-canton)

HTML

<a href="https://mcpmetrics.io/servers/network-tenzro-tenzro-canton"><img src="https://mcpmetrics.io/badge/network.tenzro/tenzro-canton/era.svg" alt="mcpmetrics"></a>

Raw observations

You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.