# io.github.UnityNodes/canton-ccpedia (remote · ccpedia.xyz)

Canton Network: CIPs and their on-chain vote outcomes, docs, forum, validator upgrade deadlines.

- Trust score: 63/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `ccpedia.xyz`: 63/100 (this document), [markdown](https://verifymcp.io/servers/unitynodes-canton-ccpedia/ccpedia.md), [page](https://verifymcp.io/servers/unitynodes-canton-ccpedia/ccpedia)

## Channel facts

- Endpoint: `https://ccpedia.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 44/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 10705 tokens (~112/item across 95 items; 88 tools + 7 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http unitynodes-canton-ccpedia https://ccpedia.xyz/mcp
```

### Codex

```toml
[mcp_servers.unitynodes-canton-ccpedia]
url = "https://ccpedia.xyz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "unitynodes-canton-ccpedia": {
      "type": "remote",
      "url": "https://ccpedia.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add unitynodes-canton-ccpedia --url https://ccpedia.xyz/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  unitynodes-canton-ccpedia:
    url: "https://ccpedia.xyz/mcp"
```

### Other

```json
{
  "mcpServers": {
    "unitynodes-canton-ccpedia": {
      "type": "http",
      "url": "https://ccpedia.xyz/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 63, 0)

- [functional] Schema quality: excellent → good
- [functional] New tool “get_validator”

### 2026-08-02 (score 63, +1)

- [security] Tool “list_cips” rewrote its description, which is the text the model reads
- [cosmetic] “list_mailing_threads” reworded the description of “group”

### 2026-07-31 (score 62, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, +2)

- [security] Tool “list_github_discussions” rewrote its description, which is the text the model reads
- [functional] Schema quality: good → excellent

### 2026-07-28 (score 58, 0)

- [security] Tool “get_breaking_changes” rewrote its description, which is the text the model reads
- [security] Tool “get_cip_attachments” rewrote its description, which is the text the model reads
- [security] Tool “get_cip_citations” rewrote its description, which is the text the model reads
- [security] Tool “get_cip_history” rewrote its description, which is the text the model reads
- [security] Tool “get_cip_mentions” rewrote its description, which is the text the model reads
- [security] Tool “get_cip_votes” rewrote its description, which is the text the model reads
- [security] Tool “get_current_versions” rewrote its description, which is the text the model reads
- [security] Tool “get_discussion” rewrote its description, which is the text the model reads
- [security] Tool “get_doc” rewrote its description, which is the text the model reads
- [security] Tool “get_github_discussion” rewrote its description, which is the text the model reads
- [security] Tool “get_kb_drift” rewrote its description, which is the text the model reads
- [security] Tool “get_latest_release” rewrote its description, which is the text the model reads
- [security] Tool “get_mailing_thread” rewrote its description, which is the text the model reads
- [security] Tool “get_network_state” rewrote its description, which is the text the model reads
- [security] Tool “get_network_stats” rewrote its description, which is the text the model reads
- [security] Tool “get_proposals” rewrote its description, which is the text the model reads
- [security] Tool “get_radar” rewrote its description, which is the text the model reads
- [security] Tool “get_recent_changes” rewrote its description, which is the text the model reads
- [security] Tool “get_recurring_issue_fingerprint” rewrote its description, which is the text the model reads
- [security] Tool “get_started_guide” rewrote its description, which is the text the model reads
- [security] Tool “get_token_market” rewrote its description, which is the text the model reads
- [security] Tool “get_trending” rewrote its description, which is the text the model reads
- [security] Tool “list_cips” rewrote its description, which is the text the model reads
- [security] Tool “list_ecosystem_projects” rewrote its description, which is the text the model reads
- [security] Tool “list_github_discussions” rewrote its description, which is the text the model reads
- [security] Tool “list_mailing_threads” rewrote its description, which is the text the model reads
- [security] Tool “list_repos” rewrote its description, which is the text the model reads
- [security] Tool “list_videos” rewrote its description, which is the text the model reads
- [security] Tool “outdated_guidance_detector” rewrote its description, which is the text the model reads
- [security] Tool “search” rewrote its description, which is the text the model reads
- [security] Tool “get_video” rewrote its description, which is the text the model reads
- [security] Tool “get_api_reference” rewrote its description, which is the text the model reads
- [security] Tool “find_similar_projects” rewrote its description, which is the text the model reads
- [security] Tool “full_context” rewrote its description, which is the text the model reads
- [security] Tool “check_deprecation” rewrote its description, which is the text the model reads
- [security] Tool “detect_builder_overlap” rewrote its description, which is the text the model reads
- [security] Tool “find_collaboration_opportunities” rewrote its description, which is the text the model reads
- [functional] Schema quality: excellent → good
- [cosmetic] “search_mailing_list” reworded the description of “query”
- [cosmetic] “search_talks” reworded the description of “query”
- [cosmetic] “find_known_issues” reworded the description of “description”

### 2026-07-27 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (88)

### `search` (~148 tokens)

Keyword/full-text search over the Canton Network knowledge base (CIPs, Canton/Daml/Splice docs, forum, mailing lists, whitepapers, grant proposals, blog, YouTube, GitHub). Canton-specific. Do NOT use for other blockchains, the web, or local files. Use this for exact-term/name lookups; use semantic_search instead for conceptual or 'how does X work' questions, and get_doc to read a full page once you have its id.

Input parameters:

- `limit` (integer): Max results to return (1-50)
- `query` (string, required): Search query
- `type` (string): Restrict results to one source type; "all" searches everything

### `get_cip` (~161 tokens)

Fetch the full markdown body of a single Canton Improvement Proposal (CIP) by its ID (e.g. "CIP-0042", "0042", "PR-0117"). Returns only what the proposal SAYS. To learn whether that CIP was approved, enforced, or acted on ON CHAIN, use get_cip_vote_outcome instead: reading the proposal text does not tell you its on-chain fate. For the status timeline use get_cip_history; to browse or filter multiple CIPs use list_cips. Canton/Daml/Splice ecosystem only, not Cardano or other CIP schemes.

Input parameters:

- `id` (string, required): CIP ID: "0001", "CIP-0042", or "PR-0117"

### `list_cips` (~155 tokens)

Browse Canton Improvement Proposals (CIPs), optionally filtered by status (Draft, Early Draft, In Review, Proposed, Approved, Active, Final, Withdrawn, Rejected, Replaced, Obsolete) and type (e.g. "Standards Track"). Returns a metadata list (id, title, status, type, author). Not full text. Use to discover or enumerate CIPs when you don't have a specific ID; use get_cip to read one. Canton/Daml/Splice governance only. Not Cardano or other 'CIP' schemes.

Input parameters:

- `limit` (integer)
- `status` (string)
- `type` (string): Type filter, e.g. "Standards Track"

### `get_discussion` (~114 tokens)

Get a single thread from the official Canton Network community forum (Discourse at forum-style discussions on ccpedia.xyz) by numeric topic id: title, category, view/post counts, and the first ~15 posts. Canton-only, served from CCPEDIA's cached forum index. This is the WEB FORUM. For GitHub Discussions use get_github_discussion, for sync.global mailing-list threads use get_mailing_thread. Get the id from search results or trending.

Input parameters:

- `id` (integer, required): Forum topic ID

### `get_whitepaper` (~89 tokens)

Get the full extracted text of a specific Canton Network whitepaper by slug (e.g. 'canton-network-whitepaper'): title, tag, page count, PDF link, and body text (up to ~50k chars). Canton-only. Call list_whitepapers first to obtain valid slugs.

Input parameters:

- `slug` (string, required): Whitepaper slug, e.g. "canton-network-whitepaper"

### `list_whitepapers` (~54 tokens)

List every Canton Network whitepaper indexed by CCPEDIA, returning slug, title, description, tag and page count (metadata only, no body). Use the returned slug with get_whitepaper to fetch full content. Canton-only.

### `get_trending` (~76 tokens)

Get this week's most popular/trending Canton Network content (CIPs, forum threads, docs, blog, etc.) ranked by an engagement score. Canton-specific. Not general crypto/social/news trends. Use for 'what's hot/popular on Canton right now'; use get_recent_changes instead for a chronological 'what changed recently' feed.

### `get_radar` (~92 tokens)

Get the Canton Network Radar, CCPEDIA's curated feed of time-sensitive ecosystem alerts: breaking changes, upgrade deadlines, protocol migrations and required validator actions, each with deadline, affected components and source link. Filter by level (critical/important/ecosystem/all). Canton-only. Use when a user asks what's changing, what's about to break, or what deadlines are approaching on Canton.

Input parameters:

- `level` (string)

### `get_proposals` (~104 tokens)

List Canton Network Dev Fund grant proposals: community funding requests tracked on GitHub. Filterable by state (open/closed/all). Use for 'what grants/funding requests exist' questions. NOT the same as Canton Improvement Proposals (CIPs): those are governance specs (use list_cips / get_cip). Returns number, title, state, author, and board status. Canton ecosystem only.

Input parameters:

- `limit` (integer)
- `state` (string)

### `get_doc` (~103 tokens)

Fetch the FULL text of one indexed Canton-ecosystem documentation page (Canton/Daml/Splice and integrated partner docs) by its numeric id. Canton-specific. Use this AFTER search or semantic_search returns a doc id, to read complete commands, flags, and full sections a search snippet truncates. Requires an id. Not a discovery tool; use search/semantic_search first.

Input parameters:

- `id` (integer, required): Doc page ID (from search/semantic_search results)

### `get_cip_history` (~121 tokens)

Get the status-transition timeline of a single Canton Improvement Proposal (CIP): each dated from->to change (e.g. Draft->Review->Final). Use for 'how/when did CIP-X move through governance' questions. Returns history only, not the proposal body (get_cip) or vote tallies (get_cip_votes). Canton ecosystem only. Not Cardano or other 'CIP' schemes.

Input parameters:

- `id` (string, required): CIP ID: "0001", "CIP-0042", or "PR-0117"

### `get_cip_attachments` (~108 tokens)

List file/PDF attachments linked to a single Canton Improvement Proposal (CIP): supporting docs and signed-vote-record PDFs, with filenames and URLs. Use to find downloadable artifacts for a CIP. For the parsed who-voted-how breakdown use get_cip_votes; for the proposal text use get_cip. Canton ecosystem only. Not Cardano or other 'CIP' schemes.

Input parameters:

- `id` (string, required): CIP ID: "0001", "CIP-0042"

### `get_cip_mentions` (~174 tokens)

Find every place that references a given Canton Improvement Proposal (CIP): forum threads, mailing-list posts, blog articles, Dev Fund grant proposals, and sibling CIPs that require/cite it. A reverse-reference (backlink) lookup: use for 'who is discussing CIP-X and where' / impact questions. Returns aggregated per-source counts, not individual items. For individual forum posts/mailing messages and CCPEDIA's finer per-message mailing-list granularity, use get_cip_citations instead. Not for the proposal's own text (get_cip) or its vote records (get_cip_votes). Canton ecosystem only. Not Cardano or other 'CIP' schemes.

Input parameters:

- `id` (string, required): CIP ID: "0001", "CIP-0042", or "PR-0117"

### `get_recent_changes` (~111 tokens)

Get a chronological (newest-first) feed of recent Canton Network activity: CIP status changes, new grant proposals, new forum threads, blog posts, GitHub releases, and radar items, merged into one time-ordered stream (default last 7 days). Canton-specific. Not a git/repo changelog. Use for 'what changed/happened on Canton recently'; use get_trending instead for popularity-ranked 'what's hot'.

Input parameters:

- `days` (integer)
- `limit` (integer)

### `get_network_stats` (~107 tokens)

Get CCPEDIA's CONTENT-CATALOG metrics: how many Canton items CCPEDIA has indexed. Counts of CIPs (total/in-review/final), forum topics & posts, GitHub issues/PRs, dev-fund proposals, docs pages, videos, blog posts, mailing threads, and radar items. This is CCPEDIA coverage/inventory, NOT live Canton on-chain stats. For on-chain validators/rounds use get_network_state, for price/TVL use get_token_market.

### `get_token_market` (~102 tokens)

Get the latest cached market snapshot for CANTON COIN (CC) ONLY: USD price, 24h change, market cap, 24h volume, total Canton DeFi TVL, and per-protocol TVL on Canton. Canton-specific. Cannot price BTC, ETH or any other asset (use a general crypto-price MCP like CoinGecko for those). Snapshot from CCPEDIA's sync (captured_at timestamp), not a live exchange feed.

### `list_ecosystem_projects` (~139 tokens)

List Canton Network ecosystem projects (DeFi protocols, wallets, custody, infrastructure, NaaS, etc.) from the curated canton.wiki catalog. Filter by category or free-text query. Returns name, category, description and URL: a static directory of who-builds-on-Canton, not live on-chain/TVL data (use get_token_market for live DeFi TVL). Canton-only.

Input parameters:

- `category` (string): Filter by category (e.g. "DeFi", "Wallets", "NaaS")
- `limit` (integer)
- `query` (string): Search in title/description/tags

### `get_network_state` (~100 tokens)

Get the latest Canton Network ON-CHAIN state snapshot from the public Scan API (api.cantonnodes.com): Super Validator list & count, voting threshold, sequencer count, latest mining round, featured-apps count, and cumulative app/validator rewards in CC. Canton-only, cached snapshot (captured_at). This is live network telemetry. NOT CCPEDIA content counts (get_network_stats) and NOT price/TVL (get_token_market).

### `list_repos` (~96 tokens)

List the Canton Network GitHub repositories that CCPEDIA has indexed (Canton org repos such as canton-foundation and Daml/Splice, excluding the dev-fund proposals repo), with the count of issues+PRs indexed per repo. CANTON-ONLY and read from CCPEDIA's cache. This is NOT a live GitHub API and does NOT list the user's own repos (use a GitHub MCP for that).

### `list_github_discussions` (~167 tokens)

List GitHub Discussions from Canton Network repositories (currently canton-foundation/docs) cached by CCPEDIA, sorted by upvotes then recency. Filter by repo or category. CANTON-ONLY and read from CCPEDIA's cache, NOT the live GitHub API or the user's own repos (use a GitHub MCP for those). This is GitHub Discussions: distinct from the Canton web forum (get_discussion) and the sync.global mailing lists (list_mailing_threads). Use get_github_discussion for full body + comments.

Input parameters:

- `category` (string): Filter by Discussions category, e.g. "Q&A", "Ideas"
- `limit` (integer)
- `repo` (string): Filter by repo, e.g. "canton-foundation/docs"

### `get_github_discussion` (~125 tokens)

Get the full body and comments of a single GitHub Discussion from a Canton Network repo (e.g. canton-foundation/docs), by its GitHub GraphQL node id (from list_github_discussions). CANTON-ONLY, read from CCPEDIA's cache. Not the live GitHub API. This is GitHub Discussions, distinct from the Canton web forum (get_discussion) and mailing lists (get_mailing_thread).

Input parameters:

- `id` (string, required): GitHub GraphQL node ID, e.g. "D_kwDOMNgu5s4AY..."

### `get_video` (~128 tokens)

Get a Canton Network video that CCPEDIA has cached (curated channels: Canton Network, Digital Asset, Sync Insights, Canton Foundation, Daml) by its YouTube id: title, channel, publish date, description and full transcript text if stored. CANTON-ONLY and limited to videos already in CCPEDIA's index. Does NOT fetch arbitrary YouTube videos (use a dedicated YouTube tool for that). Obtain ids from list_videos or search.

Input parameters:

- `id` (string, required): YouTube video id, e.g. "dQw4w9WgXcQ"

### `list_videos` (~206 tokens)

List Canton Network videos cached in CCPEDIA, filtered by channel (Canton Network, Digital Asset, Sync Insights, Canton Foundation, Daml), publish date (since), and transcript availability. CANTON-ONLY corpus. These are curated Canton ecosystem videos, not general YouTube. Returns metadata only (id, title, channel, date); call get_video with an id for the transcript.

Input parameters:

- `channel` (string): Channel name filter, e.g. "Canton Network", "Digital Asset", "Sync Insights", "Canton Foundation", "Daml". Case-insensitive substring.
- `has_transcript` (boolean): If true, only return videos with a stored transcript. If false, only those still missing one. Omit for both.
- `limit` (integer)
- `offset` (integer)
- `since` (string): Earliest published_at (ISO date, e.g. "2026-01-01"). Default: no lower bound.

### `get_validator_fleet` (~170 tokens)

Where do you stand versus other Canton operators on your Splice version? Reports the whole DSO-approved validator fleet as a version distribution; call with no version to see the whole distribution, or pass your own version to get your exact position (early, typical, or dangerously behind most nodes). CCPEDIA-unique: no other public source publishes this. IMPORTANT: versions are self-reported by each operator in its license metadata, not observed, and many reports are months stale; the tool returns how many are fresh so you can qualify the answer. For the pass/fail rule (are you above the required minimum) use get_upgrade_status. Canton ecosystem only.

Input parameters:

- `version` (string): Your Splice version, e.g. "0.6.9", to locate it in the distribution.

### `get_validator` (~205 tokens)

Look up an individual Canton validator node in the DSO registry by name or party id: its sponsor, self-reported Splice version and how stale that report is, when it was last active, the round range it has been earning over, and how many reward coupons it has missed. CCPEDIA-unique: derived from the DSO validator licenses on the public Scan API. Use for "is node X still live", "who sponsors X", "how reliable is X". For the version distribution across the whole fleet use get_validator_fleet; for whether a version passes the MainNet minimum use get_upgrade_status; for Super Validator GOVERNANCE voting records use list_votes_by_sv, which is a different population. Canton ecosystem only.

Input parameters:

- `limit` (integer): Maximum matches to return (default 10, max 50).
- `name` (string, required): Validator name or party id, whole or partial, e.g. "GSF-validator-2" or "MPCH".

### `get_upcoming_deadlines` (~189 tokens)

Canton operational deadlines coming up: scheduled upgrades, minimum-version raises, topology freezes and Logical Synchronizer Upgrades, per network. Use for "what do I have to do in the next N days" on DevNet, TestNet or MainNet. Events whose network could not be attributed are excluded rather than guessed, because a wrong deadline is worse than a missing one. A subscribable calendar of the same data is at https://ccpedia.xyz/calendar. For a verdict on your specific version use get_upgrade_status; for the full historical schedule use get_sv_schedule. Canton ecosystem only.

Input parameters:

- `days` (integer): How far ahead to look, in days. Default 30.
- `environment` (string): "MainNet", "TestNet" or "DevNet". Omit for all networks.
- `validator_only` (boolean): Only events that require a validator operator to act.

### `list_governance_votes` (~241 tokens)

List Canton Network on-chain DSO governance vote requests and their outcomes, from the ledger itself. Covers Featured App rights being granted or revoked, Super Validator reward-weight changes, SV offboarding, and AmuletRules/DsoRules config changes. CCPEDIA-unique: no other public source exposes this joined to the CIP corpus. Use for 'what has the DSO decided recently', 'which apps got Featured App status', 'what got rejected'. For one CIP's fate use get_cip_vote_outcome; for one Super Validator's record use list_votes_by_sv. Canton ecosystem only.

Input parameters:

- `action` (string): Filter by action, e.g. "SRARC_GrantFeaturedAppRight", "SRARC_RevokeFeaturedAppRight", "SRARC_UpdateSvRewardWeight", "SRARC_OffboardSv".
- `limit` (integer): Max rows (default 20).
- `outcome` (string): Filter by outcome: "VRO_Accepted", "VRO_Rejected", "VRO_Expired".
- `status` (string): "open" for votes still in flight, "closed" for decided ones.

### `get_governance_vote` (~109 tokens)

Get the full detail of one Canton on-chain DSO governance vote request: the proposed action, the requester's stated reason, every Super Validator's individual vote with their own written reason, who abstained, the outcome and the date it took effect. Use after list_governance_votes when a specific decision matters. Canton ecosystem only.

Input parameters:

- `tracking_cid` (string, required): The vote request tracking contract id, or a unique prefix of it, as returned by list_governance_votes.

### `list_votes_by_sv` (~137 tokens)

Get the on-chain voting record of Canton Super Validators: how many DSO governance votes each has cast, how often they voted for or against, how often they abstained, and the span of their participation. Use for 'how does Tradeweb vote', 'which SVs abstain most', 'who is most active in governance'. CCPEDIA-unique: derived from the full ledger vote history. Canton ecosystem only.

Input parameters:

- `sv_name` (string): Super Validator short name, e.g. "Tradeweb-Markets-1", "Digital-Asset-1", "Cumberland-1". Omit for all of them.

### `get_cip_vote_outcome` (~150 tokens)

Find out whether a Canton Improvement Proposal (CIP) was actually acted on ON CHAIN, and how. Returns every DSO governance vote request whose text cites this CIP, with outcomes and dates. This answers 'was it decided', which the mailing-list tools cannot: get_cip_votes reads the discussion on the cip-vote list, this reads the ledger. Example: CIP-0116 (Featured App Locking) is cited in dozens of requests that paused apps for non-compliance. Canton ecosystem only, not Cardano or other CIP schemes.

Input parameters:

- `cip_id` (string, required): CIP id, e.g. "CIP-0116", "116", "0116".

### `get_cip_votes` (~137 tokens)

Get the formal vote tally (in-favor / against / abstain, one entry per recorded vote) for a specific Canton Improvement Proposal (CIP), sourced from the Canton cip-vote mailing list. Use for 'who voted how' / approval-trail verification on Governance-type CIPs. Not the attachment PDFs (get_cip_attachments) or status timeline (get_cip_history). Canton ecosystem only. Not Cardano or other 'CIP' schemes.

Input parameters:

- `cip_id` (string, required): CIP id, e.g. "0117", "0118", or "CIP-0117". Numeric form preferred.

### `list_mailing_threads` (~177 tokens)

List threads from the Canton Network governance mailing lists (lists.sync.global groups: cip-discuss, cip-vote, cip-announce, globalSyncForum, grants-discuss, validator-announce). Filter by group, CIP number, or date. Canton-only. This is the EMAIL/mailing-list channel. Distinct from the web forum (get_discussion) and GitHub Discussions (list_github_discussions). Returns thread metadata only; use get_mailing_thread for message bodies.

Input parameters:

- `cip_id` (string): CIP number filter, e.g. "0117". Returns only threads tagged with this CIP.
- `group` (string): Restrict to one of the eight indexed groups.
- `limit` (integer)
- `offset` (integer)
- `since` (string): Earliest last_post_at ISO date.

### `get_mailing_thread` (~102 tokens)

Get every message (oldest first) in a specific Canton Network governance mailing-list thread on lists.sync.global (cip-discuss, cip-vote, grants-discuss, etc.). Canton-only. Pass the thread id from list_mailing_threads. This is the email/mailing-list channel. Not the web forum (get_discussion) or GitHub Discussions.

Input parameters:

- `id` (string, required): Thread id, e.g. "cip-discuss-12345".

### `get_foundation_info` (~123 tokens)

Retrieve official Canton Foundation pages (canton.foundation): team and board bios, working groups, membership process, grants program. Free-text topic search over CCPEDIA's index of the canton.foundation site, returning matched-page snippets (not the curated knowledge base). Canton-only. Use when a user asks about Foundation people, governance structure, or member/grant processes.

Input parameters:

- `limit` (integer)
- `topic` (string, required): Free-text topic, e.g. "team", "executive director", "working groups", "membership", "grants", "board".

### `semantic_search` (~204 tokens)

PRIMARY tool for open-ended questions: how / why / what-is, troubleshooting a symptom ("why is my balance zero", "how do I fix X"), and locating config or setup steps. Conceptual/meaning-based search over the full Canton corpus (CIPs, docs, forum, mailing lists, proposals, blog, releases, ecosystem, foundation KB, YouTube) using vector+FTS hybrid retrieval with reranking. Canton-specific. Use this FIRST for anything a specific tool does not clearly own; the narrow curated tools (get_faq, find_known_issues, diagnose_error) cover only small hand-picked sets or need a literal error string, so prefer semantic_search for real how/why/config questions. Then call get_doc with a returned id to read the full source page.

Input parameters:

- `limit` (integer)
- `query` (string, required): Free-form question or phrase.
- `source_types` (array): Restrict to these source types. Omit for all.

### `check_deprecation` (~117 tokens)

Check whether a specific Canton/Daml toolchain item (CLI, SDK package, or command: e.g. daml-assistant, Navigator, dpm) is deprecated. Canton-specific. Not a general npm/pip deprecation checker. ALWAYS call before recommending any Canton tool or package to a developer. Returns DEPRECATED (with replacement), CURRENT, or NOT_FOUND.

Input parameters:

- `name` (string, required): Tool/package/command to check, e.g. "daml-assistant", "Navigator", "dpm", "canton sandbox".

### `get_started_guide` (~138 tokens)

Generate a personalized Canton Network developer onboarding/quickstart path. Use when a developer asks how to start building, build a dApp, or develop on Canton specifically. Canton-only. Do not use for onboarding to other chains or tools. Ask the user's background first (EVM, Solana, Sui/Move, Web, Enterprise, or New to Blockchain). Prefer this over 'search' for 'how to build / get started on Canton'; use get_faq for a single specific gotcha and get_api_reference for API details.

Input parameters:

- `background` (string, required): Developer's primary background. Ask the user to select this before proceeding.

### `get_faq` (~184 tokens)

Look up answers in the Canton Network developer FAQ (Canton Foundation curated, hackathon-tested): Canton/Daml installation, party creation, Daml contracts, Ledger/Scan APIs, testnet deployment, Canton Coin/token standard, common gotchas. Returns the 3 NEAREST FAQ entries, which may not exactly match. Canton-specific, do NOT use for other blockchains or general/non-Canton questions. If none of the 3 directly answers the question, or the user needs specific config values, commands, or parameters, use semantic_search over the full docs (then get_doc) rather than answering from a near-miss. For a full onboarding path use get_started_guide; for API endpoint details use get_api_reference.

Input parameters:

- `question` (string, required): Developer's question, e.g. "how do I install", "create party", "deploy to testnet".

### `get_api_reference` (~106 tokens)

Get a structured reference (ports, endpoints, services, links) for one specific Canton Network API: JSON Ledger API, gRPC Ledger API, Scan API, Validator API, Token Standard APIs, Admin API, or Splice HTTP. Canton-specific. Not for GitHub, REST, or non-Canton APIs. Use when the user names one of these Canton APIs; use search/semantic_search for broader doc lookups.

Input parameters:

- `api` (string, required): Which API to look up.

### `compare_to_evm` (~122 tokens)

Map one Ethereum/EVM concept (e.g. smart contract, wallet, gas, ERC20, Hardhat, ABI) to its Canton Network equivalent, for developers migrating from Solidity/EVM to Canton. Canton-specific (target is always Canton). Use for single concept-to-concept translations; use get_started_guide for a full EVM-to-Canton learning path.

Input parameters:

- `concept` (string, required): EVM concept, e.g. "smart contract", "wallet", "gas", "ERC20", "Hardhat", "Remix", "ABI".

### `migrate_lookup` (~133 tokens)

Look up the modern replacement for a deprecated Daml/Canton CLI command, npm package, or tool (e.g. "daml start", "@daml/ledger", "Navigator", "Daml Triggers", "splice-wallet-payments subscription"). Returns the replacement, since-version, install instructions when applicable, and a migration note. Canton/Daml/Splice ecosystem only. Use when a user mentions a specific deprecated symbol; use list_deprecations to enumerate all known pairs or browse by category.

Input parameters:

- `query` (string, required): The deprecated command, package, or tool name to look up. Best-match search.

### `list_deprecations` (~83 tokens)

List all known deprecated Daml/Canton CLI commands, packages, and tools with their modern replacements. Returns a compact table you can scan, optionally filtered by category (cli, package, tool, api, workflow). Canton/Daml/Splice only. Use this to enumerate or browse; use migrate_lookup for a specific name.

Input parameters:

- `category` (string)

### `get_current_versions` (~175 tokens)

Get the freshest Canton SDK, Splice, Daml, and DPM versions ALL AT ONCE, plus per-network Splice deployment status (DevNet / TestNet / MainNet) and any upcoming synchronizer-upgrade windows. Derived live on every call from two CCPEDIA-only joins: github_releases (latest stable tag per repo) + mailing_messages (validator-announce list). This is fresher than the Foundation Build-on-Canton KB snapshot, which can lag by weeks. Use this when a user asks "what version should I target?", "is Splice X.Y.Z still current?", "what is on MainNet?". Anything time-sensitive about Canton/Splice/Daml/DPM versioning across MULTIPLE packages. If the user names ONE specific package and wants its release notes, use get_latest_release instead.

### `get_cip_citations` (~306 tokens)

Comprehensive citation graph for a Canton Improvement Proposal (CIP): every place across CCPEDIA's corpus that references CIP-N. Returns per-source counts AND samples for: sibling CIPs (declared `requires:` or content-mentions), individual forum posts (not just topic count), individual mailing-list messages (cip-vote / cip-discuss / grants-discuss / validator-announce), GitHub items (issues + PRs + dev-fund proposals across all indexed Canton repos), blog posts (third-party coverage), and YouTube videos (transcript matches). CCPEDIA-unique: joins through our parsed `mailing_messages.cip_id` column give per-message granularity no other source has. Use when an agent needs 'who is referencing CIP-X and where' / impact analysis, and a specific CIP id is already known. For the proposal's own text use get_cip, for its votes use get_cip_votes, for the legacy aggregated counts use get_cip_mentions. For a general topic or feature name with NO known CIP id. E.g. 'featured app locking' rather than 'CIP-0116'. Use full_context instead, which searches by free text across the whole corpus rather than requiring an id. Canton/Daml/Splice ecosystem only.

Input parameters:

- `cip_id` (string, required): CIP id, e.g. "CIP-0056", "0056", "PR-0117". Padded or unpadded both accepted.

### `get_kb_drift` (~189 tokens)

Report where the Foundation Build-on-Canton KB snapshot (which CCPEDIA syncs daily from github.com/canton-network-devs/Build-on-Canton-MCP) diverges from CCPEDIA's live signals (github_releases, mailing_messages). Returns each drifted (category, key) with the KB value, the live value derived right now, the drift age in days, and severity (info | warn | stale). Use this when a user or another agent quotes a Canton SDK / Splice / DPM / Daml version from foundation_kb and you need to confirm whether it is still current. CCPEDIA-specific transparency layer: no other Canton MCP server exposes this kind of cross-source quality audit. Canton/Daml/Splice ecosystem only.

Input parameters:

- `refresh` (boolean): If true, re-run the validator before returning the report. Default false uses the most recent stored findings.

### `diagnose_error` (~170 tokens)

Paste a Canton/Daml/Splice ERROR MESSAGE, stack trace, or error code and get the most likely resolved fixes from CCPEDIA history: forum threads where the same error was discussed, related GitHub issues, and the SDK version range it appeared in. Needs a literal error string or code (e.g. TOPOLOGY_TOO_MANY_PENDING_TOPOLOGY_TRANSACTIONS, ValidatorLicense); do NOT use it for symptom descriptions with no error text (e.g. "my balance is zero"), use semantic_search for those. Canton-specific. Returns top 3 matches each from forum and github.

Input parameters:

- `error_text` (string, required): Error message, stack trace, or status code. Longer/more distinctive text returns better matches.
- `limit` (integer): Max matches per source (default 3).

### `get_breaking_changes` (~191 tokens)

Compare two Canton/Daml/Splice SDK versions and return the list of changes between them: release notes from github_releases plus any forum/GitHub reports near the release window. Canton-specific. Use when a developer is planning an upgrade and asks "what breaks moving from X to Y?". Pass version strings as they appear in github_releases tags (with or without the leading "v").

Input parameters:

- `from_sdk` (string, required): Origin version, e.g. "0.5.0" or "v3.4.0".
- `repo` (string): Optional repo hint: "canton", "splice" (alias for decentralized-canton-sync), "daml", or a full owner/name. Auto-inferred from version shape when omitted.
- `to_sdk` (string, required): Target version, e.g. "0.6.10" or "v3.5.6".

### `get_recurring_issue_fingerprint` (~134 tokens)

Identify error patterns that recur across multiple Canton SDK or Splice release windows: structural bugs the ecosystem keeps hitting versus one-off regressions. Returns the top keywords/error codes mentioned in forum_posts that span at least 3 distinct months over the last 18 months. Canton/Daml/Splice ecosystem only. Useful for triage prioritisation and for choosing what to add to a runbook.

Input parameters:

- `min_months` (integer): A keyword must appear in this many distinct months to count as recurring (default 3).
- `window_months` (integer): Look-back window in months (default 18).

### `list_featured_apps` (~131 tokens)

List Canton Network Featured Apps from the live Scan-API-sourced catalogue. Filter by category (when known) and choose ordering. Canton-specific. Use for "what dApps are live on Canton?" or to discover providers offering a particular service. Returns name, provider/app_id, category, last_activity, url.

Input parameters:

- `category` (string): Filter by category, e.g. "Validator", "DeFi", "Tokenized Assets" (case-insensitive substring match).
- `limit` (integer): Max rows (default 25).
- `sort` (string): Sort key (default: recent).

### `get_app_metrics` (~98 tokens)

Fetch metrics for one specific Featured App by its app_id (contract id from the Scan API). Returns name, category, TVL, 24h volume, user count, last activity, and any cross-referenced ecosystem_projects metadata. Canton-specific. TVL / volume / users may be null when only the Scan API source is available.

Input parameters:

- `app_id` (string, required): Featured-app contract id (long hex string from list_featured_apps).

### `find_apps_by_pattern` (~85 tokens)

Pattern-search the Featured Apps catalogue by free-text query across name, category, and description. Returns the best matches in name+category, falling back to description. Canton-specific.

Input parameters:

- `limit` (integer): Max rows (default 10).
- `pattern` (string, required): Free text, e.g. "AMM", "wallet", "DeFi vault", "validator".

### `get_upgrade_status` (~154 tokens)

Upgrade Copilot for a Canton validator: given the Splice version a node runs and its network, report whether it is below the minimum in force, how many releases behind, the next topology freeze and LSU (with UTC time), the minimum .dar package versions, and the breaking changes between the running version and the target. Canton-specific. Use when an operator asks "am I safe to skip this week?", "what breaks if I upgrade?", or "when is my next deadline?".

Input parameters:

- `environment` (string, required): Which network the node runs on.
- `version` (string): Splice version the node currently runs, e.g. "0.6.9". Omit to get the schedule without a verdict.

### `get_sv_schedule` (~122 tokens)

Show the Super Validator operations schedule from the Canton Foundation's sv-cal.canton.foundation feed: planned releases, deploys, upgrades, governance windows, freezes. Filter by environment. Canton-specific. Use when an operator asks "what is happening on MainNet next?" or "when is the next Splice cut?".

Input parameters:

- `environment` (string): Restrict to one environment. Omit for all.
- `limit` (integer): Max rows (default 20).
- `upcoming_only` (boolean): If true (default), only events with start_at >= today.

### `get_upcoming_operations` (~64 tokens)

Convenience wrapper: SV operations in the next N days, all environments, all operation types. Canton-specific. Quick "what should I be ready for this week?" answer for validator/SV ops.

Input parameters:

- `days` (integer, required): Days ahead to look (1-180).

### `get_recent_deployments` (~75 tokens)

Recent completed SV deployments/releases from sv_operations_calendar (operation_type in deploy|release|upgrade), cross-referenced with github_releases when the title names a SemVer-looking tag. Canton-specific. Use to answer "what shipped on MainNet recently?".

Input parameters:

- `limit` (integer): Max rows (default 10).

### `detect_cip_dependency_chain` (~129 tokens)

Walk the CIP `requires:` graph from a starting CIP or PR draft. Returns the full chain of prerequisites that must reach `Final` before the starting proposal becomes implementable, with each prerequisite's current status. Accepts both approved CIPs ("CIP-0112", "0112") and dev-fund PR drafts ("PR-203"). Canton governance only. Use when planning around a CIP that hasn't shipped yet.

Input parameters:

- `cip_id` (string, required): Starting CIP or PR id, e.g. "0112", "CIP-0112", or "PR-203".

### `compare_governance_outcomes` (~84 tokens)

Aggregate governance throughput over a window: CIPs that changed status (approved / rejected / advanced), counts of cip-vote and cip-discuss mailing activity, and dev-fund proposals merged or closed. Canton-specific. Use to summarise "what governance has shipped this quarter?".

Input parameters:

- `window_days` (integer, required): Window in days, 7-365.

### `get_sdk_changelog` (~108 tokens)

Fetch the release-notes body for one SDK version across canton / daml / dpm / decentralized-canton-sync (Splice). Canton-specific. Returns the rendered release body with a link to the GitHub release.

Input parameters:

- `repo` (string): Optional repo hint: canton, daml, dpm, splice.
- `version` (string, required): Version tag, e.g. "3.5.6", "v3.5.6", "0.6.10".

### `search_community` (~82 tokens)

One-call semantic-style search across CCPEDIA's community sources at once: forum, mailing lists, blog, and GitHub discussions. Canton-specific. Use when you want to scan everything written by humans (not docs/code) for a topic.

Input parameters:

- `limit` (integer): Max hits per source (default 5).
- `query` (string, required): Free-text query.

### `search_github_issues` (~97 tokens)

Full-text search across CCPEDIA's indexed GitHub issues (15+ Canton repos). Canton ecosystem only. Use to find prior reports / open bugs / requested features. For PRs use search_github (broader) or list_proposals.

Input parameters:

- `limit` (integer): Max rows (default 10).
- `query` (string, required): Free-text query.
- `state` (string): Issue state filter (default: all).

### `search_talks` (~70 tokens)

Search CCPEDIA's indexed Canton talks/videos (YouTube transcripts). Canton-specific. Returns matches across title + transcript with a short snippet around the hit.

Input parameters:

- `limit` (integer): Max rows (default 5).
- `query` (string, required): Free-text query. Appears in title or transcript.

### `find_known_issues` (~135 tokens)

Surface known UNRESOLVED problems matching a free-text description: forum threads with zero replies but high views, plus open GitHub issues. Answers "is anyone else hitting this?". Canton-specific. Does NOT return fixes, solutions, config, or how-to steps, and returns nothing when no open issue matches; for "how do I fix / configure / why does X happen" use semantic_search (then get_doc) instead.

Input parameters:

- `description` (string, required): What you're seeing. Short prose, not a stack trace (for that use diagnose_error).
- `limit` (integer): Max rows per source (default 5).

### `find_cip_for_feature` (~70 tokens)

Given a Canton feature or capability description, find the matching CIP(s) by searching titles and bodies. Canton-specific. Use to answer "is there a CIP for X?".

Input parameters:

- `feature` (string, required): Feature description, e.g. "wallet abstraction", "token standard", "validator staking".

### `get_cip_implementation_status` (~78 tokens)

For one CIP, report whether code/grants are tracking the proposal: linked dev-fund PRs, related ecosystem projects, status transitions. Canton governance. Use after find_cip_for_feature to gauge readiness.

Input parameters:

- `cip_number` (string, required): CIP id, e.g. "0112", "CIP-0112".

### `get_latest_release` (~138 tokens)

Get the single latest release (version tag, publish date, and GitHub release-notes link) for ONE NAMED Canton-ecosystem package: canton, daml, dpm, or splice. Canton-specific. Requires a package name as input. Use when the user names a specific package ("what's the latest daml release", "latest canton version"); use get_current_versions instead for a cross-package snapshot of all four at once or MainNet/TestNet deployment status.

Input parameters:

- `package` (string, required): Repo or package name: "canton", "daml", "dpm", "splice", or a full owner/repo.

### `search_release_notes` (~63 tokens)

Search across release-notes bodies of all indexed Canton repos for a feature/keyword. Canton-specific. Use to find which release first mentioned X.

Input parameters:

- `feature` (string, required): Feature keyword, e.g. "logical synchronizer", "topology", "wallet kernel".

### `find_security_patches` (~55 tokens)

Surface release notes likely to contain security or CVE fixes. Canton-specific. Heuristic: matches release bodies containing security / CVE / vulnerability / patch keywords.

Input parameters:

- `limit` (integer): Max rows (default 10).

### `get_npm_packages` (~59 tokens)

List the indexed Canton/Daml npm packages (sdk_versions registry=npm) optionally filtered by name. Canton-specific.

Input parameters:

- `limit` (integer): Max packages (default 25).
- `query` (string): Optional substring filter on package name.

### `find_similar_projects` (~95 tokens)

Find Canton ecosystem projects most similar to a free-text description by matching across title + category + description + tags: searches only the live ecosystem directory. Canton-specific. Useful before proposing a project to check overlap; to also check pending/past Dev Fund proposals for the same idea, use detect_builder_overlap instead.

Input parameters:

- `description` (string, required): Project description / idea.
- `limit` (integer): Max rows (default 10).

### `search_mailing_list` (~91 tokens)

Search across CCPEDIA's indexed Canton mailing-list archives (cip-discuss, cip-vote, grants-discuss, validator-announce, etc). Canton-specific.

Input parameters:

- `group` (string): Optional group_slug filter, e.g. "cip-discuss".
- `limit` (integer): Max rows (default 10).
- `query` (string, required): Free-text query. Appears in subject or body.

### `find_maintainer_guidance` (~71 tokens)

Surface forum/mailing posts authored by top-volume Canton contributors (likely maintainers) on a topic. Canton-specific. Use when you want to weight expert voices over the general forum.

Input parameters:

- `topic` (string, required): Topic keyword, e.g. "topology", "wallet", "DAR upload".

### `get_issue_status` (~73 tokens)

Look up one GitHub issue or PR by repo + number. Canton/Daml/Splice repos only.

Input parameters:

- `number` (integer, required): Issue or PR number.
- `repo` (string, required): Repo, e.g. "canton-foundation/canton-dev-fund" or shorthand "canton-dev-fund".

### `find_code_examples` (~69 tokens)

Find Canton/Daml code snippets in forum posts on a topic. Filters forum_posts where the rendered HTML contains `<pre>` or `<code>` blocks AND matches the topic keyword. Canton-specific.

Input parameters:

- `limit` (integer): Max rows (default 5).
- `topic` (string, required): Topic keyword.

### `get_funding_landscape` (~77 tokens)

Overview of the Canton Dev Fund: counts of proposals by state and label, top categories, and recent activity. Canton-specific. Use to gauge whether a category is over- or under-funded before proposing.

Input parameters:

- `category` (string): Optional label filter, e.g. "daml-tooling", "node-deployment-operations".

### `get_proposal_milestones` (~59 tokens)

For one Canton Dev Fund proposal PR, list any related milestone tracking issues (issues whose body or title references the PR number). Canton-specific.

Input parameters:

- `pr_number` (integer, required): PR number in canton-foundation/canton-dev-fund.

### `get_ecosystem_gaps` (~71 tokens)

Surface ecosystem gaps: high-view forum threads with zero replies (unanswered demand), recent unanswered mailing threads, and Dev Fund categories with few accepted proposals. Canton-specific. Use to find "where the ecosystem needs help".

Input parameters:

- `limit` (integer): Max rows per gap type (default 5).

### `detect_builder_overlap` (~88 tokens)

Given a project/proposal idea, find existing Canton ecosystem projects + dev-fund proposals that look similar: across BOTH the canton-dev-fund proposals corpus AND ecosystem_projects. Broader than find_similar_projects, which only searches the live ecosystem directory. Canton-specific. Cuts manual cross-reference research before submitting a new proposal.

Input parameters:

- `idea` (string, required): One-paragraph project idea or capability description.

### `proposal_success_predictor` (~68 tokens)

Heuristic readiness score for a Dev Fund proposal draft, based on attributes that correlate with approval in the historical corpus: explicit milestones, code/PoC references, sources, scope realism. Canton-specific. Not a vote; a checklist.

Input parameters:

- `draft_text` (string, required): Full draft text.

### `full_context` (~156 tokens)

Single free-text query across CCPEDIA's entire corpus at once: docs, CIPs, forum, mailing, GitHub items, blog, videos, whitepapers, ecosystem projects. Canton-specific. Use for an exhaustive cross-source roundup on a topic described in words, even if that topic happens to be a known CIP's nickname (e.g. 'featured app locking'). This tool does not require a CIP id. If the user already gives a specific CIP id/number, use get_cip_citations instead for a deeper single-CIP citation graph. For narrow single-source searches prefer the specialised tools.

Input parameters:

- `limit_per_source` (integer): Max rows per source (default 3).
- `topic` (string, required): Topic / question.

### `community_consensus` (~69 tokens)

Surface signals of what the Canton community thinks about a topic: forum thread reply ratios, mailing list debate volume, and the highest-rated reply on the most-viewed thread. Canton-specific. Not sentiment-analysis; a structured roundup the caller can summarise.

Input parameters:

- `topic` (string, required): Topic to assess.

### `find_expert` (~67 tokens)

Rank likely Canton experts on a topic across CCPEDIA: forum activity matching the topic, plus overall forum/GitHub volume of that author. Canton-specific.

Input parameters:

- `limit` (integer): Max authors (default 5).
- `topic` (string, required): Topic / domain to find experts for.

### `detect_drift` (~77 tokens)

Find contradictions between docs, forum and GitHub on a topic. Returns counts of how each surface talks about it plus the most recent doc-page and forum statement so the caller can spot mismatches. Distinct from get_kb_drift (which compares foundation_kb to live releases).

Input parameters:

- `topic` (string, required): Topic to cross-check.

### `learning_path` (~86 tokens)

Construct a structured Canton onboarding sequence for a stated goal: whitepaper → relevant docs → CIPs to know → forum starter threads → talks. Canton-specific. Topic-driven (distinct from get_started_guide which is background-driven).

Input parameters:

- `goal` (string, required): What the learner wants to do, e.g. "build a Canton dApp", "operate a validator", "write a CIP".

### `outdated_guidance_detector` (~63 tokens)

Surface CCPEDIA content that mentions deprecated Canton/Daml tooling alongside the user's query: likely outdated. Cross-references foundation_kb.DEPRECATED with doc_pages, forum_posts, and blog_posts. Canton-specific.

Input parameters:

- `query` (string, required): Topic to scan.

### `ecosystem_dependency_graph` (~65 tokens)

Map ecosystem_projects matching a topic to the SDK versions and repos they appear alongside, building a quick dependency picture. Canton-specific. Useful for "if I build with X SDK version, who else is on it?".

Input parameters:

- `topic` (string, required): Topic / category / project family.

### `find_collaboration_opportunities` (~55 tokens)

Given one Canton ecosystem project, find others with complementary tags/category that could plug in. Canton-specific. Lightweight heuristic: overlap of tags + adjacent categories.

Input parameters:

- `project` (string, required): Project name or slug to look around.

### `list_canton_mcps` (~78 tokens)

List the Canton Network MCP servers CCPEDIA knows about: a directory of the Canton MCP ecosystem (payments, wallets, docs, knowledge). For each: what it does, how to connect or run it, whether it is free/hosted, and whether CCPEDIA can call it directly via call_canton_mcp. Canton-specific.

### `call_canton_mcp` (~133 tokens)

Federate a tool call to another Canton MCP server (see list_canton_mcps). CCPEDIA proxies the call and returns the result, acting as one MCP that routes across the Canton MCP ecosystem. Only free, hosted, no-auth Canton MCPs can be proxied; local or paid ones return connect instructions instead. Canton-only.

Input parameters:

- `arguments` (object): Arguments object for that tool
- `server` (string, required): Target MCP id from list_canton_mcps (e.g. "ccpedia", "x402-mcp")
- `tool` (string, required): Tool name to call on that server

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/unitynodes-canton-ccpedia/ccpedia#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 63
- 2026-08-01: 62
- 2026-07-31: 62
- 2026-07-30: 60
- 2026-07-29: 58
- 2026-07-28: 58
- 2026-07-27: 58
- 2026-07-26: 57

## Links

- Remote endpoint: https://ccpedia.xyz/mcp
- Repository: https://github.com/UnityNodes/ccpedia
- Website: https://ccpedia.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/unitynodes-canton-ccpedia/ccpedia/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/unitynodes-canton-ccpedia/ccpedia/changelog.json
- HTML version of this page: https://verifymcp.io/servers/unitynodes-canton-ccpedia/ccpedia