原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Chia MCP

作者:Chia-Network版本 1.0.1i★ –i在你的电脑上运行
注册名称io.github.danieljperry/chia-mcp

安装

概览

作者提供的说明(英文原文)

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 0 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ! 注意

    作者与仓库一致

    发布者(danieljperry)不是仓库所有者(Chia-Network);可能是其他人代为上架的

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 32686 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 32686 个服务器的 62% 更新
  • 基础检查结果等于或优于此分类中其他 32686 个服务器的 29%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Chia MCP 安全吗?

它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.0.1)于24天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, Microsoft Exchange Online MCP

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

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

在云端运行★ 211前天更新
安装

Exchange Online admin for MSPs: forwarding audits, EWS posture and offboarding, no PowerShell

在你的电脑上运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx