Home / MCP registry index / io.github.UnityNodes/canton-ccpedia

io.github.UnityNodes/canton-ccpedia

io.github.UnityNodes/canton-ccpedia in the official MCP registry. Endpoint https://ccpedia.xyz/mcp. Source: github.com/UnityNodes/ccpedia.

The registry describes it as: Canton Network: CIPs and their on-chain vote outcomes, docs, forum, validator upgrade deadlines.

We read its 104 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http canton-ccpedia https://ccpedia.xyz/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "canton-ccpedia": {
      "url": "https://ccpedia.xyz/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"canton-ccpedia","type":"http","url":"https://ccpedia.xyz/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

search get_cip list_cips get_discussion get_whitepaper list_whitepapers get_trending get_radar get_proposals get_doc get_cip_history get_cip_attachments get_cip_mentions get_recent_changes get_network_stats get_token_market get_asset_supply get_defi_pools list_ecosystem_projects get_network_state list_repos list_github_discussions get_github_discussion get_video list_videos get_validator_fleet get_validator get_upcoming_deadlines list_governance_votes get_governance_vote list_votes_by_sv get_cip_vote_outcome get_cip_votes list_mailing_threads get_mailing_thread get_foundation_info semantic_search check_deprecation get_started_guide get_faq get_api_reference compare_to_evm migrate_lookup list_deprecations get_current_versions get_cip_citations get_kb_drift diagnose_error get_breaking_changes get_recurring_issue_fingerprint list_featured_apps get_app_metrics find_apps_by_pattern get_upgrade_status get_sv_schedule get_upcoming_operations get_recent_deployments detect_cip_dependency_chain compare_governance_outcomes get_sdk_changelog and 44 more

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-unitynodes-canton-ccpedia/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-unitynodes-canton-ccpedia)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.