io.github.UnityNodes/canton-ccpedia
REMOTE · CCPEDIA.XYZ · SCANNED SEP 22
Canton Network: CIPs and their on-chain vote outcomes, docs, forum, validator upgrade deadlines.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability49
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 12482 tokens (~128/item across 97 items; 90 tools + 7 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 99% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 90 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 92 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.UnityNodes/canton-ccpedia MCP server?
io.github.UnityNodes/canton-ccpedia is a hosted endpoint at https://ccpedia.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ccpedia.xyz
claude mcp add --transport http unitynodes-canton-ccpedia 'https://ccpedia.xyz/mcp'
{
"mcpServers": {
"unitynodes-canton-ccpedia": {
"url": "https://ccpedia.xyz/mcp"
}
}
} {
"servers": {
"unitynodes-canton-ccpedia": {
"type": "http",
"url": "https://ccpedia.xyz/mcp"
}
}
} [mcp_servers.unitynodes-canton-ccpedia] url = "https://ccpedia.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"unitynodes-canton-ccpedia": {
"type": "remote",
"url": "https://ccpedia.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add unitynodes-canton-ccpedia --url 'https://ccpedia.xyz/mcp' --transport streamable-http
mcp_servers:
unitynodes-canton-ccpedia:
url: "https://ccpedia.xyz/mcp" {
"McpServers": {
"unitynodes-canton-ccpedia": {
"Transport": "http",
"Url": "https://ccpedia.xyz/mcp"
}
}
} assistant mcp add unitynodes-canton-ccpedia -t streamable-http -u 'https://ccpedia.xyz/mcp'
{
"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.
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.
- 21 Sept 26 0
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: 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. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 0 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 20 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Schema quality: 0 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 16 Sept 26 0
- Stability: fail → pass ▲ security
- 8 Sept 26 0
- New tool “get_asset_supply” functional
- New tool “get_defi_pools” functional
- 30 Aug 26 0
- Tool “compare_governance_outcomes” 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 “list_cips” 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 “search” rewrote its description, which is the text the model reads security
- “list_mailing_threads” reworded the description of “group” cosmetic
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 96 to 99.
- 18 Aug 26 0
- Tool “community_consensus” rewrote its description, which is the text the model reads security
- Tool “get_app_metrics” rewrote its description, which is the text the model reads security
- Tool “search_github_issues” rewrote its description, which is the text the model reads security
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 22 Sept 2026 · Probed https://ccpedia.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ccpedia.xyz | CN=YE1,O=Let's Encrypt,C=US | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 52fc0b44cdf871a6a4a22743e0fe4cc89ab |
| SANs: *.ccpedia.xyz, ccpedia.xyz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ccpedia.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| ccpedia.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ccpedia.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://ccpedia.xyz/mcp | HTTPS enforced | 301 | https://ccpedia.xyz/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_proposals ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many proposals to return. Default 20, max 50. The response states the full count. |
| offset | integer | – | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
| state | string | – | Grant-request state on GitHub. Defaults to "open", so the total reported is open requests rather than every proposal ever filed. |
No output schema declared.
No examples provided.
get_radar ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | Severity floor. "critical" and "important" return only that level; "ecosystem" is the low-severity feed; "all" (default) returns every live alert. |
| limit | integer | – | How many alerts to return, most severe and most recent first. Default 25. |
| offset | integer | – | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
No output schema declared.
No examples provided.
get_recent_changes ~147
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How far back to look, in days, counted from now. Default 7, max 90. |
| limit | integer | – | How many changes to return, newest first. Default 50, max 200. |
No output schema declared.
No examples provided.
get_recent_deployments ~115
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?".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many deployments to return, newest first. Default 10, max 50. |
| offset | integer | – | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
No output schema declared.
No examples provided.
get_recurring_issue_fingerprint ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
get_sdk_changelog ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | – | Optional repo hint: canton, daml, dpm, splice. |
| version | string | yes | Version tag, e.g. "3.5.6", "v3.5.6", "0.6.10". |
No output schema declared.
No examples provided.
get_started_guide ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| background | string | yes | Developer's primary background. Ask the user to select this before proceeding. |
No output schema declared.
No examples provided.
get_sv_schedule ~122
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?".
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_token_market ~102
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_trending ~76
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_upcoming_deadlines ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_upcoming_operations ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days ahead to look (1-180, default 30). |
No output schema declared.
No examples provided.
get_upgrade_status ~154
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?".
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | yes | 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. |
No output schema declared.
No examples provided.
get_validator ~237
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", "how reliable is X", and "who onboarded X" where the registry records a distinct sponsor (about half the fleet does; the rest name themselves and this says so rather than repeating the node name back). 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum matches to return (default 10, max 50). |
| name | string | yes | Validator name or party id, whole or partial, e.g. "GSF-validator-2" or "MPCH". |
No output schema declared.
No examples provided.
get_validator_fleet ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| version | string | – | Your Splice version, e.g. "0.6.9", to locate it in the distribution. |
No output schema declared.
No examples provided.
get_video ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | YouTube video id, e.g. "dQw4w9WgXcQ" |
| transcript_chars | integer | – | Transcript characters to return. Default 12000; raise it (max 200000) for the full text, or set 0 for metadata only. |
No output schema declared.
No examples provided.
get_whitepaper ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Whitepaper slug, e.g. "canton-network-whitepaper" |
No output schema declared.
No examples provided.
learning_path ~86
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).
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | yes | What the learner wants to do, e.g. "build a Canton dApp", "operate a validator", "write a CIP". |
No output schema declared.
No examples provided.
list_canton_mcps ~78
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_cips ~218
Browse Canton Improvement Proposals (CIPs), optionally filtered by status (Draft, Early Draft, In Review, Proposed, Approved, Active, Final, Withdrawn, Rejected, Replaced, Obsolete, Pending) 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many CIPs to return. Default 20, max 100. The response states the full count, which can exceed this limit; page with offset. |
| offset | integer | – | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
| status | string | – | – |
| type | string | – | Type filter, e.g. "Standards Track" |
No output schema declared.
No examples provided.
list_deprecations ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Kind of thing deprecated. "all" (default) returns every category. |
No output schema declared.
No examples provided.
list_ecosystem_projects ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category (e.g. "DeFi", "Wallets", "NaaS") |
| limit | integer | – | How many projects to return. Default 30, max 100. The response states the full count. |
| liveness | string | – | Restrict to projects whose site last responded this way to CCPEDIA's daily probe. Omit for all of them; every row is labelled either way. |
| offset | integer | – | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
| query | string | – | Search in title/description/tags |
No output schema declared.
No examples provided.
list_featured_apps ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
list_github_discussions ~207
List GitHub Discussions from Canton Network and Digital Asset repositories cached by CCPEDIA, sorted by recency (newest first). Filter by repo or category, or call with no filter to see which repos are present. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by Discussions category, e.g. "Q&A", "Ideas" |
| limit | integer | – | How many discussions to return, newest first. Default 15, max 50. |
| repo | string | – | Filter by owner/name as shown in the unfiltered listing. Repos get transferred, so read the value from a result rather than assuming one. |
No output schema declared.
No examples provided.
list_governance_votes ~278
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Filter by action, e.g. "SRARC_GrantFeaturedAppRight", "SRARC_RevokeFeaturedAppRight", "SRARC_UpdateSvRewardWeight", "SRARC_OffboardSv". |
| limit | integer | – | Max rows (default 20). |
| offset | integer | – | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
| outcome | string | – | Filter by outcome. Omit for all outcomes; there is no "all" value. |
| status | string | – | "open" for votes still in flight, "closed" for decided ones. Omit for both; there is no "all" value. |
No output schema declared.
No examples provided.
list_mailing_threads ~224
List threads from the Canton Network governance mailing lists (lists.sync.global groups: cip-discuss, cip-vote, cip-announce, globalSyncForum, grants-discuss, validator-announce, tokenomics-announce, supervalidator-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.
| Name | Type | Req | Description |
|---|---|---|---|
| cip_id | string | – | CIP number filter, e.g. "0117". Returns only threads tagged with this CIP. |
| group | string | – | Restrict to one of the 8 indexed groups. |
| limit | integer | – | How many threads to return. Default 20, max 100. |
| offset | integer | – | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
| since | string | – | Earliest last_post_at ISO date. |
No output schema declared.
No examples provided.
list_repos ~96
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_videos ~242
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | How many videos to return. Default 20, max 100. |
| offset | integer | – | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
| since | string | – | Earliest published_at (ISO date, e.g. "2026-01-01"). Default: no lower bound. |
No output schema declared.
No examples provided.
list_votes_by_sv ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sv_name | string | – | Super Validator short name, e.g. "Tradeweb-Markets-1", "Digital-Asset-1", "Cumberland-1". Omit for all of them. |
No output schema declared.
No examples provided.
list_whitepapers ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
migrate_lookup ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The deprecated command, package, or tool name to look up. Best-match search. |
No output schema declared.
No examples provided.
outdated_guidance_detector ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Topic to scan. |
No output schema declared.
No examples provided.
proposal_success_predictor ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| draft_text | string | yes | Full draft text. |
No output schema declared.
No examples provided.
search ~246
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. NOTE: forum matches cover the topic TITLE and the FIRST POST only; a term that appears only inside a forum reply will not surface here, so use semantic_search (which indexes all forum post bodies) when a forum discussion is likely and this returns nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results to return (1-50) |
| offset | integer | – | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
| query | string | yes | Search query |
| type | string | – | Restrict results to one source type; "governance" is the stated reasoning behind an on-chain DSO vote; "all" searches everything |
No output schema declared.
No examples provided.
search_community ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max hits per source (default 5). |
| query | string | yes | Free-text query. |
No output schema declared.
No examples provided.
search_github_issues ~136
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 get_proposals (Dev Fund grant PRs) or search with type="github" (broader).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows (default 10). |
| offset | integer | – | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
| query | string | yes | Free-text query. |
| state | string | – | Issue state filter (default: all). |
No output schema declared.
No examples provided.
search_mailing_list ~121
Search across CCPEDIA's indexed Canton mailing-list archives (cip-discuss, cip-vote, grants-discuss, validator-announce, etc). Canton-specific.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Optional group_slug filter, e.g. "cip-discuss". |
| limit | integer | – | Max rows (default 10). |
| offset | integer | – | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
| query | string | yes | Free-text query. Appears in subject or body. |
No output schema declared.
No examples provided.
search_release_notes ~63
Search across release-notes bodies of all indexed Canton repos for a feature/keyword. Canton-specific. Use to find which release first mentioned X.
| Name | Type | Req | Description |
|---|---|---|---|
| feature | string | yes | Feature keyword, e.g. "logical synchronizer", "topology", "wallet kernel". |
No output schema declared.
No examples provided.
search_talks ~100
Search CCPEDIA's indexed Canton talks/videos (YouTube transcripts). Canton-specific. Returns matches across title + transcript with a short snippet around the hit.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows (default 5). |
| offset | integer | – | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
| query | string | yes | Free-text query. Appears in title or transcript. |
No output schema declared.
No examples provided.
semantic_search ~276
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many chunks to return. Default 6, max 15. Capped at 2 per document so one long file cannot take every slot. |
| query | string | yes | Free-form question or phrase. |
| source_types | array | – | Restrict to these source types. "proposal" is a Dev Fund grant request; "github_item" is an ordinary issue or PR from any other indexed repo; "sdk_version" is a released package version from the npm/… |
No output schema declared.
No examples provided.
What is the io.github.UnityNodes/canton-ccpedia MCP server?
io.github.UnityNodes/canton-ccpedia is an MCP server listed in the public MCP registry as io.github.UnityNodes/canton-ccpedia. Canton Network: CIPs and their on-chain vote outcomes, docs, forum, validator upgrade deadlines. This page covers its hosted endpoint (https://ccpedia.xyz/mcp).
Is the io.github.UnityNodes/canton-ccpedia MCP server safe to use?
io.github.UnityNodes/canton-ccpedia scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.UnityNodes/canton-ccpedia MCP server expose?
io.github.UnityNodes/canton-ccpedia exposes 90 tools: search, get_cip, list_cips, get_discussion, get_whitepaper, and 85 more. Their descriptions and schemas cost roughly 12,057 tokens of context every time the server is loaded.
Does the io.github.UnityNodes/canton-ccpedia MCP server require authentication?
No. We connected to io.github.UnityNodes/canton-ccpedia without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.UnityNodes/canton-ccpedia MCP server still maintained?
io.github.UnityNodes/canton-ccpedia is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.