Trellis MCP gives AI agents structured access to Hiero's distributed ledger and Guardian governance — through five auditable layers, each independently attestable. No trust-me APIs. Every action traces to the ledger. Every layer can be verified in isolation.
git clone https://github.com/trellis-mcp/trellis-mcp.git
click to copy
Infrastructure separated from domain logic. Open-source core that anyone can build on. Domain layers where your application plugs in. Developers work in their domain language — certificates, milestones, provenance — not Hedera's infrastructure language. The ledger is the trust layer, not the interface layer.
Each primitive maps a real-world business concept directly to ledger mechanics. No custom integration. No bespoke schema design.
Every other MCP server is a trust-me API. An agent calls a tool, gets a result, and has no way to verify the response wasn't spoofed, manipulated, or fabricated. That's fine for weather data. It's unacceptable for finance, procurement, or carbon verification.
Every Trellis MCP response traces to a Hiero transaction with a consensus timestamp and cryptographic proof. The trust is mathematical, not reputational.
A monolithic AI system is a black box. Five independent layers with bounded scope and deterministic behavior can be attested in isolation — by auditors, by regulators, by anyone.
An auditor attests procurement governance on Layer 1–5. The same methodology transfers to carbon verification, supply chain, healthcare — at decreasing cost and increasing confidence. Trust compounds with adoption.
The LLM's internal reasoning will always be opaque — and that's irrelevant. The model has no unmediated authority. It can only call tools with defined parameters, and every action is validated by deterministic layers below. The LLM proposes. The ledger disposes.
Not loose prompt-based tool calling. Every agent–tool interaction uses explicit JSON-RPC schemas with defined parameters, constraints, and predictable responses. Developers and auditors inspect exact interfaces without touching model weights.
Every MCP interaction is inherently loggable: tool discovery, calls, parameters, results, errors. A machine-readable chain of actions far easier to audit than opaque neural activations or scattered custom integrations.
Other frameworks let agents blindly trust tool responses. Trellis grounds every high-stakes action in on-ledger proofs — consensus timestamps and cryptographic signatures. Even if the AI hallucinates, the outcome is verifiable against the immutable ledger.
Over autonomous iterations, AI agents gradually diverge from intended parameters — individually small deviations that become collectively significant. Fixed-contract interfaces and per-action ledger attestation make drift detectable by design, not in retrospect.
Each demonstrates the full Layer 4 + Layer 5 pattern. Define your domain, spin up the server, and you have an enterprise-grade AI-native application on Hiero.
Independent commercial entities proving the enterprise-readiness of the architecture. Each vertical is a complete network application executing on Hiero.
Production deployments requiring advanced resilience and physics-bounded intelligence.
Clone, build, connect your MCP client. The agent discovers tools automatically.