Governance code is the point of Axone's dataverse, and exposing it as a first-class lookup rather than raw chain queries is the right abstraction — an agent can ask whether it is permitted to use a resource before it uses one. The surface is small, which is honest about what the gateway currently does.
Axone's own MCP server: a lightweight gateway that lets an MCP client query the Axone chain over gRPC. Two tools cover the questions the dataverse is designed to answer — what is in this dataverse, and what rules govern this particular resource.
- `get_dataverse_info` — information about a dataverse, given the address of its contract
- `get_resource_governance_code` — the governance code attached to a resource, given the dataverse contract address and the resource's DID URI
Nothing — no account, no key; you point it at a public node. Download the release binary and put it on your `$PATH`. The documented client entry runs `axone-mcp serve stdio --node-grpc grpc.dentrite.axone.xyz:443`; SSE is available with `axone-mcp serve sse --listen-addr localhost:8080`. Building from source needs Go, and the Makefile also expects Docker.
One command — axone-mcp serve stdio --node-grpc grpc.dentrite.axone.xyz:443