CCPEDIAdocs
MCP tools

MCP tool reference

Every CCPEDIA MCP tool. Auto-generated from the live registry.

CCPEDIA exposes 90 MCP tools to AI clients at https://ccpedia.xyz/mcp. They cover every Canton developer surface.

This page is auto-generated. The per-tool sections below reflect /mcp tools/list as of the last sync; the count above is read live on every render, so it stays right even between syncs.

Search

Full-text and semantic search across every synced Canton source. Covers the forum, GitHub, docs, CIPs, mailing lists, videos, blog, whitepapers, and the ecosystem registry. (17 tools).

CIPs

Canton Improvement Proposals. Lookup, status, votes, citations, dependency chains, governance comparisons, on-chain DSO governance votes. (14 tools).

Forum and community

Live Canton developer forum. Discussions, trending topics, expert discovery, consensus detection. (4 tools).

Code and errors

Diagnose errors, find code samples, surface breaking changes and known issues across the Canton stack. (4 tools).

Releases and SDKs

Track Canton, Splice, and Daml SDK versions. Release notes, npm packages, deprecation status, upgrade verdicts. Everything you need before bumping a version. (10 tools).

Featured apps and SV

Live Featured Apps from the Scan API, the Super Validator operations calendar, and the DSO validator registry. Schedules, freezes, upgrades, releases, validator lookups. (13 tools).

Dev Fund

Canton Dev Fund proposal intelligence. Open asks, milestones, builder overlap detection, success prediction. (5 tools).

Onboarding and drift

Get started fast, follow a learning path, see where curated KBs drift from live Canton state. (7 tools).

Talks, docs, and mail

Canton YouTube talks, official documentation, whitepapers, the foundation knowledge-base, and four Canton mailing lists. (8 tools).

Ecosystem

Canton ecosystem projects. Similarity search, collaboration matching, dependency graph, gap detection, Canton MCP directory and federation. (8 tools).

Calling a tool

curl -X POST https://ccpedia.xyz/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Client-specific config snippets live in Integrations.

On this page