Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.UnityNodes/canton-ccpedia

REMOTE · CCPEDIA.XYZ

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

Available components

0 this week 76 Trust /100

Last scanned (16 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability47
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 15944 tokens (~143/item across 111 items; 104 tools + 7 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 104 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 106 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 28 Oct 26 0
    • Tool “list_cips” rewrote its description, which is the text the model reads security
  • 27 Oct 26 0
    • New tool “get_blog_post” functional
    • New tool “list_blog_posts” functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://ccpedia.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ccpedia.xyz CN=YE2,O=Let's Encrypt,C=US 4 Nov 2026 2 Feb 2027 ECDSA 256 ECDSA-SHA384 57da946b6bd4892269922e8a9b6781f6f02
SANs: *.ccpedia.xyz, ccpedia.xyz
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ccpedia.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
xyz. DS published 3599, 18130 8, 8 Verified
ccpedia.xyz. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ccpedia.xyz/mcp Verified 200
http (plaintext) http://ccpedia.xyz/mcp HTTPS enforced 301 https://ccpedia.xyz/mcp
MCP tools · 104 exposed · ~15,339 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
search_mailing_list ~121

Search across CCPEDIA's indexed Canton mailing-list archives (cip-discuss, cip-vote, grants-discuss, validator-announce, etc). Canton-specific.

NameTypeReqDescription
groupstring–Optional group_slug filter, e.g. "cip-discuss".
limitinteger–Max rows (default 10).
offsetinteger–Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
querystringyesFree-text query. Appears in subject or body.

No output schema declared.

No examples provided.

search_release_notes ~63

Search across release-notes bodies of all indexed Canton repos for a feature/keyword. Canton-specific. Use to find which release first mentioned X.

NameTypeReqDescription
featurestringyesFeature keyword, e.g. "logical synchronizer", "topology", "wallet kernel".

No output schema declared.

No examples provided.

search_talks ~113

Search CCPEDIA's indexed Canton talks/videos (YouTube transcripts). Canton-specific. Returns matches across title + transcript with the best-matching passage, its time in the video and a link that opens the video there.

NameTypeReqDescription
limitinteger–Max rows (default 5).
offsetinteger–Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
querystringyesFree-text query. Appears in title or transcript.

No output schema declared.

No examples provided.

semantic_search ~308

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 FIRST for anything a specific tool does not clearly own; the narrow curated tools (get_faq, find_known_issues, diagnose_error) cover only small hand-picked sets or need a literal error string, so prefer semantic_search for real how/why/config questions. Then call get_doc with a returned id to read the full source page.

NameTypeReqDescription
limitinteger–How many chunks to return. Default 6, max 15. Capped at 2 per document so one long file cannot take every slot.
querystringyesFree-form question or phrase.
source_typesarray–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/…

No output schema declared.

No examples provided.

Install

How do I install the io.github.UnityNodes/canton-ccpedia MCP server?

io.github.UnityNodes/canton-ccpedia is a hosted endpoint at https://ccpedia.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · ccpedia.xyz

# add to Claude Code
claude mcp add --transport http unitynodes-canton-ccpedia 'https://ccpedia.xyz/mcp'
Common questions

What is the io.github.UnityNodes/canton-ccpedia MCP server?

io.github.UnityNodes/canton-ccpedia is an MCP server listed in the public MCP registry as io.github.UnityNodes/canton-ccpedia. Canton Network: CIPs and their on-chain vote outcomes, docs, forum, validator upgrade deadlines. This page covers its hosted endpoint (https://ccpedia.xyz/mcp).

Is the io.github.UnityNodes/canton-ccpedia MCP server safe to use?

io.github.UnityNodes/canton-ccpedia scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.UnityNodes/canton-ccpedia MCP server expose?

io.github.UnityNodes/canton-ccpedia exposes 104 tools: search, get_cip, list_cips, get_discussion, get_whitepaper, and 99 more. Their descriptions and schemas cost roughly 15,339 tokens of context every time the server is loaded.

Does the io.github.UnityNodes/canton-ccpedia MCP server require authentication?

No. We connected to io.github.UnityNodes/canton-ccpedia without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.UnityNodes/canton-ccpedia MCP server still maintained?

io.github.UnityNodes/canton-ccpedia is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.UnityNodes/canton-ccpedia MCP server?

VerifyMCP ran 12 checks on io.github.UnityNodes/canton-ccpedia, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.UnityNodes/canton-ccpedia: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.