Ext Ops Panel
Open dashboard
Comparison

dev.fentz.envcp/envcp vs vaultgate

dev.fentz.envcp/envcp is an MCP server published by envcp.fentz.dev. Marketplaces we read that list it: 1 (Official MCP Registry). vaultgate is an MCP server published by adamrowles1996. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
Marketplacedev.fentz.envcp/envcpvaultgate
Official MCP Registry Listed
Version: 1.1.0
Downloads/month (npm): 563
Downloads/week (npm): 116
Not marked · First seen
Listed
Version: 0.1.0-rc.10
Forks (GitHub): 0
Stars (GitHub): 3
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

dev.fentz.envcp/envcp vs vaultgate
Factdev.fentz.envcp/envcpvaultgate
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub3
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@fentz26/envcp)Not stated
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/fentz26/envcpgithub.com/adamrowles1996/vaultgate
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

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.

vaultgate

In its own words, on Official MCP Registry:

Self-hosted remote MCP server for Bitwarden and Vaultwarden with OAuth 2.1; agents hold tokens only

How to run each

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

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

vaultgate

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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: dev.fentz.envcp/envcp · What it can do: vaultgate · Compare two other plugins

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