Skip to main content
Glama
agenticledger

CC Explorer MCP Server

README.md
# CC Explorer MCP Server

An MCP (Model Context Protocol) server for interacting with the **Canton Network Explorer API** at [pro.ccexplorer.io](https://pro.ccexplorer.io).

## Overview

This server provides AI assistants (Claude, etc.) with tools to query the Canton Network blockchain explorer via the CC Explorer Pro API.

**API Version:** 2.9.0  
**Base URL:** https://pro.ccexplorer.io/api  
**Auth:** x-api-key header

## Installation

```bash
# Clone the repo
git clone https://github.com/agenticledger/ClientMCP_CCEXPLORER_MCPSERVER.git
cd ClientMCP_CCEXPLORER_MCPSERVER

# Install dependencies
npm install

# Build
npm run build
```

## Configuration

### Get an API Key

Contact NodeFortress / CC Explorer Pro for API access.

### Set Environment Variable

```bash
export CCEXPLORER_API_KEY=your_api_key_here
```

### Claude Desktop Configuration

Add to your `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "ccexplorer": {
      "command": "node",
      "args": ["/path/to/ccexplorer-mcp-server/dist/index.js"],
      "env": {
        "CCEXPLORER_API_KEY": "your_api_key_here"
      }
    }
  }
}
```

## Available Tools (14)

### Consensus
| Tool | Description |
|------|-------------|
| `consensus_get` | Get latest consensus block and validator set |

### Contracts
| Tool | Description |
|------|-------------|
| `contract_get` | Get details of a specific contract by ID |
| `contract_updates_list` | List updates involving a specific contract |

### Updates
| Tool | Description |
|------|-------------|
| `updates_list` | List ledger updates |
| `update_get` | Get a specific ledger update by ID |
| `party_updates_list` | List updates involving a specific party |

### Rounds
| Tool | Description |
|------|-------------|
| `round_current` | Get the current round number |

### Governance
| Tool | Description |
|------|-------------|
| `governance_list` | List all governance votes (in progress and closed) |
| `governance_get` | Get a governance vote by tracking CID |

### Overview
| Tool | Description |
|------|-------------|
| `overview_get` | Network overview: validators, supply, consensus height, open votes |

### Parties
| Tool | Description |
|------|-------------|
| `party_get` | Get details of a specific party (wallet) by ID |

### Search
| Tool | Description |
|------|-------------|
| `search` | Search for parties, updates, or other entities |

### Validators
| Tool | Description |
|------|-------------|
| `super_validators_list` | List super validators and their reward weights |
| `validators_list` | List all active validator licenses |

## Usage Examples

### Get Network Overview

```
Use the overview_get tool to see network stats including active validators, supply, and open votes
```

### Search for a Party

```
Use the search tool with query="party_id_here" to find information
```

### List Governance Votes

```
Use governance_list to see all in-progress and closed governance votes
```

### Get Current Round

```
Use round_current to get the current network round number
```

## Resources

The server also provides informational resources:

| Resource URI | Description |
|--------------|-------------|
| `ccexplorer://api-info` | Overview of available endpoints |

## License

MIT

## Author

Ore Phillips ([@oregpt](https://github.com/oregpt))

## Links

- [CC Explorer Pro](https://pro.ccexplorer.io) - Canton Network Explorer
- [Canton Network](https://canton.network) - Learn about Canton

TDQS

B3.4/5.0

Scored across 14 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness5/5

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.