Ext Ops Panel
Open dashboard
Comparison

Env-Var-Locker vs io.github.chirag127/secenv-mcp

Env-Var-Locker is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.chirag127/secenv-mcp is an MCP server published by chirag127. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
MarketplaceEnv-Var-Lockerio.github.chirag127/secenv-mcp
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 1.1.4
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

Env-Var-Locker vs io.github.chirag127/secenv-mcp
FactEnv-Var-Lockerio.github.chirag127/secenv-mcp
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (env-locker-mcp.vercel.app/api/mcp)On your machine (https://github.com/chirag127/secenv-mcp/releases/download/v1.1.0/secenv-mcp.mcpb)
Transport (differs)SSEstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/chirag127/secenv-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 402 (3 days ago)no remote endpoint we check

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

Env-Var-Locker

In its own words, on Official MCP Registry:

Encrypted env variables manager with zero-leak capabilities.

io.github.chirag127/secenv-mcp

In its own words, on Official MCP Registry:

Centralized secrets manager MCP server. Generate .env files, rotate keys, sync to GitHub Actions.

How to run each

Env-Var-Locker As a remote MCP server

Claude Code
claude mcp add --transport sse env-locker https://env-locker-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"

Requires: payment-signature header

io.github.chirag127/secenv-mcp

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

Requires: SECENV_REPO_URL (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Env-Var-Locker 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

The marketplaces of Env-Var-Locker publish no settings it asks for, so we do not compare settings.

What it can do: Env-Var-Locker · What it can do: io.github.chirag127/secenv-mcp · 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