Query Canton Network balances, rewards, transactions, prices, and identity from any AI agent.
Query Canton Network balances, rewards, transactions, prices, and identity from any AI agent. Exposed over MCP by the canton mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
@noves/canton-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Everything the assistant can do here goes through one of these:
resolve_party — "Who is this party?" — canonical party ID, org type, balance, ANS namessearch_directory — "Who are the super validators?" — browse/filter the network directoryget_balance — "What's this party's balance?" — current or at any point in time (date)get_balance_history — "Chart its balance over last month" — daily end-of-day snapshotsget_rewards — "What did it earn?" — summary metrics, per-day totals, or individual payoutsget_transactions — "Show its recent traffic purchases" — classified history (transfer, buyTraffic, …)get_transfer_stats — "How active is it?" — counts, volumes, unique counterpartiesget_price — "CC price trend this month?" — spot, historical spot, hourly/daily OHLCget_transaction — Full classified payload of one update by IDYou will need one environment variable: NOVES_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of file and storage access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Canton's toolset — resolve_party, search_directory, get_balance and 6 more — is a fair guide to whether it matches your workflow. It is maintained by Noves-Inc; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| resolve_party | "Who is this party?" — canonical party ID, org type, balance, ANS names |
| search_directory | "Who are the super validators?" — browse/filter the network directory |
| get_balance | "What's this party's balance?" — current **or at any point in time** (date) |
| get_balance_history | "Chart its balance over last month" — daily end-of-day snapshots |
| get_rewards | "What did it earn?" — summary metrics, per-day totals, or individual payouts |
| get_transactions | "Show its recent traffic purchases" — classified history (transfer, buyTraffic, …) |
| get_transfer_stats | "How active is it?" — counts, volumes, unique counterparties |
| get_price | "CC price trend this month?" — spot, historical spot, hourly/daily OHLC |
| get_transaction | Full classified payload of one update by ID |
{
"mcpServers": {
"canton": {
"command": "npx",
"args": ["-y", "@noves/canton-mcp"],
"env": {
"NOVES_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| NOVES_API_KEY | Credential the server authenticates with. | Yes |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.