HederaToolbox
https://api.hederatoolbox.com/mcp ↗
Description
Production MCP server giving AI agents metered access to live Hedera blockchain data. Query token prices, screen identities, monitor governance, write tamper-evident HCS compliance records, and analyze smart contracts — all paid in HBAR micropayments per call.
What our measurements say
HederaToolbox is a remote MCP server published at api.hederatoolbox.com. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 360 ms, placing it among the faster endpoints. It exposes a broad tool surface of 25 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tools are logically grouped by function (e.g., HCS, governance, identity) with clear pricing tiers.
- Free tools like 'get_terms' and 'account_info' enable onboarding and compliance checks.
- Descriptions specify use cases (e.g., 'hcs_monitor' for topic status, 'token_analyze' for risk scoring).
Weaknesses
- Some tool names (e.g., 'hcs_monitor') are ambiguous without prior knowledge of HCS.
- Descriptions occasionally omit when to use tools (e.g., 'contract_call' lacks context for optimal use).
- Parameter requirements (optional/required) are inconsistently documented (e.g., 'hcs_write_record' mentions optional signing but no schema).
hcs_write_record— Optional parameters (agent_did, agent_signature) not explicitly marked as optional.fixatum_register— Incomplete description of key generation prerequisites.token_analyze— No mention of input constraints (e.g., token ID format).
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from 'auth-gated' to 'legacy' · indicates system transition to legacy compliance framework
- 2026-09-11T03:50:39.090Z — complianceScore improved from null to 100 · shows successful compliance validation in legacy era
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 55ms → warm 52ms (penalty 3ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 3.3.0
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/mountainmystic-hederatoolbox)<a href="https://mcpmetrics.io/servers/mountainmystic-hederatoolbox"><img src="https://mcpmetrics.io/badge/mountainmystic/hederatoolbox/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see