← Registry

Data Collection

ccledger.xyz

Provides tools to interact with the CC Ledger network, including registering an API key, viewing network statistics, and submitting attestations and mint records on Canton MainNet.

1 endpoint22 known toolsFirst detected August 18, 2026Last detected August 18, 2026

ENDPOINT 1

https://ccledger.xyz/mcp

No auth detected

MCP server metadata

Name
CC Ledger
Version
1.0.0
Capabilities
tools.listChanged

Known tools 22

register_api_key

Register for a CC Ledger API key.

Inferred read-only
get_stats

Get public CC Ledger network statistics: total actions, active apps, actions by type.

Inferred read-only
submit_attest

Record a data attestation on Canton MainNet.

Inferred read-only
submit_mint

Write a NON-ISSUER mint record on Canton MainNet — a verifiable on-chain attestation of a mint event.

Potential side effects
submit_attest_mutual

Create a mutual (two-party co-signed) attestation proposal.

Potential side effects
get_balance

Check your full account status: fee-credit balance (non-refundable prepaid credits that pay per-action fees only — ccledger is non-custodial and holds no spendable value balance), CCL discount balance, tier, rate limit, trial credits, CCL Builder Rewards progress, and discounted action rates.

Potential side effects
quote

Preview the exact CC cost of an action BEFORE spending: the (CCL-discounted) fee, the base fee, your discount percent, your balance, and whether you can afford it.

Inferred read-only
deposit_cc

Top up FEE CREDITS (manual fallback).

Inferred read-only
list_actions

List your past actions on CC Ledger.

Inferred read-only
get_action_by_id

Get a single action by its UUID.

Inferred read-only
get_action

Alias for get_action_by_id.

Inferred read-only
create_agent_key

Mint a scoped AGENT KEY — a non-custodial SPEND HANDLE on THIS (top-level) key's prepaid fee credits.

Inferred read-only
list_agent_keys

List the AGENT KEYS owned by this top-level key.

Inferred read-only
revoke_agent_key

Revoke (deactivate) an AGENT KEY you own by its id.

Inferred read-only
list_receipts

List signed FEE RECEIPTS.

Inferred read-only
get_receipt

Get one signed FEE RECEIPT by id.

Inferred read-only
create_sandbox_key

Issue a PUBLIC sandbox TEST key (prefix cbt_) — no authentication required.

Inferred read-only
create_webhook

Register a signed webhook so ccledger POSTs your endpoint when an event fires on your account.

Inferred read-only
list_webhooks

List the webhooks registered by your key.

Inferred read-only
delete_webhook

Delete (deregister) a webhook you own by its id.

Potential side effects
list_webhook_deliveries

Inspect the delivery log for one of your webhooks — the audit trail for debugging.

Inferred read-only
test_webhook

Send a webhook.ping test delivery to one of your webhooks right now — confirm your endpoint receives the POST and that your HMAC-SHA256 signature check passes, without waiting for a real event.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.cc-ledger]
url = "https://ccledger.xyz/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "cc-ledger": {
      "type": "http",
      "url": "https://ccledger.xyz/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: cc-ledger
Remote MCP URL: https://ccledger.xyz/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "cc-ledger": {
      "url": "https://ccledger.xyz/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "cc-ledger": {
      "type": "http",
      "url": "https://ccledger.xyz/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "cc-ledger",
  "transport": "streamable-http",
  "url": "https://ccledger.xyz/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.