Ext Ops Panel
Open dashboard
Comparison

clawlock vs dev.fentz.envcp/envcp

clawlock is a plugin bundle for AI coding tools published by PalmCoast. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). dev.fentz.envcp/envcp is an MCP server published by envcp.fentz.dev. 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

Where each is published
Marketplaceclawlockdev.fentz.envcp/envcp
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.0
Downloads/month (npm): 563
Downloads/week (npm): 116
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

clawlock vs dev.fentz.envcp/envcp
Factclawlockdev.fentz.envcp/envcp
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (clawlock-mcp-server)On your machine (@fentz26/envcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)5Not a bundle
Licence (differs)BUSL-1.1Not stated
Repository (differs)github.com/palmcoast/clawlock-plugingithub.com/fentz26/envcp
Changes in the last 7 days00
First seen2026-10-112026-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

clawlock

In its own words, on Claude Code: claude-plugins-community:

Identity, credential vault, and audit security for AI agents. ClawLock gives every AI agent its own Ed25519 cryptographic identity, stores API keys in an AES-256-GCM encrypted vault, enforces least-privilege scopes, and maintains an immutable audit trail of every action. Includes 4 auto-activating skills (security scanning, agent identity management, credential vault, audit log analysis) plus 14 MCP tools via the built-in ClawLock MCP server. Works with Claude Code, Claude Cowork, OpenClaw, and any MCP studio client.

dev.fentz.envcp/envcp

In its own words, on Official MCP Registry:

Encrypted environment variable vault with AI access policies, keeping secrets safe from AI agents.

How to run each

clawlock As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install clawlock@claude-community

dev.fentz.envcp/envcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio envcp -- npx -y @fentz26/envcp

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

Neither one's marketplaces publish the settings it asks for.

What it can do: clawlock · What it can do: dev.fentz.envcp/envcp · 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.

Where the data comes from: how the catalog is built