mcpbeat Sign in

vault MCP Server

local only

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

Secret and credential management MCP — securely store, retrieve, manage API keys and tokens

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 vault

same job, measured the same way
Janee
by rsdouglas

Secure secrets proxy for AI agents — manages API keys so agents never see raw credentials.

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

Encrypted secrets and credential management for agents

47 installs/wk local only
GenPark Secure Secret Token Redactor
by alphaparkinc

High-speed regex and entropy-based scanner redacting API keys, JWT tokens, and credentials

local only
VaultGuard
by evozim

Secret scanner preventing leaks of corporate keys and credentials.

1 tools answering
API Key Case
by melavern

Local MCP tools for secret status and guarded deployment. Values never reach the agent.

58 installs/wk local only
Keyfold
by codewithkolin

Use API keys from your Keyfold vault in commands and .env files. No tool returns a secret value.

local only
MCP Request-tracker
by crunchtools

Secure MCP server for Request Tracker (RT) ticket management

513 installs/wk local only
mcp-warden
by ermoluk

Local credential broker: agents call APIs, SSH and DBs via scoped presets; secrets stay in keychain.

169 installs/wk local only

vault — questions

Answers built from our own checks of this server.

Why is there no uptime for vault?
vault runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone.
Is vault 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.