carryall-policy-enforcement vs AgentAuth
carryall-policy-enforcement is a plugin bundle for AI coding tools published by tronmongoose. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). AgentAuth is an MCP server published by raditotev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 |  carryall-policy-enforcement | |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.3.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.1 Downloads/month (PyPI): 93 Downloads/week (PyPI): 30 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 | carryall-policy-enforcement | AgentAuth |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (agentauth-mcp-server) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/tronmongoose/agent.carryall_plugin | github.com/radi-totev/agent-auth |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
carryall-policy-enforcement
Deterministic IAM control plane for AI agents. Translates natural language intent into minimal-scope Ed25519-signed envelopes. You bring your own data plane. Carryall governs access with least-privilege enforcement and a tamper-evident audit trail.
AgentAuth
Identity and auth for AI agents: credentials, tokens, delegations, and permission checks.
How to run each
carryall-policy-enforcement As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install carryall-policy-enforcement@claude-communityAgentAuth As a local MCP server: PyPI package
claude mcp add --env "AGENTAUTH_API_KEY=<YOUR_AGENTAUTH_API_KEY>" --env "AGENTAUTH_URL=<YOUR_AGENTAUTH_URL>" --transport stdio agent-auth -- uvx agentauth-mcp-serverRequires: AGENTAUTH_API_KEY (secret), AGENTAUTH_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only carryall-policy-enforcement asks for
CARRYALL_KEYS_DIR (secret)CARRYALL_SLOS_CONFIGOPENAI_API_KEY (secret)
Only AgentAuth asks for
AGENTAUTH_API_KEY (secret)AGENTAUTH_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: carryall-policy-enforcement · What it can do: AgentAuth · 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 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.