Ext Ops Panel
Open dashboard
Comparison

dev.fentz.envcp/envcp vs seekrit — secrets for agents

dev.fentz.envcp/envcp is an MCP server published by envcp.fentz.dev. Marketplaces we read that list it: 1 (Official MCP Registry). seekrit — secrets for agents is an MCP server published by seekrit.dev. 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
Marketplacedev.fentz.envcp/envcpseekrit — secrets for agents
Official MCP Registry Listed
Version: 1.1.0
Downloads/month (npm): 481
Downloads/week (npm): 111
Not marked · First seen
Listed
Version: 0.1.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

dev.fentz.envcp/envcp vs seekrit — secrets for agents
Factdev.fentz.envcp/envcpseekrit — secrets for agents
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@fentz26/envcp)Remote server (mcp.seekrit.dev/mcp)
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/mileszim/seekrit
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-26

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.

seekrit — secrets for agents

In its own words, on Official MCP Registry:

Encrypted store for API keys and database URLs your code needs. Use them without reading them.

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

seekrit — secrets for agents As a remote MCP server

Claude Code
claude mcp add --transport http remote-mcp https://mcp.seekrit.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only seekrit — secrets for agents 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: dev.fentz.envcp/envcp · What it can do: seekrit — secrets for agents · 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