Lighthouse Explorer

You run an MCP server that serves Lighthouse Explorer data to AI assistants, enabling you to query the Canton Network for CNS records, governance data, validators, parties, contracts, transfers, prices, and more without requiring an API key. This guide shows you how to install, configure, and use the Lighthouse Explorer MCP Server from your own environment.

How to use

You will interact with the Lighthouse Explorer MCP Server through an MCP client. The server exposes a set of tools that let you retrieve and inspect data across CNS records, governance, party balances, transactions, prices, rounds, and other Canton Network entities. Use your MCP client to call the available tools by name, supply the required identifiers or filters, and receive structured results that you can present to users or feed into your AI workflows.

How to install

Prerequisites: ensure you have Node.js installed on your system. You should also have npm available to install dependencies and build the project.

# Clone the repository
git clone https://github.com/agenticledger/ClientMCP_LIGHTHOUSE_MCPSERVER.git
cd ClientMCP_LIGHTHOUSE_MCPSERVER

# Install dependencies
npm install

# Build the server
npm run build

Configuration and startup

You configure the MCP server as a local (stdio) service that runs with Node.js and loads the built index file. The following configuration shows how to connect your MCP client to the locally hosted server.

{
  "mcpServers": {
    "lighthouse": {
      "command": "node",
      "args": ["/path/to/lighthouse-mcp-server/dist/index.js"]
    }
  }
}

Running the server locally

After building, start the server by running the command above from your terminal or integrate the start command into your development workflow. The MCP client will connect to the stdio server using the specified node process and the built index file.

Security and access

This server is described as a public API without an API key requirement. Treat it as you would any public data source: monitor usage, respect rate limits implied by the upstream Lighthouse Explorer, and ensure your client handles errors gracefully.

Additional notes

The server exposes 28 tools that cover CNS, contracts, governance, parties, prices, rounds, searches, statistics, transactions, transfers, and validators. You can consult these tools by name from your MCP client to fetch the corresponding data from the Lighthouse Explorer.

Available tools

cns_list

List CNS records with pagination

cns_get

Get a CNS record by domain name

contracts_list

List contracts with pagination

contract_get

Get contract details by contract_id (hex)

featured_apps_get

Get list of featured applications

governance_list

List all governance vote requests

governance_stats

Get governance statistics

governance_get

Get vote request details by ID

party_balance

Get CC balance for a party

party_burns

List burns for a party

party_pnl

Get profit/loss data

party_rewards

List rewards earned

party_burn_stats

Aggregated burn stats

party_reward_stats

Aggregated reward stats

party_transfers

List party transfers

party_transactions

List party transactions

preapprovals_list

List preapproval records

price_get

Get latest CC price in USD

price_history

Get 24-hour price history

rounds_list

List consensus rounds

round_get

Get round details by number

search

Universal search across entities

stats_get

Get chain statistics

transactions_list

List transactions

transaction_get

Get transaction by update ID

transfers_list

List all transfers

validators_list

Get all validators

validator_get

Get validator details by ID