mcpbeat Sign in

Envcp MCP Server

by fentz-envcp Your server? Claim it
local only

Envcp runs on your own machine — the client starts it, so there is no endpoint to ping.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs / week
not published
Stars
on GitHub
Last commit
from GitHub
License
language unknown

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Alternatives to Envcp

same job, measured the same way
Envcp
by fentz26

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

148 installs/wk local only
Lockbox
by sathergate

Encrypted secrets for Next.js. AES-256-GCM with no vault needed.

28 installs/wk local only
Securecode
by juanisidoro

Secrets vault for Claude Code with audit logs, access rules, and AES-256 encryption.

86 installs/wk local only
Keyblind
by aarifmms

Encrypted secrets vault for AI agents — secrets resolved at runtime, never seen by LLMs.

54 installs/wk local only
Secure Vault
by mdfifty50-boop

Encrypted secrets and credential management for agents

35 installs/wk local only
Onepassword Agent MCP
by gambadio

Local MCP access to approved 1Password fields without exposing plaintext secrets to AI agents.

112 installs/wk local only
kdbx
by yarrasys

Read-only access to secrets in a local KeePassXC vault. Runs commands with them injected.

local only
MCP Process
by digital-defiance

Process management and monitoring for AI agents with strict security boundaries

62 installs/wk local only

Envcp — questions

Answers built from our own checks of this server.

Why is there no uptime for Envcp?
Envcp runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone.
Is Envcp still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.