Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.UnityNodes/canton-ccpedia

REMOTE · CCPEDIA.XYZ

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

Available components

0 this week 76 Trust /100

Last scanned (16 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability47
  • 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 15944 tokens (~143/item across 111 items; 104 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
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 104 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 106 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 5 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 28 Oct 26 0
    • Tool “list_cips” rewrote its description, which is the text the model reads security
  • 27 Oct 26 0
    • New tool “get_blog_post” functional
    • New tool “list_blog_posts” functional
Diagnostics

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 21 Nov 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=YE2,O=Let's Encrypt,C=US 4 Nov 2026 2 Feb 2027 ECDSA 256 ECDSA-SHA384 57da946b6bd4892269922e8a9b6781f6f02
SANs: *.ccpedia.xyz, ccpedia.xyz
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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. DS published 3599, 18130 8, 8 Verified
ccpedia.xyz. No DS 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
MCP tools · 104 exposed · ~15,339 tokens

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 →

Tool Tokens
get_latest_release ~138

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.

NameTypeReqDescription
packagestringyesRepo or package name: "canton", "daml", "dpm", "splice", or a full owner/repo.

No output schema declared.

No examples provided.

get_mailing_thread ~187

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.

NameTypeReqDescription
idstringyesThread id exactly as list_mailing_threads prints it. Both forms work: a numeric archive topic id ("119286914") and a message id for messages the archive never threaded ("cip-discuss-809").
limitinteger–How many messages (oldest first) to return. Default 25, max 100. The header states the full held count and the range shown.
offsetinteger–Skip this many messages before returning, for paging through a long thread.

No output schema declared.

No examples provided.

get_network_state ~120

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 the last published cumulative app/validator rewards in CC with the closed round and date they describe (flagged when upstream has stopped publishing them). 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).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_network_stats ~107

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_npm_packages ~89

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

NameTypeReqDescription
limitinteger–Max packages (default 25).
offsetinteger–Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
querystring–Optional substring filter on package name.

No output schema declared.

No examples provided.

get_proposal ~179

Everything CCPEDIA holds about ONE Canton Dev Fund proposal (a pull request in canton-foundation/canton-dev-fund), by its PR number: state and project-board column, labels, the facts parsed from the proposal file (organization, author, declared RFP, champion, funding in CC, duration, SIG label, milestones), champion evidence (board column, proposal file, PR text), reviewers, discussion statistics, and the timeline of label, reviewer, rename and board events. Use after get_proposals, list_proposals_needing_champion or search_dev_fund returned a number. For the full conversation use get_proposal_discussion, for the full proposal text get_proposal_file. Canton-specific.

NameTypeReqDescription
numberintegeryesPR (or issue) number in canton-foundation/canton-dev-fund, e.g. 439.

No output schema declared.

No examples provided.

get_proposal_discussion ~185

The conversation on ONE Canton Dev Fund proposal, oldest first: every comment, every formal review (approved, changes requested, commented) and every inline review comment on the proposal file, with author, GitHub role (member, collaborator, none), date, and the text. Pages with offset. Use to read what reviewers, champions and the committee actually said, or why a proposal stalled. Canton-specific.

NameTypeReqDescription
kindstring–Only this kind: issue_comment (conversation), review_comment (inline on the file), review (a formal review verdict).
limitinteger–How many entries to return. Default 10, max 30. The response states the full count.
numberintegeryesPR (or issue) number in canton-foundation/canton-dev-fund.
offsetinteger–Skip this many entries, for paging.

No output schema declared.

No examples provided.

get_proposal_file ~123

The full text of the proposal file(s) a Canton Dev Fund PR adds (proposals/*.md or rfps/<category>/*.md), exactly as in the PR head: abstract, specification, milestones, acceptance criteria, funding. A PR can add several files; pass path to pick one. Use after get_proposal when the details matter. Canton-specific.

NameTypeReqDescription
numberintegeryesPR number in canton-foundation/canton-dev-fund.
pathstring–One of the paths listed for that PR. Omit for the first file.

No output schema declared.

No examples provided.

get_proposal_milestones ~59

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

NameTypeReqDescription
pr_numberintegeryesPR number in canton-foundation/canton-dev-fund.

No output schema declared.

No examples provided.

get_proposals ~221

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, board status and how many people commented; it is only an index. For one proposal in full (champion evidence, proposal file, every comment, review and timeline event) call get_proposal and get_proposal_discussion. Canton ecosystem only.

NameTypeReqDescription
limitinteger–How many proposals to return. Default 20, max 50. The response states the full count.
offsetinteger–Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
statestring–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.

NameTypeReqDescription
levelstring–Severity floor. "critical" and "important" return only that level; "ecosystem" is the low-severity feed; "all" (default) returns every live alert.
limitinteger–How many alerts to return, most severe and most recent first. Default 25.
offsetinteger–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'.

NameTypeReqDescription
daysinteger–How far back to look, in days, counted from now. Default 7, max 90.
limitinteger–How many changes to return, newest first. Default 50, max 500.

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?".

NameTypeReqDescription
limitinteger–How many deployments to return, newest first. Default 10, max 50.
offsetinteger–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.

NameTypeReqDescription
min_monthsinteger–A keyword must appear in this many distinct months to count as recurring (default 3).
window_monthsinteger–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.

NameTypeReqDescription
repostring–Optional repo hint: canton, daml, dpm, splice.
versionstringyesVersion 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.

NameTypeReqDescription
backgroundstringyesDeveloper'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?".

NameTypeReqDescription
environmentstring–Restrict to one environment. Omit for all.
limitinteger–Max rows (default 20).
upcoming_onlyboolean–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 ~192

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/validators#subscribe. For a verdict on your specific version use get_upgrade_status; for the full historical schedule use get_sv_schedule. Canton ecosystem only.

NameTypeReqDescription
daysinteger–How far ahead to look, in days. Default 30.
environmentstring–"MainNet", "TestNet" or "DevNet". Omit for all networks.
validator_onlyboolean–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.

NameTypeReqDescription
daysinteger–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?".

NameTypeReqDescription
environmentstringyesWhich network the node runs on.
versionstring–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.

NameTypeReqDescription
limitinteger–Maximum matches to return (default 10, max 50).
namestringyesValidator 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.

NameTypeReqDescription
versionstring–Your Splice version, e.g. "0.6.9", to locate it in the distribution.

No output schema declared.

No examples provided.

get_video ~289

Get a Canton Network video that CCPEDIA has cached (curated channels: Canton Network, Digital Asset, Sync Insights, Canton Foundation, Daml, Digital Asset Training) by its YouTube id: title, channel, publish date, description and the transcript, with the time of each passage when timings are stored. Pass query to get only the passages that mention a term, each with its time and a link that opens the video there. Pass offset to keep reading a long transcript past the first part. 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.

NameTypeReqDescription
idstringyesYouTube video id, e.g. "dQw4w9WgXcQ"
offsetinteger–Character position to start reading the transcript from, for a long one. The response names the offset that continues the read.
querystring–Return only the passages of the transcript that mention these words, each with its time and a link that opens the video at that moment. Replaces the plain read; offset is ignored.
transcript_charsinteger–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.

NameTypeReqDescription
slugstringyesWhitepaper 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).

NameTypeReqDescription
goalstringyesWhat 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_blog_posts ~248

List the blog posts CCPEDIA holds: articles, news and press releases from Canton, Digital Asset and the Canton Foundation, and in tabs of their own partner press, network notices from the release channel, and third-party reprints. Omit source for what the Blog page shows under All. Pass query to search titles and text. Returns metadata only (id, title, kind, author, date); call get_blog_post with an id to read one. Release notes are not blog posts: they are under /releases.

NameTypeReqDescription
limitinteger–How many posts to return. Default 20, max 50.
offsetinteger–Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
querystring–Words to look for in titles and text. Results come best match first.
sourcestring–Which tab: blog (Blog), news (News), press-release (Press), canton-foundation (Foundation), da-blog (Digital Asset), partner-news (Partner press), notices (Network notices), third-party (Third-party)…

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 ~221

Browse Canton Improvement Proposals (CIPs), optionally filtered by status (Draft, Early Draft, In Review, Proposed, Proposed Amendment, 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.

NameTypeReqDescription
limitinteger–How many CIPs to return. Default 20, max 100. The response states the full count, which can exceed this limit; page with offset.
offsetinteger–Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
statusstring––
typestring–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.

NameTypeReqDescription
categorystring–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.

NameTypeReqDescription
categorystring–Filter by category (e.g. "DeFi", "Wallets", "NaaS")
limitinteger–How many projects to return. Default 30, max 100. The response states the full count.
livenessstring–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.
offsetinteger–Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
querystring–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.

NameTypeReqDescription
categorystring–Filter by category, e.g. "Validator", "DeFi", "Tokenized Assets" (case-insensitive substring match).
limitinteger–Max rows (default 25).
sortstring–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.

NameTypeReqDescription
categorystring–Filter by Discussions category, e.g. "Q&A", "Ideas"
limitinteger–How many discussions to return, newest first. Default 15, max 50.
repostring–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.

NameTypeReqDescription
actionstring–Filter by action, e.g. "SRARC_GrantFeaturedAppRight", "SRARC_RevokeFeaturedAppRight", "SRARC_UpdateSvRewardWeight", "SRARC_OffboardSv".
limitinteger–Max rows (default 20).
offsetinteger–Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
outcomestring–Filter by outcome. Omit for all outcomes; there is no "all" value.
statusstring–"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 ~220

List threads from the Canton Network governance mailing lists (lists.sync.global groups: cip-discuss, cip-vote, cip-announce, 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.

NameTypeReqDescription
cip_idstring–CIP number filter, e.g. "0117". Returns only threads tagged with this CIP.
groupstring–Restrict to one of the 7 indexed groups.
limitinteger–How many threads to return. Default 20, max 100.
offsetinteger–Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
sincestring–Earliest last_post_at ISO date.

No output schema declared.

No examples provided.

list_proposals_needing_champion ~274

List open Canton Dev Fund proposals waiting in the Needs Champion or Incoming columns of the Foundation's project board, i.e. with no champion confirmed there, oldest first, with what the proposal file and the PR text say about its champion. A proposal needs a champion, a sponsor from the Tech & Ops Committee, to move into review, and many stall without one. The bot labels needs-champion and champion-confirmed are deliberately NOT used as evidence: champion-confirmed is set from the PR text at filing and has been wrong. Evidence is the board column (champion assigned, Ready for Vote, Voting Live, Approved) plus the Champion line in the proposal file and in the PR text; a name there is the applicant's claim, not a confirmation. A proposal whose file is not held and whose PR text is silent is reported as "not stated", which does not mean "none". SIG-membership PRs are excluded. Canton-specific.

NameTypeReqDescription
limitinteger–How many proposals to return. Default 20, max 50. The response states the full count.
offsetinteger–Skip this many before returning, for paging past the limit.
rfpinteger–Only proposals that declare this RFP number (label, PR text, title or proposal file).

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_rfps ~196

List the Canton Foundation Dev Fund Requests for Proposals (RFPs) from the 2026-2028 roadmap: number, title, category, and how many Dev Fund proposals declare each one. Pass number to read one RFP in full: what the Foundation asks for, its stated appetite for grants, prior funded examples, and the proposals declaring it. RFP numbers are the ones proposals and labels use (RFP 18 is Integration into SDLCs). A proposal counts only if a label, its PR text, its title or its proposal file names the RFP, and most proposals do not, so a low count is not proof that an area is uncrowded. Canton-specific. To find the RFP that fits an idea use find_rfp_for_idea.

NameTypeReqDescription
numberinteger–RFP number to read in full, e.g. 18. Omit to list every RFP.

No output schema declared.

No examples provided.

list_stuck_proposals ~202

Open Canton Dev Fund proposals that nothing has happened on for at least a number of days (no human comment, review or board move), oldest first, grouped by who the next step is on: the applicant (the committee asked for changes), the committee (someone is assigned or it is ready for a vote), nobody picked it up (no champion, no reviewer), or a vote. Each item states the reason in plain words and who acted last. Proposals whose board history is incomplete are listed apart as unplaced. Use for "what is stuck and on whom". Canton-specific.

NameTypeReqDescription
limitinteger–How many proposals. Default 20, max 50. The response states the full count.
offsetinteger–Skip this many, for paging.
stuck_daysinteger–Idle for at least this many days. Default 30.
waiting_onstring–Only proposals whose next step is on this side.

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, Digital Asset Training), 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.

NameTypeReqDescription
channelstring–Channel name filter, one of Canton Network, Digital Asset, Sync Insights, Canton Foundation, Daml, Digital Asset Training. Case-insensitive substring.
has_transcriptboolean–If true, only return videos with a stored transcript. If false, only those still missing one. Omit for both.
limitinteger–How many videos to return. Default 20, max 100.
offsetinteger–Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
sincestring–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.

NameTypeReqDescription
sv_namestring–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.

NameTypeReqDescription
querystringyesThe 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.

NameTypeReqDescription
querystringyesTopic 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.

NameTypeReqDescription
draft_textstringyesFull 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.

NameTypeReqDescription
limitinteger–Max results to return (1-50)
offsetinteger–Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
querystringyesSearch query
typestring–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.

NameTypeReqDescription
limitinteger–Max hits per source (default 5).
querystringyesFree-text query.

No output schema declared.

No examples provided.

search_dev_fund ~338

Search ALL Canton Dev Fund text for words: proposal files, PR descriptions, every comment, formal review and inline review comment, ranked by relevance with a snippet around the match. Scope can be narrowed to comments, proposal_files or descriptions, and to one GitHub author. Use for "who said what about X", "which proposals mention Y", "did a reviewer object to Z". Default mode "words" is lexical (the words must appear, exact and exhaustive). Mode "meaning" searches the same text by meaning with embeddings plus words, so "did anyone worry about validator uptime" finds a comment that never says uptime; it cannot be limited to one author. For a ranked pick among whole proposals for an idea use find_rfp_for_idea or detect_builder_overlap. Canton-specific.

NameTypeReqDescription
authorstring–GitHub login; limits comments and PR descriptions to that person.
limitinteger–How many hits to return. Default 10, max 30.
modestring–words (default): exact, exhaustive, every word must appear. meaning: best match by meaning and words together, over comments, proposal files and PR descriptions; does not support the author filter.
offsetinteger–Skip this many hits, for paging.
querystringyesWords to look for, e.g. "indexer champion" or "volatility amendment". In mode "meaning", a plain-language question or phrase.
scopestring–all, comments (comments + reviews + inline review comments), proposal_files, or descriptions (titles and descriptions of pull requests and tracking issues).

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).

NameTypeReqDescription
limitinteger–Max rows (default 10).
offsetinteger–Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
querystringyesFree-text query.
statestring–Issue state filter (default: all).

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http unitynodes-canton-ccpedia 'https://ccpedia.xyz/mcp'
Common questions

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 104 tools: search, get_cip, list_cips, get_discussion, get_whitepaper, and 99 more. Their descriptions and schemas cost roughly 15,339 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.UnityNodes/canton-ccpedia MCP server?

VerifyMCP ran 12 checks on io.github.UnityNodes/canton-ccpedia, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.UnityNodes/canton-ccpedia: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.