
Envcp
io.github.fentz26Published by GitHub account fentz26v1.0.82Updated Oct 24, 2026
Encrypted environment variable vault with AI access policies, keeping secrets safe from AI agents.
Overview
A local encrypted environment variable vault with AI access policies, intended to keep secrets out of reach of AI agents.
- What you can do
- Stores environment variables in an encrypted vault on the local machine, according to the registry description. Applies access policies that govern what AI agents may reach, so secrets stay protected from them. Runs as a local stdio process started by the assistant. The manifest lists no tools, so the specific operations available are not documented in the supplied material.
- When to use it
- Consider it when you keep secrets in environment variables and want an assistant connected to your machine to work without exposing those values. It is aimed at local desktop setups rather than remote or web use.
- Requirements
- Runs as a local process on the user's machine, distributed as the npm package @fentz26/envcp over stdio, so Node.js and a desktop environment are needed. No authentication, environment variables or headers are declared in the manifest.
Installation
In SourceWeft
- Open Envcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.82LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.