Zetrix · Blockchain & digital public infrastructure · Malaysia · Claude Code
| 91 of 91
commits in Zetrix’s two flagship MCP repositories co-authored by Claude |
55 tools
in the Zetrix MCP Server — first release shipped in a single day |
3 days
from empty repository to a 20-tool verifiable-credentials MCP server |
6 repos
of agent-facing blockchain infrastructure open-sourced in 9 months |
Most blockchains are judged by what happens on the chain. Zetrix is judged by what happens at the border.
Operated by Zetrix AI Berhad — the Malaysian company formerly known as MY E.G. Services, the country’s long-running e-government concessionaire — Zetrix is a Layer-1 public blockchain designed for governments and enterprises rather than retail crypto. It runs the Xinghuo BIF International Supernode that connects China’s national blockchain infrastructure to markets outside it. It is the protocol under Malaysia’s national blockchain infrastructure, built with the national R&D agency MIMOS. It carries certificates of origin and customs documentation between Malaysia, China and the Philippines, and it issues W3C-standard decentralised identifiers and verifiable credentials that let one country’s agency check another country’s document without either side handing over the underlying data.
That positioning creates a distinctive engineering problem, and in 2025 it got sharper. The parties that most need to touch this infrastructure are no longer only developers. They are AI agents — asked to verify a bill of lading, issue a credential, or pay for a service and prove who authorised the payment.
Making a chain agent-operable is not a thin wrapper. It is a large surface of exacting, specification-bound code: the full RPC and WebSocket surface, protobuf message handling, transaction construction with dynamic fee estimation, eight distinct cryptography operations, Ed25519 signing and BBS+ selective disclosure, HMAC-authenticated gateway clients, and — the part that has no analogue in ordinary SDK work — tool descriptions written carefully enough that an agent reaches for the right operation and never asks a human for a private key.
Zetrix needed that surface in several places at once. A general MCP server for the chain itself. A second one for the verifiable-credential service, because digital identity is the product that governments actually buy. A third for TradeTrust electronic bills of lading on Zetrix’s L2, because cross-border trade is where the chain earns its keep. And underneath all of it, SDKs for agentic payment: the x402 protocol for machine payments over HTTP, and x401, Zetrix’s own complement to it — where x402 asks “can you pay?”, x401 asks “who authorised this, and are they allowed?”
Zetrix put Claude Code at the centre of the work and adopted it across the engineering organisation on a Claude team plan. The choice is legible in the company’s own public record: rather than treating AI assistance as an invisible convenience, Zetrix’s engineers left the attribution in place. Every commit in the two flagship MCP repositories carries a Co-Authored-By trailer naming the model that helped write it — Claude Opus 4.6 running in its 1M-context configuration on the large majority, with Claude Sonnet 4.6 and Claude Sonnet 5 on later work.
The pattern that emerges from those repositories is one of compressed first releases followed by fast, surgical maintenance. The Zetrix MCP Server’s entire first release — 55 tools across seven categories, dual stdio and HTTP transports, a full README tool catalogue, developer guides and a test report — landed in seventeen commits on a single day in November 2025. The Zetrix VC MCP Server went from empty repository to twenty tools spanning DID generation and resolution, credential issuance, revocation and selective-disclosure presentations in three days the following April, with thirty-two of its thirty-seven commits on day one.
The maintenance commits are as telling as the launches. “Strengthen tool descriptions to not ask user for credentials.” “Strengthen VP tool routing so agents don’t pick vp_create for ‘create VP’.” “Fix decrypt failing when encryptedData passed as JSON string.” This is the texture of shipping agent-facing infrastructure: the hard part is not the happy path but the hundred small ways a tool surface misleads the model calling it — and it is work that goes faster when the thing helping you write it is the same kind of thing that will consume it.
The strategic point is not that Zetrix wrote software faster. It is what the software is for. Zetrix’s bet is that the next decade of cross-border trade and digital identity will be transacted by agents acting on behalf of institutions, and that those agents will need to prove authorisation before they are allowed to act — the problem x401 exists to solve, on top of an identity stack Zetrix already runs for national governments. Building that layer with Claude Code meant the company could take the bet at the speed the market is moving rather than at the speed of a hiring plan.
In April, Zetrix and CAICT’s Astron launched a blockchain trust layer for autonomous AI agents. In July, an MOU made Zetrix the protocol under the Philippines’ national public blockchain. The MCP servers are the connective tissue between all of it and the agents that will use it.
“A blockchain is only as useful as the software people can reach it with. Claude Code let a small team write the whole agent-facing surface of Zetrix — tools, SDKs, docs, tests — at a pace that used to be reserved for prototypes, and ship it as production infrastructure that governments depend on.” — Rushdan Anuar, Chief Technology Officer, Zetrix
