Polymarket and Predict.fun historical tick data, plus backtest quotes and status, over MCP
Nothing to run from here
Canton Ccpedia is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
102
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Canton Network: CIPs and their on-chain vote outcomes, docs, forum, validator upgrade deadlines.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http canton-ccpedia-mcp https://ccpedia.xyz/mcp
# 2 — ask your agent for something these tools do
# search, get_cip, list_cips and 99 more
Canton Ccpedia costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
UNAll 2 servers
UnityNodes2 servers
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http canton-ccpedia-mcp https://ccpedia.xyz/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
102 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 yo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query |
| type | string | no | Restrict results to one source type; "governance" is the stated reasoning behind an on-chain DSO vote; "all" searches everything |
| limit | integer | no | Max results to return (1-50) |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
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 multip
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | CIP ID: "0001", "CIP-0042", or "PR-0117" |
Browse Canton Improvement Proposals (CIPs), optionally filtered by status (Draft, Early Draft, In Review, Proposed, Approved, Active, Final, Withdrawn, Rejected, Replaced, Obsolete, Pending) and type (e.g. "Standards Track"). Returns a metadata list (id, title, status, type, author). Not full text. Use to discover or enumerate CIPs when you don't have a specific ID; use get_cip to read one. Canton
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | — |
| type | string | no | Type filter, e.g. "Standards Track" |
| limit | integer | no | How many CIPs to return. Default 20, max 100. The response states the full count, which can exceed this limit; page with offset. |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Whitepaper slug, e.g. "canton-network-whitepaper" |
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.
No parameter schema on file.
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.
No parameter schema on file.
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 Ca
| Parameter | Type | Required | Notes |
|---|---|---|---|
| level | string | no | Severity floor. "critical" and "important" return only that level; "ecosystem" is the low-severity feed; "all" (default) returns every live alert. |
| limit | integer | no | How many alerts to return, most severe and most recent first. Default 25. |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | Grant-request state on GitHub. Defaults to "open", so the total reported is open requests rather than every proposal ever filed. |
| limit | integer | no | How many proposals to return. Default 20, max 50. The response states the full count. |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | CIP ID: "0001", "CIP-0042", or "PR-0117" |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | CIP ID: "0001", "CIP-0042" |
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 an
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | CIP ID: "0001", "CIP-0042", or "PR-0117" |
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'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | How far back to look, in days, counted from now. Default 7, max 90. |
| limit | integer | no | How many changes to return, newest first. Default 50, max 500. |
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_m
No parameter schema on file.
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.
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | no | Slug or symbol to filter to one asset, e.g. "cbtc", "CBTC", "canton-coin", or "CC". Case-insensitive. Omit for all seven. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| protocol | string | no | Restrict to one DEX. Omit for all three. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Filter by category (e.g. "DeFi", "Wallets", "NaaS") |
| query | string | no | Search in title/description/tags |
| liveness | string | no | 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. |
| limit | integer | no | How many projects to return. Default 30, max 100. The response states the full count. |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
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_t
No parameter schema on file.
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).
No parameter schema on file.
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_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | Filter by owner/name as shown in the unfiltered listing. Repos get transferred, so read the value from a result rather than assuming one. |
| category | string | no | Filter by Discussions category, e.g. "Q&A", "Ideas" |
| limit | integer | no | How many discussions to return, newest first. Default 15, max 50. |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | GitHub GraphQL node ID, e.g. "D_kwDOMNgu5s4AY..." |
Get a Canton Network video that CCPEDIA has cached (curated channels: Canton Network, Digital Asset, Sync Insights, Canton Foundation, Daml) by its YouTube id: title, channel, publish date, description and full transcript text if stored. CANTON-ONLY and limited to videos already in CCPEDIA's index. Does NOT fetch arbitrary YouTube videos (use a dedicated YouTube tool for that). Obtain ids from lis
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | YouTube video id, e.g. "dQw4w9WgXcQ" |
| transcript_chars | integer | no | Transcript characters to return. Default 12000; raise it (max 200000) for the full text, or set 0 for metadata only. |
List Canton Network videos cached in CCPEDIA, filtered by channel (Canton Network, Digital Asset, Sync Insights, Canton Foundation, Daml), publish date (since), and transcript availability. CANTON-ONLY corpus. These are curated Canton ecosystem videos, not general YouTube. Returns metadata only (id, title, channel, date); call get_video with an id for the transcript.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| channel | string | no | Channel name filter, e.g. "Canton Network", "Digital Asset", "Sync Insights", "Canton Foundation", "Daml". Case-insensitive substring. |
| since | string | no | Earliest published_at (ISO date, e.g. "2026-01-01"). Default: no lower bound. |
| has_transcript | boolean | no | If true, only return videos with a stored transcript. If false, only those still missing one. Omit for both. |
| limit | integer | no | How many videos to return. Default 20, max 100. |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
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 e
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version | string | no | Your Splice version, e.g. "0.6.9", to locate it in the distribution. |
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",
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Validator name or party id, whole or partial, e.g. "GSF-validator-2" or "MPCH". |
| limit | integer | no | Maximum matches to return (default 10, max 50). |
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 d
| Parameter | Type | Required | Notes |
|---|---|---|---|
| environment | string | no | "MainNet", "TestNet" or "DevNet". Omit for all networks. |
| days | integer | no | How far ahead to look, in days. Default 30. |
| validator_only | boolean | no | Only events that require a validator operator to act. |
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 A
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max rows (default 20). |
| action | string | no | Filter by action, e.g. "SRARC_GrantFeaturedAppRight", "SRARC_RevokeFeaturedAppRight", "SRARC_UpdateSvRewardWeight", "SRARC_OffboardSv". |
| outcome | string | no | Filter by outcome. Omit for all outcomes; there is no "all" value. |
| status | string | no | "open" for votes still in flight, "closed" for decided ones. Omit for both; there is no "all" value. |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tracking_cid | string | yes | The vote request tracking contract id, or a unique prefix of it, as returned by list_governance_votes. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sv_name | string | no | Super Validator short name, e.g. "Tradeweb-Markets-1", "Digital-Asset-1", "Cumberland-1". Omit for all of them. |
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 r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cip_id | string | yes | CIP id, e.g. "CIP-0116", "116", "0116". |
| limit | integer | no | How many vote requests to return, newest first. Default 20, max 100. The response states the full count either way. |
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 ge
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cip_id | string | yes | CIP id, e.g. "0117", "0118", or "CIP-0117". Numeric form preferred. |
| limit | integer | no | How many messages (oldest first) to return. Default 25, max 100. The header states the full count and the range shown. |
| offset | integer | no | Skip this many messages before returning, for paging through a long vote thread. |
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). Retur
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group | string | no | Restrict to one of the 7 indexed groups. |
| cip_id | string | no | CIP number filter, e.g. "0117". Returns only threads tagged with this CIP. |
| since | string | no | Earliest last_post_at ISO date. |
| limit | integer | no | How many threads to return. Default 20, max 100. |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 | no | How many messages (oldest first) to return. Default 25, max 100. The header states the full held count and the range shown. |
| offset | integer | no | Skip this many messages before returning, for paging through a long thread. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Free-text topic, e.g. "team", "executive director", "working groups", "membership", "grants", "board". |
| limit | integer | no | How many matching sections to return. Default 3, max 10. |
PRIMARY tool for open-ended questions: how / why / what-is, troubleshooting a symptom ("why is my balance zero", "how do I fix X"), and locating config or setup steps. Conceptual/meaning-based search over the full Canton corpus (CIPs, docs, forum, mailing lists, proposals, blog, releases, ecosystem, foundation KB, YouTube) using vector+FTS hybrid retrieval with reranking. Canton-specific. Use this
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-form question or phrase. |
| source_types | array | no | Restrict to these source types. "proposal" is a Dev Fund grant request; "github_item" is an ordinary issue or PR from any other indexed repo; "sdk_version" is a released package version from the npm/D |
| limit | integer | no | How many chunks to return. Default 6, max 15. Capped at 2 per document so one long file cannot take every slot. |
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 (wit
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
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 Can
| Parameter | Type | Required | Notes |
|---|---|---|---|
| background | string | yes | Developer's primary background. Ask the user to select this before proceeding. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | Developer's question, e.g. "how do I install", "create party", "deploy to testnet". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api | string | yes | Which API to look up. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| concept | string | yes | EVM concept, e.g. "smart contract", "wallet", "gas", "ERC20", "Hardhat", "Remix", "ABI". |
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_d
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | The deprecated command, package, or tool name to look up. Best-match search. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Kind of thing deprecated. "all" (default) returns every category. |
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 snapsho
No parameter schema on file.
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 +
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cip_id | string | yes | CIP id, e.g. "CIP-0056", "0056", "PR-0117". Padded or unpadded both accepted. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| refresh | boolean | no | If true, re-run the validator before returning the report. Default false uses the most recent stored findings. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| error_text | string | yes | Error message, stack trace, or status code. Longer/more distinctive text returns better matches. |
| limit | integer | no | Max matches per source (default 3). |
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").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_sdk | string | yes | Origin version, e.g. "0.5.0" or "v3.4.0". |
| to_sdk | string | yes | Target version, e.g. "0.6.10" or "v3.5.6". |
| repo | string | no | Optional repo hint: "canton", "splice" (alias for decentralized-canton-sync), "daml", or a full owner/name. Auto-inferred from version shape when omitted. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| window_months | integer | no | Look-back window in months (default 18). |
| min_months | integer | no | A keyword must appear in this many distinct months to count as recurring (default 3). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Filter by category, e.g. "Validator", "DeFi", "Tokenized Assets" (case-insensitive substring match). |
| sort | string | no | Sort key (default: recent). |
| limit | integer | no | Max rows (default 25). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | string | yes | Featured-app contract id, or a unique prefix of it as shown by list_featured_apps. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pattern | string | yes | Free text, e.g. "AMM", "wallet", "DeFi vault", "validator". |
| limit | integer | no | Max rows (default 10). |
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?", "w
| Parameter | Type | Required | Notes |
|---|---|---|---|
| environment | string | yes | Which network the node runs on. |
| version | string | no | Splice version the node currently runs, e.g. "0.6.9". Omit to get the schedule without a verdict. |
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?".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| environment | string | no | Restrict to one environment. Omit for all. |
| upcoming_only | boolean | no | If true (default), only events with start_at >= today. |
| limit | integer | no | Max rows (default 20). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Days ahead to look (1-180, default 30). |
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?".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many deployments to return, newest first. Default 10, max 50. |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cip_id | string | yes | Starting CIP or PR id, e.g. "0112", "CIP-0112", or "PR-203". |
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?".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| window_days | integer | no | Window in days, 7-365 (default 90). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version | string | yes | Version tag, e.g. "3.5.6", "v3.5.6", "0.6.10". |
| repo | string | no | Optional repo hint: canton, daml, dpm, splice. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text query. |
| limit | integer | no | Max hits per source (default 5). |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text query. |
| state | string | no | Issue state filter (default: all). |
| limit | integer | no | Max rows (default 10). |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
Search CCPEDIA's indexed Canton talks/videos (YouTube transcripts). Canton-specific. Returns matches across title + transcript with a short snippet around the hit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text query. Appears in title or transcript. |
| limit | integer | no | Max rows (default 5). |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | yes | What you're seeing. Short prose, not a stack trace (for that use diagnose_error). |
| limit | integer | no | Max rows per source (default 5). |
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?".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feature | string | yes | Feature description, e.g. "wallet abstraction", "token standard", "validator staking". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cip_id | string | yes | CIP id, e.g. "0112", "CIP-0112", "PR-0088". |
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 M
| Parameter | Type | Required | Notes |
|---|---|---|---|
| package | string | yes | Repo or package name: "canton", "daml", "dpm", "splice", or a full owner/repo. |
Search across release-notes bodies of all indexed Canton repos for a feature/keyword. Canton-specific. Use to find which release first mentioned X.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feature | string | yes | Feature keyword, e.g. "logical synchronizer", "topology", "wallet kernel". |
Surface release notes likely to contain security or CVE fixes. Canton-specific. Heuristic: matches release bodies containing security / CVE / vulnerability / patch keywords.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max rows (default 10). |
List the indexed Canton/Daml npm packages (sdk_versions registry=npm) optionally filtered by name. Canton-specific.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Optional substring filter on package name. |
| limit | integer | no | Max packages (default 25). |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | yes | Project description / idea. |
| limit | integer | no | Max rows (default 10). |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
Search across CCPEDIA's indexed Canton mailing-list archives (cip-discuss, cip-vote, grants-discuss, validator-announce, etc). Canton-specific.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text query. Appears in subject or body. |
| group | string | no | Optional group_slug filter, e.g. "cip-discuss". |
| limit | integer | no | Max rows (default 10). |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Topic keyword, e.g. "topology", "wallet", "DAR upload". |
Look up one GitHub issue or PR by repo + number. Canton/Daml/Splice repos only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | yes | Repo, e.g. "canton-foundation/canton-dev-fund" or shorthand "canton-dev-fund". |
| number | integer | yes | Issue or PR number. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Topic keyword. |
| limit | integer | no | Max rows (default 5). |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Optional label filter, e.g. "daml-tooling", "node-deployment-operations". |
For one Canton Dev Fund proposal PR, list any related milestone tracking issues (issues whose body or title references the PR number). Canton-specific.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pr_number | integer | yes | PR number in canton-foundation/canton-dev-fund. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max rows per gap type (default 5). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| idea | string | yes | One-paragraph project idea or capability description. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| draft_text | string | yes | Full draft text. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | integer | no | RFP number to read in full, e.g. 18. Omit to list every RFP. |
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 declare the RFP. Also shows the existing Dev Fund proposals closest to the idea by text whether or not th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| idea | string | yes | One-paragraph project idea or capability description. |
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 champ
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rfp | integer | no | Only proposals that declare this RFP number (label, PR text, title or proposal file). |
| limit | integer | no | How many proposals to return. Default 20, max 50. The response states the full count. |
| offset | integer | no | Skip this many before returning, for paging past the limit. |
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,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | integer | yes | PR (or issue) number in canton-foundation/canton-dev-fund, e.g. 439. |
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-specifi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | integer | yes | PR (or issue) number in canton-foundation/canton-dev-fund. |
| kind | string | no | Only this kind: issue_comment (conversation), review_comment (inline on the file), review (a formal review verdict). |
| limit | integer | no | How many entries to return. Default 10, max 30. The response states the full count. |
| offset | integer | no | Skip this many entries, for paging. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | integer | yes | PR number in canton-foundation/canton-dev-fund. |
| path | string | no | One of the paths listed for that PR. Omit for the first file. |
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 lexica
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Words to look for, e.g. "indexer champion" or "volatility amendment". In mode "meaning", a plain-language question or phrase. |
| mode | string | no | 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. |
| scope | string | no | all, comments (comments + reviews + inline review comments), proposal_files, or descriptions (titles and descriptions of pull requests and tracking issues). |
| author | string | no | GitHub login; limits comments and PR descriptions to that person. |
| limit | integer | no | How many hits to return. Default 10, max 30. |
| offset | integer | no | Skip this many hits, for paging. |
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 committee say this week", "which proposals just got reviewed". Canton-specific.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Look back this many days. Default 7, max 120. |
| include_events | boolean | no | Also list timeline events (labels, reviewer requests, renames, board moves). Default true. |
| limit | integer | no | How many entries. Default 20, max 50. |
| offset | integer | no | Skip this many entries, for paging. |
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 committee, a vote or nobody, bot labels against the board, and steps back. Pass number for one proposal:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | integer | no | A proposal (PR) number: its own history instead of the overview. |
| view | string | no | overview (default) or flow (weekly numbers). Ignored when number is given. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| waiting_on | string | no | Only proposals whose next step is on this side. |
| stuck_days | integer | no | Idle for at least this many days. Default 30. |
| limit | integer | no | How many proposals. Default 20, max 50. The response states the full count. |
| offset | integer | no | Skip this many, for paging. |
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 building the same indexer), by default only groups with an open proposal; with a number it lists the clos
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | integer | no | A proposal (PR) number: list the proposals closest to it instead of listing groups. |
| relations | array | no | Only these relations. Default: exact-duplicate, likely-duplicate, likely-resubmission and overlap, the same set the Dev Fund Navigator page counts. likely-amendment (maintainer edits), same-applicant- |
| scope | string | no | open (default): groups with at least one open proposal. all: every group, closed ones too. |
| min_similarity | number | no | Raise the similarity floor, 0 to 1 on the proposal-file comparison. Defaults are the validated thresholds. |
| limit | integer | no | How many groups or neighbours. Default 10, max 30. The response states the full count. |
| offset | integer | no | Skip this many groups, for paging. |
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, and where a champion line names them. Use to judge who a possible champion or reviewer is and how re
| Parameter | Type | Required | Notes |
|---|---|---|---|
| login | string | yes | GitHub login, e.g. "waynecollier-da" or "srikanth-bitdynamics". |
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 speci
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Topic / question. |
| limit_per_source | integer | no | Max rows per source (default 3). |
Surface signals of what the Canton community thinks about a topic: the forum threads that match it best (views, replies, distinct participants), mailing list debate volume, and the first reply on the best-matching thread. Canton-specific. Not sentiment-analysis; a structured roundup the caller can summarise.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Topic to assess. |
Rank likely Canton experts on a topic across CCPEDIA: forum activity matching the topic, plus overall forum/GitHub volume of that author. Canton-specific.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Topic / domain to find experts for. |
| limit | integer | no | Max authors (default 5). |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Topic to cross-check. |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| goal | string | yes | What the learner wants to do, e.g. "build a Canton dApp", "operate a validator", "write a CIP". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Topic to scan. |
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?".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Topic / category / project family. |
Given one Canton ecosystem project, find others with complementary tags/category that could plug in. Canton-specific. Lightweight heuristic: overlap of tags + adjacent categories.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project name or slug to look around. |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 |
| arguments | object | no | Arguments object for that tool |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Canton Ccpedia or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Canton Ccpedia can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.