Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Chia MCP

by Chia-Networkversion 1.0.1i★ –iRuns on your computer
Registry nameio.github.danieljperry/chia-mcp

Install

Overview

Description from the maker (original English)

MCP server for the Chia blockchain. Read-only full-node access via Coinset hosted nodes, 36 tools.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 0 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "chia": {
      "command": "npx",
      "args": [
        "-y",
        "chia-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add chia -- npx -y chia-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "chia": {
      "command": "npx",
      "args": [
        "-y",
        "chia-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "chia": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "chia-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ! Caution

    Maker matches the repo

    The publisher (danieljperry) is not the repo owner (Chia-Network); someone else may have listed it

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32684 servers in this category
  • Published to the registry more recently than 62% of the other 32684 servers in this category
  • Basic checks equal to or better than 29% of the other 32684 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Chia MCP safe?

It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 24 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Master CSS

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

Master CSS

by master-co

Inspect Master CSS classes, generated CSS, and project stylesheets from your AI client.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

chia-mcp

A Model Context Protocol (MCP) server that exposes 36 tools for querying the Chia blockchain (up to 38 with push_tx and local-node options). Uses Coinset hosted nodes — no local Chia node required.

Quick Start

Claude Desktop

Add to your config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json
{

"mcpServers": { "chia": { "command": "npx", "args": ["-y", "chia-mcp"] } } }

Claude Code
claude mcp add chia -- npx -y chia-mcp

claude mcp add chia --env CHIA_NETWORK=testnet11 -- npx -y chia-mcp

Cursor

Add to .cursor/mcp.json in your project or ~/.cursor/mcp.json globally:

{

"mcpServers": { "chia": { "command": "npx", "args": ["-y", "chia-mcp"] } } }

VS Code

Add to your User Settings (JSON) or .vscode/mcp.json:

{

"mcp": { "servers": { "chia": { "command": "npx", "args": ["-y", "chia-mcp"] } } } }

Testnet

Set CHIA_NETWORK to use testnet11:

{

"mcpServers": { "chia": { "command": "npx", "args": ["-y", "chia-mcp"], "env": { "CHIA_NETWORK": "testnet11" } } } }

Environment Variables

VariableDefaultDescription
CHIA_NETWORKmainnetNetwork to connect to: mainnet or testnet11
CHIA_FULL_NODE_URL_(auto from network)_Override the full node RPC endpoint URL (e.g., https://api.coinset.org or your own node). Local Chia nodes require mTLS client certificates; use a reverse proxy that terminates mTLS since chia-mcp does not support client certificates directly.
CHIA_MCP_ENABLE_PUSH_TX_(unset)_Set to 1 or true to enable the push_tx tool (disabled by default for safety)

Available Tools

Blockchain State
  • `get_blockchain_state` — Current chain state: peak height, sync status, difficulty, sub-slot iters, mempool size, network space estimate.
  • `get_network_info` — Network name and address prefix (xch/txch).
  • `get_routes` — List all available RPC endpoints on the node (only available on non-Coinset nodes).
Blocks
  • `get_block` — Full block by header hash (transactions, proofs, rewards).
  • `get_block_record` — Block record by header hash (lighter than full block).
  • `get_block_record_by_height` — Block record metadata at a height (lighter than full block).
  • `get_block_records` — Block records for a height range [start, end).
  • `get_blocks` — Full blocks for a height range [start, end).
  • `get_block_spends` — All coin spends in a block by header hash.
  • `get_block_spends_with_conditions` — Coin spends with parsed CLVM conditions by header hash.
  • `get_additions_and_removals` — All coins created/spent in a block.
  • `get_unfinished_block_headers` — Unfinished block headers (blocks in progress).
  • `get_block_count_metrics` — Block count metrics (compact/uncompact counts).
Coins
  • `get_coin_record_by_name` — Single coin by its ID (sha256 of parent+puzzle_hash+amount).
  • `get_coin_records_by_names` — Multiple coins by IDs (batch lookup).
  • `get_coin_records_by_puzzle_hash` — Coins locked to a puzzle hash, with optional spent/height filters.
  • `get_coin_records_by_puzzle_hashes` — Coins locked to multiple puzzle hashes (batch lookup).
  • `get_coin_records_by_hint` — Coins tagged with a hint (common in CAT/NFT transactions).
  • `get_coin_records_by_hints` — Coins tagged with multiple hints (batch lookup).
  • `get_coin_records_by_parent_ids` — Coins created by specific parent coins (trace lineage).
  • `get_puzzle_and_solution` — CLVM puzzle and solution for a spent coin at a given height.
  • `get_puzzle_and_solution_with_conditions` — Puzzle, solution, AND parsed CLVM conditions for a spent coin.
  • `get_memos_by_coin_name` — Memos/messages associated with a coin.
Mempool
  • `get_all_mempool_tx_ids` — List all pending transaction IDs.
  • `get_all_mempool_items` — All mempool items with full details (can be large).
  • `get_mempool_item_by_tx_id` — Single mempool item by transaction ID.
  • `get_mempool_items_by_coin_name` — Mempool items referencing a specific coin.
  • `get_fee_estimate` — Fee estimates for target inclusion times.
Transactions
  • `push_tx` — Submit a signed spend bundle to the mempool.
  • `get_aggsig_additional_data` — AGG_SIG additional data for signature verification.
Network
  • `get_network_space` — Estimate total network space between two blocks.
Composite (higher-level queries, multiple RPCs)
  • `get_address_summary` — Complete balance summary for an address or puzzle hash. Pages through ALL unspent coins to produce an accurate total with a complete flag. This is the correct way to check a balance.
  • `decode_offer` — Decode a Chia offer string (offer1...) into a structured summary: coin spends, amounts, coin IDs, puzzle sizes, signature status. Uses the official chia-wallet-sdk for correct parsing.
  • `trace_coin_lineage` — Trace a coin's ancestry back to its origin (coinbase). Follows parent links up to max_depth hops.
  • `summarize_block` — Compact summary of all coin movements in a block: counts, totals, largest movements, net flow by puzzle hash. Much more useful than raw get_additions_and_removals (which can be 1+ MB).
Utilities (local computation, no RPC)
  • `address_encode` — Convert a puzzle hash to a bech32m Chia address (xch1.../txch1...).
  • `address_decode` — Decode a bech32m Chia address back to its puzzle hash.
  • `coin_id` — Compute a coin ID from parent_coin_id + puzzle_hash + amount.

Tool Examples

Quick reference showing input → output shape for the most commonly used tools.

get_blockchain_state
Input:  {} (no parameters)

Output: { peak_height: 9470000, sync: { synced: true }, difficulty: 2528, space: "33501849665552384", mempool_size: 3, ... }

get_coin_record_by_name
Input:  { name: "0xabc123..." }

Output: { coin: { parent_coin_info: "0x...", puzzle_hash: "0x...", amount: 1750000000000 }, confirmed_block_index: 5000000, spent_block_index: 5000042, coinbase: false, timestamp: 1700000000 }

get_coin_records_by_puzzle_hash
Input:  { puzzle_hash: "0xabc123...", include_spent_coins: false }

Output: [ { coin: { ... }, confirmed_block_index: ..., spent_block_index: 0 }, ... ] Note: Response truncated at 50KB. For complete balance, use get_address_summary instead.

get_address_summary
Input:  { address: "xch1abc123..." }

Output: { total_balance_mojos: "1750000000000", total_balance_xch: "1.75", coin_count: 3, complete: true, oldest_coin_height: 4500000, newest_coin_height: 9400000 } Note: Pages through ALL unspent coins. The complete flag indicates whether the full balance was reached.

trace_coin_lineage
Input:  { coin_id: "0xabc123...", max_depth: 10 }

Output: { lineage: [ { coin_id: "0x...", parent: "0x...", amount: 1750000000000, height: 5000042 }, ... ], depth_reached: 5, reached_coinbase: true }

summarize_block
Input:  { header_hash: "0xabc123..." }

Output: { height: 5000042, is_transaction_block: true, num_additions: 12, num_removals: 6, total_amount_created: "3500000000000", total_amount_spent: "3500000000000", top_movements: [ ... ] } Note: Much smaller than raw get_additions_and_removals (which can be 1+ MB).

decode_offer
Input:  { offer: "offer1..." }

Output: { valid: true, summary: { offered: { xch: "1.0" }, requested: { "asset_id_abc...": 100 } }, coin_spends: 3, has_signature: true }

address_encode
Input:  { puzzle_hash: "0xabc123...", prefix: "xch" }

Output: { address: "xch1abc123..." } Note: Local computation — no RPC call.

address_decode
Input:  { address: "xch1abc123..." }

Output: { puzzle_hash: "0xabc123..." } Note: Local computation — no RPC call.

coin_id
Input:  { parent_coin_info: "0x...", puzzle_hash: "0x...", amount: 1750000000000 }

Output: { coin_id: "0xabc123..." } Note: SHA256(parent + puzzle_hash + amount). Accepts string amounts for values > Number.MAX_SAFE_INTEGER.

Resources

Network State (live)
  • `chia://network/mainnet` — Mainnet connection info and live blockchain state.
  • `chia://network/testnet11` — Testnet11 connection info and live blockchain state.
Guides (embedded documentation)
  • `chia://guide/coin-model` — Chia's coin/UTXO model, spend bundles, token standards, and common LLM mistakes.
  • `chia://guide/rpc-quickstart` — Common RPC calls with curl examples and Coinset endpoints.
  • `chia://guide/recipes` — Step-by-step recipes for balance checks, transaction tracing, CAT detection — with failure modes.

How It Works

This server wraps the Chia full node RPC API using Coinset's hosted endpoints:

  • Mainnet: https://api.coinset.org/
  • Testnet11: https://testnet11.api.coinset.org/

All RPC calls are simple HTTP POST requests with JSON bodies. No authentication required.

Coinset Hosted Node vs Local Node

Most tools work against any Chia full node (Coinset-hosted or your own). Three tools are Coinset extensions — they do not exist in chia-blockchain's full node RPC API and will return HTTP 404 against a local node or the simulator:

ToolCoinsetLocal node / Simulator
get_puzzle_and_solution_with_conditions✅❌ — use get_puzzle_and_solution + local CLVM eval
get_memos_by_coin_name✅❌
get_coin_records_by_hints✅❌ — only singular get_coin_records_by_hint exists

Simulator portability: Code written against Coinset's extended endpoints will not work against the simulator or a local node. The simulator (chia dev sim) and standard chia-blockchain nodes support the same standard RPC surface. Develop against the simulator using standard RPCs for maximum portability; use Coinset extensions for production querying convenience.

Shared RPCs: get_network_info and get_aggsig_additional_data are shared RPC endpoints available on all Chia services (not full-node-specific). They work on both Coinset and local nodes.

Deliberately omitted RPCs: Three upstream full node RPCs are not exposed as tools: get_constants (static data better served by constants.json), get_recent_signage_point_or_eos (internal consensus detail not useful for agents), and create_block_generator (timelord/farmer internal). All other full node RPCs are exposed.

Prompts

The server provides 9 prompts that encode tool sequencing and failure modes for common Chia tasks:

PromptDescription
network_statusCheck the current state of a Chia network: peak height, sync status, difficulty, mempool.
address_balanceCheck the XCH balance of a Chia address using get_address_summary for accuracy.
coin_lookupLook up a specific coin by its coin ID and inspect its details.
trace_lineageTrace a coin's parent chain to understand where funds came from.
block_summarySummarize a block's contents: transaction count, value moved, top addresses.
transaction_statusCheck whether a transaction is confirmed, in mempool, or dropped.
offer_safetyEvaluate whether a Chia offer is safe to accept (hidden spends, asset verification, expiry).
token_verificationVerify whether tokens (CATs) are legitimate by checking the asset ID against trusted registries.
fee_selectionDetermine the appropriate fee for a Chia transaction based on current network conditions.

Known Limitations

  • `get_routes` unavailable on Coinset hosted nodes — Returns HTTP 404. This i

Only the beginning is shown; read the rest in the repo

Ask PopNx