Use GOVENANT and an MCP gateway together — govern the MCP & agent protocols, not the framework. Govern the pipes once. Govern every client.
A platform team standardizes 60 internal agents across five frameworks on MCP so any agent can reach any tool.
Governance would mean 60 bespoke integrations — one per agent — and it still wouldn’t cover the next team’s agents. Tool calls flow through the protocol, but nothing ledgers them or checks ownership at the boundary.
A governing MCP gateway ledgers every tool call and enforces ownership gates for every client at once. One integration, whole ecosystem: the record shows which agents call which tools, what verifiably resulted, and where an unowned call was stopped at the gate — framework-independent.
The substrate: The protocol boundary: every tool call and task already flows through it — the natural place for an append-only ledger and an ownership gate.
The path — Protocol chokepoint: Govern the pipe once (MCP/A2A gateway) and every agent behind it inherits a ledger and ownership gates — regardless of framework.
The substrate shapes and acceptance tests are open (CC BY 4.0): developer integration · the portable schema.
A governed protocol boundary lets every system behind it claim a real, inspectable ledger — and the gateway operator can publish its own conformance record to the registry with probe logs. As always: self-assessed, open to challenge, never “certified.”
This example is a documented reference pattern; the runnable adapter/mapping is being built in the open. It will never say “supported” or “certified” before a working example lands and its record is public — progress lives in the GitHub issue. Holding our own examples to the standard’s claims discipline is the product.
All sample projects · Govern MCP & agent protocols · All integrations · Run the audit