# io.github.UnityNodes/canton-ccpedia

- Registry name: `io.github.UnityNodes/canton-ccpedia` · version 1.0.1
- Categories (automatic, keyword rules): Code & repositories, Developer tools, Crypto & blockchain, Finance & markets
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.UnityNodes%2Fcanton-ccpedia
- Server page: https://mcpstation.net/s/io.github.UnityNodes--canton-ccpedia.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://ccpedia.xyz/mcp`

## Tools (as reported by the server, not verified)

- `search`: 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\_s
- `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\_cip\_vote\_outcome instead: reading the proposal text does not
- `list\_cips`: Browse Canton Improvement Proposals \(CIPs\), optionally filtered by status \(Draft, Early Draft, In Review, Proposed, Approved, Active, Final, Withdrawn, Rejected, Replaced, Obsolete, Pending\) and type \(e.g. "Standards Track"\). Returns a metadata list \(id, title, status, type, author\). Not full text.
- `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 cached forum index. This is the WEB FORUM. For GitHub Discuss
- `get\_whitepaper`: 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.
- `list\_whitepapers`: List every Canton Network whitepaper indexed by CCPEDIA, returning slug, title, description, tag and page count \(metadata only, no body\). Use the returned slug with get\_whitepaper to fetch full content. Canton-only.
- `get\_trending`: 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 chang
- `get\_radar`: 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.
- `get\_proposals`: 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\). Return
- `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, flags, and full sections a search snippet truncates. Requi
- `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 body \(get\_cip\) or vote tallies \(get\_cip\_votes\). Canton ecos
- `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 proposal ITSELF as a PDF and leave only a header block in markd
- `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 'who is discussing CIP-X and where' / impact questions. Return
- `get\_recent\_changes`: 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 cha
- `get\_network\_stats`: 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
- `get\_token\_market`: 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 CC
- `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 Global Synchronizer Scan registry\); every other asset's supp
- `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 \(that one also lists Cantex, which this tool does not cover
- `list\_ecosystem\_projects`: 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\_network\_state`: 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 dat
- `list\_repos`: 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 N
- `list\_github\_discussions`: 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 repo
- `get\_github\_discussion`: 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
- `get\_video`: Get a Canton Network video that CCPEDIA has cached \(curated channels: Canton Network, Digital Asset, Sync Insights, Canton Foundation, Daml\) by its YouTube id: title, channel, publish date, description and full transcript text if stored. CANTON-ONLY and limited to videos already in CCPEDIA's index.
- `list\_videos`: List Canton Network videos cached in CCPEDIA, filtered by channel \(Canton Network, Digital Asset, Sync Insights, Canton Foundation, Daml\), publish date \(since\), and transcript availability. CANTON-ONLY corpus. These are curated Canton ecosystem videos, not general YouTube. Returns metadata only \(id,
- `get\_validator\_fleet`: 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
- `get\_validator`: 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
- `get\_upcoming\_deadlines`: 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
- `list\_governance\_votes`: 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 th
- `get\_governance\_vote`: 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 d
- `list\_votes\_by\_sv`: 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'.
- `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-list tools cannot: get\_cip\_votes reads the discussion on the ci
- `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 is the message thread, NOT a pre-computed count; the first m
- `list\_mailing\_threads`: 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.
- `get\_mailing\_thread`: 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 Gi
- `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 snippets \(not the curated knowledge base\). Canton-only. Use when a
- `semantic\_search`: PRIMARY tool for open-ended questions: how / why / what-is, troubleshooting a symptom \("why is my balance zero", "how do I fix X"\), and locating config or setup steps. Conceptual/meaning-based search over the full Canton corpus \(CIPs, docs, forum, mailing lists, proposals, blog, releases, ecosystem,
- `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 tool or package to a developer. Accepts either one name or a b
- `get\_started\_guide`: 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,
- `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. Returns the 3 NEAREST FAQ entries, which may not exactly matc
- `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, REST, or non-Canton APIs. Use when the user names one of the
- `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-to-concept translations; use get\_started\_guide for a full EVM
- `migrate\_lookup`: 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.
- `list\_deprecations`: 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 specif
- `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 joins: github\_releases \(latest stable tag per repo\) + mailin
- `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 forum posts \(not just topic count\), individual mailing-list
- `get\_kb\_drift`: 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, network\_state\). Returns each drifted \(category, key\) with the KB value, the live value derived right now,
- `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 literal error string or code \(e.g. TOPOLOGY\_TOO\_MANY\_PENDING
- `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 and asks "what breaks moving from X to Y?". Pass version str
- `get\_recurring\_issue\_fingerprint`: 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/Spl
- `list\_featured\_apps`: 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, u
- `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 null when only the Scan API source is available.
- `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.
- `get\_upgrade\_status`: 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 v
- `get\_sv\_schedule`: 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 Splic
- `get\_upcoming\_operations`: 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.
- `get\_recent\_deployments`: 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?".
- `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 approved CIPs \("CIP-0112", "0112"\) and dev-fund PR drafts \("PR-203
- `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, withdrawn and rejected are not distinguished; no close dates are s
- `get\_sdk\_changelog`: 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.
- `search\_community`: 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.
- `search\_github\_issues`: 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\).
- `search\_talks`: Search CCPEDIA's indexed Canton talks/videos \(YouTube transcripts\). Canton-specific. Returns matches across title + transcript with a short snippet around the hit.
- `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, or how-to steps, and returns nothing when no open issue matc
- `find\_cip\_for\_feature`: Given a Canton feature or capability description, find the matching CIP\(s\) by the words of their titles and bodies and by meaning over the CIP index. Canton-specific. Use to answer "is there a CIP for X?".
- `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.
- `get\_latest\_release`: 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 cant
- `search\_release\_notes`: Search across release-notes bodies of all indexed Canton repos for a feature/keyword. Canton-specific. Use to find which release first mentioned X.
- `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.
- `get\_npm\_packages`: List the indexed Canton/Daml npm packages \(sdk\_versions registry=npm\) optionally filtered by name. Canton-specific.
- `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; to also check pending/past Dev Fund proposals for the same
- `search\_mailing\_list`: Search across CCPEDIA's indexed Canton mailing-list archives \(cip-discuss, cip-vote, grants-discuss, validator-announce, etc\). Canton-specific.
- `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.
- `get\_issue\_status`: Look up one GitHub issue or PR by repo + number. Canton/Daml/Splice repos only.
- `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.
- `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.
- `get\_proposal\_milestones`: For one Canton Dev Fund proposal PR, list any related milestone tracking issues \(issues whose body or title references the PR number\). Canton-specific.
- `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 "where the ecosystem needs help". For per-category funding levels
- `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 the live ecosystem directory. Canton-specific. Cuts manual c
- `proposal\_success\_predictor`: 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.
- `list\_rfps`: 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 p
- `find\_rfp\_for\_idea`: Given a project idea, find which Canton Dev Fund RFP\(s\) it fits and how crowded that area is. Matches the idea against the RFP texts in the 2026-2028 roadmap \(shared terms, shown\), then for the best fits shows what the Foundation asks for, its stated appetite for grants, and the proposals that decla
- `list\_proposals\_needing\_champion`: 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
- `get\_proposal`: 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, mile
- `get\_proposal\_discussion`: 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
- `get\_proposal\_file`: 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. C
- `search\_dev\_fund`: 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
- `get\_dev\_fund\_activity`: What happened in the Canton Dev Fund lately, newest first: new comments and reviews with a snippet, and \(optionally\) timeline events such as labels added, reviewers requested, proposals renamed, merged, closed or moved on the project board. Use for "what is going on in the Dev Fund", "what did the c
- `get\_dev\_fund\_lifecycle`: How Canton Dev Fund proposals actually move through the Foundation project board, from the recorded column history: the funnel \(how many reach each column\), median and p90 days in each column, time to decision, time to the first human response, how many open proposals wait on the applicant, the comm
- `list\_stuck\_proposals`: 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
- `find\_duplicate\_proposals`: Find Canton Dev Fund proposals that duplicate, re-file or overlap each other, from the proposal files compared by meaning plus identical text, title, author and organization. Without a number it lists groups \(for example the same text filed twice, a team re-filing under Dev Fund 2.0, two teams build
- `get\_dev\_fund\_person`: Who is this person in the Canton Dev Fund, by GitHub login: their SIG memberships and organization \(from the SIG directory\), the proposals they authored, how much they comment and review \(and how often they approve or request changes\), which proposals asked them to review, which they were assigned,
- `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 words, even if that topic happens to be a known CIP's nickname \(
- `community\_consensus`: Surface signals of what the Canton community thinks about a topic: the forum threads that match it best by meaning \(views, replies, distinct participants\), the mailing-list threads that match best with how many messages mention every term, and the first reply on the best-matching thread. Canton-spec
- `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.
- `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 foundation\_kb to live releases\).
- `learning\_path`: 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\).
- `outdated\_guidance\_detector`: 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.
- `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?".
- `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.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html