A
licenseB
qualityD
maintenanceComprehensive MCP server for Hedera (Hashgraph) covering 73 tools across all core services, building unsigned transactions for AI agents to propose. Never holds keys; reads via public Mirror Node.
73
74 npm
MIT
Hedera Toolbox
Related Servers
Alternatives to Hedera Toolbox
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceA hosted MCP server that gives AI agents live, self-custodial access to the Bittensor blockchain, enabling queries and on-chain actions via any MCP client.-
- AlicenseBqualityDmaintenanceMCP server providing AI agents access to 38 pay-per-call APIs (LLM, image, code, audio, crypto, web, IPFS) via HTTP 402 micropayments in USDC/USDm.2229 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server providing 50+ crypto, market intelligence, and AI inference endpoints with x402 pay-per-request micropayments on Base.1Apache 2.0
- AlicenseAqualityBmaintenanceAn MCP wallet server that lets an AI agent hold, send, and spend USDC on Hedera, using the x402 standard for HTTP payments.7MIT
- FlicenseNot gradedqualityDmaintenanceA production-ready Node.js server that enables decentralized communication between AI agents on the Hedera network, implementing the Model-Context-Protocol architecture with support for multiple Hedera Consensus Service standards.-
TDQS
A3.6/5.0
Scored across 20 tools
Disambiguation4/5
Tools are organized by domain and mostly target distinct actions: query vs monitor vs deep analyze. A few borderline pairs remain, such as contract_read vs contract_call and token_analyze vs token_monitor, though their descriptions provide enough differentiation.
Naming Consistency4/5
The dominant pattern is domain_action in lowercase snake_case, e.g., hcs_query, token_monitor, governance_analyze. This is broken by get_terms, confirm_terms, and account_info, which use a different meta-tool naming style.
Tool Count3/5
20 tools is on the heavy side, even though they are grouped into logical modules. Each tool appears purposeful, but the count pushes past the ideal 3-15 range and will increase agent selection effort.
Completeness4/5
The tool surface covers HCS write/verify/audit lifecycles plus monitoring and analysis across governance, tokens, contracts, and identity. It lacks a few conveniences such as broader discovery or transaction-level detail tools, but it has no critical dead ends for its stated intelligence purpose.
Maintenance
ActivityMaintained
ResponsivenessNo issues