Hedera Mcp

io.github.ExpertVagabond由 GitHub 帳號 ExpertVagabond 發布v0.5.0更新於 Oct 24, 2026

Build-only Hedera (Hashgraph) MCP — 73 tools across all core services plus analytics reads.

概覽

AI 產生的概覽

一個僅建構交易的 Hedera(Hashgraph)MCP 伺服器,讓助理建構並檢查 Hedera 交易、讀取網路資料,本身從不持有金鑰。

可以做什麼
為帳戶、代幣、共識主題、智慧合約、檔案與排程交易建構未簽章、已凍結的交易,以 base64 回傳供你在別處簽章。解碼並檢查已建構的交易後再簽章。從公開 Mirror Node 讀取網路與分析資料:區塊、交易、餘額、代幣與 NFT 持有、授權額度、合約狀態與結果、質押、供給量、費用和匯率。依公鑰或 EVM 位址查找帳戶,並讀取匯率、供給量、帳戶和代幣等免金鑰資源。
適用情境
適合讓 AI 助理協助草擬 Hedera 操作(例如建立代幣、主題、合約或排程交易),而由你自己簽章並提交。也適合透過 Mirror Node 讀取來查詢 Hedera 網路與帳戶資料。
執行需求
透過 npx 從 npm 套件啟動的本機程序,需要 Node.js。選用環境變數:HEDERA_NETWORK(mainnet、testnet 或 previewnet,預設 testnet)、HEDERA_OPERATOR_ID(作為預設付款方的帳戶 ID,不是金鑰)以及用來覆寫 Mirror Node REST 位址的 HEDERA_MIRROR_URL。讀取需要連線至 Mirror Node 的網路存取。
安裝前請注意
寫入不會被執行:伺服器回傳未簽章交易,需你用自有錢包或 SDK 簽章並提交,提交前請先檢視,例如使用解碼工具。它從不索取私鑰;operator id 只是帳戶 ID。README 中的實盤測試腳本使用本機環境檔裡的臨時 testnet 金鑰,這屬於伺服器之外的部分。讀取會送往公開 Mirror Node,或 HEDERA_MIRROR_URL 所指的端點。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Hedera Mcp,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

hedera-mcp

[hedera-mcp]

[MCP Registry] [npm] [license]

Comprehensive Model Context Protocol server for Hedera (Hashgraph). Full coverage of every core Hedera service — Account, Token (HTS), Consensus (HCS), Smart Contract (EVM), File, Schedule, and Network — exposed as 79 MCP tools any AI agent (Claude, Cursor, etc.) can call.

Build-only. Never holds keys. Reads hit the public Mirror Node REST API (no auth). Writes return an unsigned, frozen transaction (base64) for you to sign and submit with your own wallet/SDK/CLI. This server never sees a private key and never executes anything.


Why this exists

The official Hedera Agent Kit ships a preconfigured MCP server, but its tool surface is intentionally small (balance, transfer, deploy). This server fills the gap with end-to-end coverage of the Hedera API, organized for developer education and agent-driven onboarding — so a developer can go from "certified" to "shipping their first HTS token / HCS topic / contract" inside a single AI session.

ServiceOfficial starter MCPhedera-mcp
Accountbalancecreate, transfer, update, delete, allowances, info, balances, NFTs
Token (HTS)transfer, deploycreate FT/NFT, mint, burn, transfer, associate, freeze, KYC, pause, wipe, delete, info
Consensus (HCS)—create/update/delete topic, submit + read messages
Smart contract—deploy, execute, eth_call read, info
File—create, append, delete, info
Schedule—create, sign, delete, info
Network—tx lookup, nodes, fees, supply, exchange rate, decode

Security model

  • Reads → public Mirror Node REST. No keys, no account required.
  • Writes → the tool constructs the transaction, freezes it for offline signing, and returns base64 bytes plus a human summary. You inspect it (hedera_decode_transaction), then sign and submit yourself.
  • The only optional environment input is HEDERA_OPERATOR_ID — an account id, used as the default payer/treasury when building. Never a key.

This mirrors the posture of goat-network-mcp: safe to run anywhere, safe to give to an autonomous agent.

Published on npm and the MCP Registry as io.github.ExpertVagabond/hedera-mcp.

Install

Run directly with npx (no clone needed):

bash
npx @purplesquirrel/hedera-mcp

Or from source:

bash
npm installnpm run build

Configure (Claude Desktop / Claude Code)

json
{  "mcpServers": {    "hedera": {      "command": "npx",      "args": ["-y", "@purplesquirrel/hedera-mcp"],      "env": {        "HEDERA_NETWORK": "testnet",        "HEDERA_OPERATOR_ID": "0.0.1234"      }    }  }}
Env varDefaultNotes
HEDERA_NETWORKtestnetmainnet | testnet | previewnet
HEDERA_OPERATOR_ID(unset)Optional default payer/treasury account id (not a key)
HEDERA_MIRROR_URLper-networkOverride Mirror Node REST base (e.g. a private/HGraph node)

Build-only workflow

agent calls hedera_create_fungible_token        │        ▼hedera-mcp builds + freezes the TokenCreateTransaction        │        ▼returns base64 (unsigned)  ──►  you sign in HashPack / SDK / CLI  ──►  submit to Hedera

Inspect anything before signing:

hedera_decode_transaction { transactionBase64: "<bytes>" }→ { type: "TokenCreateTransaction", transactionId, nodeAccountIds, maxTransactionFee, ... }

Tool catalog (79)

Account (8): create_account · transfer_hbar · update_account · delete_account · approve_hbar_allowance · get_account_info · get_account_balance · get_account_nfts

Token / HTS (23): create_fungible_token · create_nft_collection · mint_fungible · mint_nft · burn_token · transfer_token · transfer_nft · associate_token · dissociate_token · freeze_token_account · unfreeze_token_account · grant_kyc · revoke_kyc · pause_token · unpause_token · wipe_token · delete_token · update_token · token_airdrop · reject_token · approve_token_allowance · approve_nft_allowance · get_token_info · get_nft_info

Consensus / HCS (6): create_topic · submit_message · update_topic · delete_topic · get_topic_info · get_topic_messages

Smart contract / EVM (6): deploy_contract · execute_contract · update_contract · delete_contract · query_contract · get_contract_info — execute_contract & query_contract are ABI-aware (pass { abi, functionName, args }; calldata encoded + results decoded automatically)

File (4): create_file · append_file · update_file · delete_file

Schedule (4): create_schedule · sign_schedule · delete_schedule · get_schedule_info

Network / utility (7): prng · get_transaction · get_network_nodes · get_exchange_rate · get_network_supply · get_network_fees · decode_transaction

Analytics (Mirror Node reads, 14): get_block · get_blocks · get_account_transactions · get_token_balances · get_token_nfts · get_nft_history · get_account_allowances · get_account_token_allowances · get_account_nft_allowances · get_contract_results · get_contract_state · get_network_stake · search_accounts_by_pubkey · get_account_by_evm

Resources (4)

Besides tools, the server exposes addressable, keyless MCP resources agents can read by URI:

hedera://network/exchange-rate · hedera://network/supply · hedera://account/{accountId} · hedera://token/{tokenId}

Examples & learning

  • examples/TUTORIAL.md — Build on Hedera in 5 prompts (the certified→shipping learning path)
  • examples/agent-demo.md — wire into Claude Desktop and build by asking; node examples/agent-sim.mjs prints a reproducible agent transcript
  • examples/scenarios/ — unique use cases, each runnable + Mirror Node-verified: HCS notary, AI agent audit trail, agent-to-agent payments, self-taxing token

Verification

  • npm run lint / npm run build — clean against @hashgraph/sdk 2.81.0
  • node test-battle.mjs — 72/73 in the auto-discovery suite (1 skip: query_contract needs a known ABI, verified separately) → all 73 tools verified (pre-MPP; 79 with the MPP charge tools)
  • node test-live.mjs — 10/10 write paths executed on testnet, Mirror Node-verified
  • node test-battle-live.mjs — battle mode: 31/31 operations on testnet across two accounts (full token lifecycle incl. freeze/KYC/pause/wipe, NFT, topic, file, scheduled transfer requiring a 2nd signer, PRNG), Mirror Node-verified. Re-run signed by an ED25519 operator: 31/31 still pass — non-EVM tools are key-type-agnostic (the server holds no keys; EVM tools inherently require ECDSA per Hedera's EVM-alias rule)
  • node test-contract.mjs — real Solidity contract compiled → deployed → executed → read end-to-end (store(42) → retrieve() = 42), confirming the full EVM path and query_contract
  • node test-contract-abi.mjs — ABI-aware query_contract: fed a raw ABI, it auto-encodes/decodes — answer() → 73 (uint), title() → "hedera-mcp" (string), ping() → 73 (pure)
  • node test-edge-cases.mjs — 12/12 edge paths on testnet the happy-path suites miss: large file via create+append (>1 tx chunk), HCS message >1024 B auto-chunked across 2 mirror entries (reassembled to 1200 B), NFT collection with a 10% royalty + 1ℏ fallback custom fee, delegated approved spend (operator approves B → B pulls 200 paying its own fee), HBAR → fresh ED25519 alias auto-account-create, and a decode_transaction round-trip

Development

bash
npm run lint       # tsc --noEmitnpm run build      # compile to dist/node test-smoke.mjs    # MCP stdio: live Mirror Node read + build-only write + decodenode demo.mjs          # narrated "developer's first session" walkthrough (build-only)node test-execute.mjs  # LIVE testnet submit (needs a throwaway key in .env — see below)

Live execution verification

test-execute.mjs proves the build-only output is real: the MCP server builds an unsigned transaction, the harness signs it with a throwaway testnet key from .env and submits it, then confirms the result independently via Mirror Node. The server stays build-only the whole time — only the test harness ever touches a key.

HEDERA_NETWORK=testnetHEDERA_OPERATOR_ID=0.0.xxxxxxHEDERA_OPERATOR_KEY=302e0201...    # rotate/discard after verifying

Get a free testnet account at portal.hedera.com.

Built on @hashgraph/sdk and @modelcontextprotocol/sdk.

Releasing

Bump the version in package.json, server.json (both top-level version and packages[0].version), and src/index.ts; update CHANGELOG.md; then publish to npm and the MCP Registry.

bash
npm run buildnpm publish --access public

Then sync the MCP Registry. Run mcp-publisher from /tmp, not from the project directory — on this setup the project lives on a volume where the publisher can't persist its OAuth token (operation not permitted), which silently fails the publish step. Copying server.json to a writable scratch dir sidesteps it:

bash
mkdir -p /tmp/hedera-publishcp server.json /tmp/hedera-publish/cd /tmp/hedera-publishmcp-publisher login github      # device-code flow, authorize as ExpertVagabondmcp-publisher publish

Verify all three surfaces are aligned:

bash
curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=ExpertVagabond/hedera-mcp&version=latest" | jq '.servers[0].server | {name, version}'npm view @purplesquirrel/hedera-mcp version

License

MIT © Matthew Karsten

來源:README.md,提交 5f9a722

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.5.0最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分