Library
85,340 resources from 11 public sources. 54 checked by hand; the rest are unreviewed.
Results
Looks like a goal we have a starting path for: I want to connect AI to my tools
-
env
MCP serversMCP server for .env file validation, parsing, and comparison.
env-forge-mcp@1.0.3 -
envibe
MCP serversSecure permission layer between AI agents and your .env files
envibe-mcp@0.2.7 -
envdoctor
MCP serversLocal environment doctor: runtime, tools, env files, and services, pass or fail.
@reneturcios/envdoctor@0.1.0 -
phantom-secrets
MCP serversStop AI coding agents from leaking your API keys. Local proxy + MCP that swaps real secrets for phm_ tokens — works with Claude Code, Cursor, Windsurf, and Codex.
git clone https://github.com/ashlrai/phantom-secrets.git -
secenv-mcp
MCP serversCentralized secrets manager MCP server. Generate .env files, rotate keys, sync to GitHub Actions.
https://github.com/chirag127/secenv-mcp/releases/download/v1.1.0/secenv-mcp.mcpb@1.1.0 -
ghosthunt
MCP serversFind every leaked secret on your machine — API keys in .env files, shell history, and configs.
ghosthunt@1.0.0 -
Secret Store
MCP serversVault for .env files and credentials with scoped, audited MCP access for coding agents.
-
ShipLatch
MCP serversFree passive security scan for AI-built apps: leaked API keys, public .env files, security headers
-
Keyfold
MCP serversUse API keys from your Keyfold vault in commands and .env files. No tool returns a secret value.
https://github.com/codewithkolin/keyfold/releases/download/v1.0.1/keyfold-1.0.1.mcpb -
env-secret-exposure-analyzer-mcp
MCP serversScans projects for secret exposure: leaked API keys, unprotected .env files, and secrets in logs.
env-secret-exposure-analyzer-mcp@0.2.0
Indexed entries aren't reviewed or tested by InnerVault. Details come straight from each source. Anything that can reach your accounts, files or browser can do damage, so read the source before you install it.