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 →
call_canton_mcp ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | Arguments object for that tool |
| server | string | yes | Target MCP id from list_canton_mcps (e.g. "ccpedia", "x402-mcp") |
| tool | string | yes | Tool name to call on that server |
No output schema declared.
No examples provided.
check_deprecation ~162
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. Accepts either one name or a block of prose: given prose it reports every deprecated item mentioned in it. Returns DEPRECATED (with replacement), CURRENT, or NOT_FOUND.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Tool/package/command to check, e.g. "daml-assistant", "Navigator", "dpm", "canton sandbox". A longer block of text (a forum post, a draft answer) is scanned for every deprecated item it mentions. |
No output schema declared.
No examples provided.
community_consensus ~68
Surface signals of what the Canton community thinks about a topic: forum thread reply ratios, mailing list debate volume, and the first reply on the most-viewed thread. Canton-specific. Not sentiment-analysis; a structured roundup the caller can summarise.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | Topic to assess. |
No output schema declared.
No examples provided.
compare_governance_outcomes ~108
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 opened in the window that are closed today (merged, withdrawn and rejected are not distinguished; no close dates are stored). Canton-specific. Use to summarise "what governance has shipped this quarter?".
| Name | Type | Req | Description |
|---|---|---|---|
| window_days | integer | – | Window in days, 7-365 (default 90). |
No output schema declared.
No examples provided.
compare_to_evm ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| concept | string | yes | EVM concept, e.g. "smart contract", "wallet", "gas", "ERC20", "Hardhat", "Remix", "ABI". |
No output schema declared.
No examples provided.
detect_builder_overlap ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| idea | string | yes | One-paragraph project idea or capability description. |
No output schema declared.
No examples provided.
detect_cip_dependency_chain ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cip_id | string | yes | Starting CIP or PR id, e.g. "0112", "CIP-0112", or "PR-203". |
No output schema declared.
No examples provided.
detect_drift ~77
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).
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | Topic to cross-check. |
No output schema declared.
No examples provided.
diagnose_error ~168
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, and related GitHub issues (each with its own date). 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.
| Name | Type | Req | Description |
|---|---|---|---|
| error_text | string | yes | Error message, stack trace, or status code. Longer/more distinctive text returns better matches. |
| limit | integer | – | Max matches per source (default 3). |
No output schema declared.
No examples provided.
ecosystem_dependency_graph ~65
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?".
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | Topic / category / project family. |
No output schema declared.
No examples provided.
find_apps_by_pattern ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows (default 10). |
| pattern | string | yes | Free text, e.g. "AMM", "wallet", "DeFi vault", "validator". |
No output schema declared.
No examples provided.
find_cip_for_feature ~70
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?".
| Name | Type | Req | Description |
|---|---|---|---|
| feature | string | yes | Feature description, e.g. "wallet abstraction", "token standard", "validator staking". |
No output schema declared.
No examples provided.
find_code_examples ~99
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.
| 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. |
| topic | string | yes | Topic keyword. |
No output schema declared.
No examples provided.
find_collaboration_opportunities ~55
Given one Canton ecosystem project, find others with complementary tags/category that could plug in. Canton-specific. Lightweight heuristic: overlap of tags + adjacent categories.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name or slug to look around. |
No output schema declared.
No examples provided.
find_expert ~67
Rank likely Canton experts on a topic across CCPEDIA: forum activity matching the topic, plus overall forum/GitHub volume of that author. Canton-specific.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max authors (default 5). |
| topic | string | yes | Topic / domain to find experts for. |
No output schema declared.
No examples provided.
find_known_issues ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What you're seeing. Short prose, not a stack trace (for that use diagnose_error). |
| limit | integer | – | Max rows per source (default 5). |
No output schema declared.
No examples provided.
find_maintainer_guidance ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | Topic keyword, e.g. "topology", "wallet", "DAR upload". |
No output schema declared.
No examples provided.
find_security_patches ~55
Surface release notes likely to contain security or CVE fixes. Canton-specific. Heuristic: matches release bodies containing security / CVE / vulnerability / patch keywords.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows (default 10). |
No output schema declared.
No examples provided.
find_similar_projects ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Project description / idea. |
| 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. |
No output schema declared.
No examples provided.
full_context ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit_per_source | integer | – | Max rows per source (default 3). |
| topic | string | yes | Topic / question. |
No output schema declared.
No examples provided.
get_api_reference ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | yes | Which API to look up. |
No output schema declared.
No examples provided.
get_app_metrics ~100
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, and last activity from the Featured Apps registry. Canton-specific. TVL / volume / users may be null when only the Scan API source is available.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Featured-app contract id, or a unique prefix of it as shown by list_featured_apps. |
No output schema declared.
No examples provided.
get_asset_supply ~237
Get total token supply for a Canton-ecosystem asset: Canton Coin (CC), CBTC, HECTO, HANDL, USDCx, EDELx, or cETH. Omit the asset param to get all seven. Each row carries provenance: Canton Coin's supply is chain_derived (verifiable via the Global Synchronizer Scan registry); every other asset's supply is issuer_reported (CIP-0056 states on-ledger publication does not allow independent verification of total supply, since the holdings it's computed from are private) - treat those numbers as the issuer's own claim, not an audited fact. Holder counts are usually not_disclosed (Canton's privacy model hides holdings from third parties by design) and appear as null, not zero. Sourced from CCTools' public API. Canton-only; cannot price or size-supply any other chain's tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Slug or symbol to filter to one asset, e.g. "cbtc", "CBTC", "canton-coin", or "CC". Case-insensitive. Omit for all seven. |
No output schema declared.
No examples provided.
get_breaking_changes ~191
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").
| Name | Type | Req | Description |
|---|---|---|---|
| from_sdk | string | yes | 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 | yes | Target version, e.g. "0.6.10" or "v3.5.6". |
No output schema declared.
No examples provided.
get_cip ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | CIP ID: "0001", "CIP-0042", or "PR-0117" |
No output schema declared.
No examples provided.
get_cip_attachments ~143
Get the file/PDF attachments of a single Canton Improvement Proposal (CIP): supporting documents and signed-vote-record PDFs, with filename, page count, URL, and the full text CCPEDIA has extracted from each. Many older CIPs publish the proposal ITSELF as a PDF and leave only a header block in markdown, so for those this returns the actual proposal text and get_cip returns the index entry. For the parsed who-voted-how breakdown use get_cip_votes. Canton ecosystem only. Not Cardano or other 'CIP' schemes.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | CIP ID: "0001", "CIP-0042" |
No output schema declared.
No examples provided.
get_cip_citations ~302
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 (all indexed lists.sync.global groups; no group is excluded), 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.
| Name | Type | Req | Description |
|---|---|---|---|
| cip_id | string | yes | CIP id, e.g. "CIP-0056", "0056", "PR-0117". Padded or unpadded both accepted. |
No output schema declared.
No examples provided.
get_cip_history ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | CIP ID: "0001", "CIP-0042", or "PR-0117" |
No output schema declared.
No examples provided.
get_cip_implementation_status ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cip_id | string | yes | CIP id, e.g. "0112", "CIP-0112", "PR-0088". |
No output schema declared.
No examples provided.
get_cip_mentions ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | CIP ID: "0001", "CIP-0042", or "PR-0117" |
No output schema declared.
No examples provided.
get_cip_vote_outcome ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cip_id | string | yes | CIP id, e.g. "CIP-0116", "116", "0116". |
| limit | integer | – | How many vote requests to return, newest first. Default 20, max 100. The response states the full count either way. |
No output schema declared.
No examples provided.
get_cip_votes ~239
Get the cip-vote mailing-list messages for a specific Canton Improvement Proposal (CIP), oldest first: the raw discussion trail as sent, with each SV/participant's vote stated in their message body ("… votes in favor / not in favor"). This is the message thread, NOT a pre-computed count; the first message is usually the proposal announcement, not a vote. For the on-chain accept/reject tally use get_cip_vote_outcome. Use for reading who said what 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.
| Name | Type | Req | Description |
|---|---|---|---|
| cip_id | string | yes | CIP id, e.g. "0117", "0118", or "CIP-0117". Numeric form preferred. |
| limit | integer | – | How many messages (oldest first) to return. Default 25, max 100. The header states the full count and the range shown. |
| offset | integer | – | Skip this many messages before returning, for paging through a long vote thread. |
No output schema declared.
No examples provided.
get_current_versions ~175
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_defi_pools ~135
Get per-pool DeFi liquidity data on Canton from OneSwap, Send, and Tradecraft: pair, TVL, fee rate, APY, and reserve amounts. This is pool-level detail; for aggregate protocol-level TVL across all of Canton DeFi use get_token_market instead (that one also lists Cantex, which this tool does not cover - Cantex's own API has been down and CCTools marks its numbers stale). Sourced from CCTools' public API. Canton-only.
| Name | Type | Req | Description |
|---|---|---|---|
| protocol | string | – | Restrict to one DEX. Omit for all three. |
No output schema declared.
No examples provided.
get_discussion ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | Forum topic ID from a search result, e.g. 3242 or "topic:3242". Not a doc-page id: those go to get_doc. |
No output schema declared.
No examples provided.
get_doc ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | Doc page ID from a search/semantic_search result, e.g. 3242 or "doc:3242". Not a forum topic id: those go to get_discussion. |
No output schema declared.
No examples provided.
get_ecosystem_gaps ~93
Surface ecosystem gaps: high-view forum threads with zero replies (unanswered demand), mailing threads that got no reply, and open Dev Fund proposals with no label assigned (waiting for a SIG or champion). Canton-specific. Use to find "where the ecosystem needs help". For per-category funding levels use get_funding_landscape.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows per gap type (default 5). |
No output schema declared.
No examples provided.
get_faq ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | Developer's question, e.g. "how do I install", "create party", "deploy to testnet". |
No output schema declared.
No examples provided.
get_foundation_info ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many matching sections to return. Default 3, max 10. |
| topic | string | yes | Free-text topic, e.g. "team", "executive director", "working groups", "membership", "grants", "board". |
No output schema declared.
No examples provided.
get_funding_landscape ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional label filter, e.g. "daml-tooling", "node-deployment-operations". |
No output schema declared.
No examples provided.
get_github_discussion ~120
Get the full body and comments of a single GitHub Discussion from a Canton Network or Digital Asset repo, 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).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | GitHub GraphQL node ID, e.g. "D_kwDOMNgu5s4AY..." |
No output schema declared.
No examples provided.
get_governance_vote ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tracking_cid | string | yes | The vote request tracking contract id, or a unique prefix of it, as returned by list_governance_votes. |
No output schema declared.
No examples provided.
get_issue_status ~73
Look up one GitHub issue or PR by repo + number. Canton/Daml/Splice repos only.
| Name | Type | Req | Description |
|---|---|---|---|
| number | integer | yes | Issue or PR number. |
| repo | string | yes | Repo, e.g. "canton-foundation/canton-dev-fund" or shorthand "canton-dev-fund". |
No output schema declared.
No examples provided.
get_kb_drift ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| refresh | boolean | – | If true, re-run the validator before returning the report. Default false uses the most recent stored findings. |
No output schema declared.
No examples provided.
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.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | Repo 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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Thread 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"). |
| limit | integer | – | How many messages (oldest first) to return. Default 25, max 100. The header states the full held count and the range shown. |
| offset | integer | – | Skip this many messages before returning, for paging through a long thread. |
No output schema declared.
No examples provided.
get_network_state ~100
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).
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max packages (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. |
| query | string | – | Optional substring filter on package name. |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pr_number | integer | yes | PR number in canton-foundation/canton-dev-fund. |
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.