io.github.UnityNodes/canton-ccpedia is an MCP server with 90 tools an agent can call, among them call_canton_mcp, check_deprecation, community_consensus. It answers at https://ccpedia.xyz/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 21 October 2026, succeeded.
Canton Network: CIPs and their on-chain vote outcomes, docs, forum, validator upgrade deadlines.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
call_canton_mcp | 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; Inputs: server, tool, arguments |
check_deprecation | 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 to Inputs: name |
community_consensus | 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 calle Inputs: topic |
compare_governance_outcomes | 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, withdr Inputs: window_days |
compare_to_evm | 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-t Inputs: concept |
detect_builder_overlap | 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 Inputs: idea |
detect_cip_dependency_chain | 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 approv Inputs: cip_id |
detect_drift | 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 Inputs: topic |
diagnose_error | 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 Inputs: error_text, limit |
ecosystem_dependency_graph | 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?". Inputs: topic |
find_apps_by_pattern | 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. Inputs: pattern, limit |
find_cip_for_feature | 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?". Inputs: feature |
find_code_examples | 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. Inputs: topic, limit, offset |
find_collaboration_opportunities | Given one Canton ecosystem project, find others with complementary tags/category that could plug in. Canton-specific. Lightweight heuristic: overlap of tags + adjacent categories. Inputs: project |
find_expert | Rank likely Canton experts on a topic across CCPEDIA: forum activity matching the topic, plus overall forum/GitHub volume of that author. Canton-specific. Inputs: topic, limit |
find_known_issues | 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, Inputs: description, limit |
find_maintainer_guidance | 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. Inputs: topic |
find_security_patches | Surface release notes likely to contain security or CVE fixes. Canton-specific. Heuristic: matches release bodies containing security / CVE / vulnerability / patch keywords. Inputs: limit |
find_similar_projects | 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 Inputs: description, limit, offset |
full_context | 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 word Inputs: topic, limit_per_source |
get_api_reference | 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, Inputs: api |
get_app_metrics | 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 Inputs: app_id |
get_asset_supply | 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 Inputs: asset |
get_breaking_changes | 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 Inputs: from_sdk, to_sdk, repo |
get_cip | 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_ Inputs: id |
get_cip_attachments | 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 pro Inputs: id |
get_cip_citations | 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 Inputs: cip_id |
get_cip_history | 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 Inputs: id |
get_cip_implementation_status | 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. Inputs: cip_id |
get_cip_mentions | 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 'w Inputs: id |
get_cip_vote_outcome | 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-lis Inputs: cip_id, limit |
get_cip_votes | 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 Inputs: cip_id, limit, offset |
get_current_versions | 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 |
get_defi_pools | 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 Inputs: protocol |
get_discussion | 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 c Inputs: id |
get_doc | 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 Inputs: id |
get_ecosystem_gaps | 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 "wher Inputs: limit |
get_faq | 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. R Inputs: question |
get_foundation_info | 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 snippe Inputs: topic, limit |
get_funding_landscape | 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. Inputs: category |
get_github_discussion, get_governance_vote, get_issue_status, get_kb_drift, get_latest_release, get_mailing_thread, get_network_state, get_network_stats, get_npm_packages, get_proposal_milestones, get_proposals, get_radar, get_recent_changes, get_recent_deployments, get_recurring_issue_fingerprint, get_sdk_changelog, get_started_guide, get_sv_schedule, get_token_market, get_trending, get_upcoming_deadlines, get_upcoming_operations, get_upgrade_status, get_validator, get_validator_fleet, get_video, get_whitepaper, learning_path, list_canton_mcps, list_cips, list_deprecations, list_ecosystem_projects, list_featured_apps, list_github_discussions, list_governance_votes, list_mailing_threads, list_repos, list_videos, list_votes_by_sv, list_whitepapers, migrate_lookup, outdated_guidance_detector, proposal_success_predictor, search, search_community, search_github_issues, search_mailing_list, search_release_notes, search_talks, semantic_search
Every block below points at https://ccpedia.xyz/mcp. Pick your client and copy.
claude mcp add --transport http io-github-unitynodes-canton-ccpe https://ccpedia.xyz/mcp
{
"mcpServers": {
"io-github-unitynodes-canton-ccpe": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://ccpedia.xyz/mcp"]
}
}
}{
"mcpServers": {
"io-github-unitynodes-canton-ccpe": {
"url": "https://ccpedia.xyz/mcp"
}
}
}{
"servers": {
"io-github-unitynodes-canton-ccpe": {
"type": "http",
"url": "https://ccpedia.xyz/mcp"
}
}
}{
"context_servers": {
"io-github-unitynodes-canton-ccpe": {
"url": "https://ccpedia.xyz/mcp"
}
}
}{
"mcpServers": {
"io-github-unitynodes-canton-ccpe": {
"serverUrl": "https://ccpedia.xyz/mcp"
}
}
}{
"mcpServers": {
"io-github-unitynodes-canton-ccpe": {
"url": "https://ccpedia.xyz/mcp"
}
}
}name: io.github.UnityNodes/canton-ccpedia
version: 0.0.1
schema: v1
mcpServers:
- name: io.github.UnityNodes/canton-ccpedia
type: streamable-http
url: https://ccpedia.xyz/mcp{
"mcpServers": {
"io-github-unitynodes-canton-ccpe": {
"httpUrl": "https://ccpedia.xyz/mcp"
}
}
}{
"mcpServers": {
"io-github-unitynodes-canton-ccpe": {
"type": "http",
"url": "https://ccpedia.xyz/mcp"
}
}
}{
"mcpServers": {
"io-github-unitynodes-canton-ccpe": {
"url": "https://ccpedia.xyz/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fccpedia.xyz%2Fmcp&type=streamable_http&id=io-github-unitynodes-canton-ccpe&name=io.github.UnityNodes/canton-ccpedia
It answered our last check on 21 October 2026 in 328 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
90, as returned by the server's own tools/list on 13 September 2026: call_canton_mcp, check_deprecation, community_consensus, compare_governance_outcomes, compare_to_evm, detect_builder_overlap, detect_cip_dependency_chain, detect_drift, and 82 more.
It answered our last check on 21 October 2026 in 328 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://ccpedia.xyz/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.unitynodes. Endpoint host: ccpedia.xyz. ARD identifier: urn:air:io.github.unitynodes:mcp:canton-ccpedia.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.