Should my agent depend on the MCP server io.github.UnityNodes/canton-ccpedia?

Verdict: allow — rich-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

canton ccpedia

io.github.UnityNodes/canton-ccpedia

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

— the operator's own registry description reported

Publisher io.github.UnityNodes · first seen 2026-08-12 · endpoint https://ccpedia.xyz/mcp

allow

verdict

rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

Cluster rich-solo · distinctiveness 0.378 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency168 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools88

vs populationhigh

capabilities2

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers true0/0 agree

🔏 Signed receipt rr_508590ab055400c44a074ada · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

call_canton_mcp check_deprecation community_consensus compare_governance_outcomes compare_to_evm detect_builder_overlap detect_cip_dependency_chain detect_drift diagnose_error ecosystem_dependency_graph find_apps_by_pattern find_cip_for_feature find_code_examples find_collaboration_opportunities find_expert find_known_issues find_maintainer_guidance find_security_patches find_similar_projects full_context get_api_reference get_app_metrics get_breaking_changes get_cip get_cip_attachments get_cip_citations get_cip_history get_cip_implementation_status get_cip_mentions get_cip_vote_outcome get_cip_votes get_current_versions get_discussion get_doc get_ecosystem_gaps get_faq get_foundation_info get_funding_landscape get_github_discussion get_governance_vote get_issue_status get_kb_drift get_latest_release get_mailing_thread get_network_state get_network_stats get_npm_packages get_proposal_milestones get_proposals get_radar get_recent_changes get_recent_deployments get_recurring_issue_fingerprint get_sdk_changelog get_started_guide get_sv_schedule get_token_market get_trending get_upcoming_deadlines get_upcoming_operations get_upgrade_status get_validator get_validator_fleet get_video get_whitepaper learning_path list_canton_mcps list_cips list_deprecations list_ecosystem_projects list_featured_apps list_github_discussions list_governance_votes list_mailing_threads list_repos list_videos list_votes_by_sv list_whitepapers migrate_lookup outdated_guidance_detector proposal_success_predictor search search_community search_github_issues search_mailing_list search_release_notes search_talks semantic_search

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	88/88	✓
has a description	88/88	✓
description is substantive	88/88	✓
parameters are typed	88/88	✓
parameters are described	87/88	87/88

88 of 88 tools graded · 88 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

0/0 answers agree with the published primary source · 2 unverifiable.

claim class	key	verdict	primary source
tariff-duty	6109.10.00	unverifiable	us-hts
tariff-duty	8471.30.01	unverifiable	us-hts

Protocol conformance observed

2025-06-18

protocol version

—

session model

1.0.0

server version ccpedia

Capabilities: resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:59:18Z	ok_tools	200	168	2025-06-18
2026-08-12T05:34:30Z	ok_tools	200	169	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.UnityNodes/canton-ccpedia.svg)](https://robinsaige.com/s/io.github.UnityNodes/canton-ccpedia)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview