CC Explorer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CCEXPLORER_API_KEY | Yes | API key for the CC Explorer Pro API (Canton Network Explorer). Contact NodeFortress / CC Explorer Pro for API access. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| consensus_getB | Get the latest consensus block and validator set from the Canton Network |
| contract_getB | Get details of a specific contract by ID |
| contract_updates_listC | List updates involving a specific contract |
| party_updates_listC | List updates involving a specific party |
| update_getC | Get a specific ledger update by ID |
| updates_listC | List ledger updates |
| round_currentB | Get the current round number |
| governance_getC | Get a governance vote by tracking CID |
| governance_listB | List all governance votes (in progress and closed) |
| overview_getB | Get network overview including active validators, super validators, supply, consensus height, and open votes |
| party_getC | Get details of a specific party (wallet) by ID |
| searchC | Search for parties, updates, or other entities |
| super_validators_listB | List super validators and their reward weights |
| validators_listB | List all active validator licenses |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| CC Explorer API Information | Overview of available endpoints and their status |
TDQS
Scored across 14 tools
Every tool has a clearly distinct purpose targeting specific resources and actions in the Canton Network domain. Tools like contract_get vs. contract_updates_list or party_get vs. party_updates_list show clear separation, with no overlapping functionality that would cause agent misselection.
Most tools follow a consistent verb_noun pattern (e.g., consensus_get, contract_get, governance_list), but there are minor deviations like search (noun only) and round_current (adjective_noun). The naming is still highly readable and predictable overall.
With 14 tools, this server is well-scoped for exploring the Canton Network, covering consensus, contracts, governance, parties, updates, and validators. Each tool earns its place by addressing a specific aspect of the domain without being overwhelming.
The tool surface provides complete coverage for the domain of network exploration, including CRUD-like operations (get, list), search functionality, and overview data. There are no obvious gaps that would cause agent failures, as all core entities and actions are addressed.