sanctuary-framework vs Autonomy Foundry Governance
sanctuary-framework is a plugin bundle for AI coding tools published by eriknewton. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). Autonomy Foundry Governance is an MCP server published by Diegomul. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.3.0 Forks (GitHub): 0 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | sanctuary-framework | Autonomy Foundry Governance |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 9 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@sanctuary-framework/mcp-server) | Remote server (autonomy-foundry.autonomyfoundry.workers.dev/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/eriknewton/sanctuary-framework | github.com/diegomul/autonomy-foundry |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (4 days ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
sanctuary-framework
Sovereignty infrastructure for AI agents. Gives your agent encrypted state (AES-256-GCM), self-custodied identity (Ed25519), selective disclosure (Pedersen commitments, Schnorr proofs), portable reputation, and sovereignty verification — all as MCP tools. Includes a sovereignty audit tool that detects gaps in OpenClaw and other agent harnesses.
Autonomy Foundry Governance
Governance and agentic-commerce policy tools for AI agents: spend, purchase and charter controls.
How to run each
sanctuary-framework As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install sanctuary-framework@claude-community
Autonomy Foundry Governance As a remote MCP server
claude mcp add --transport http autonomy-foundry-governance https://autonomy-foundry.autonomyfoundry.workers.dev/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Autonomy Foundry Governance has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: sanctuary-framework · What it can do: Autonomy Foundry Governance · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.