Keymaster MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 49 installs a week from npm. Last commit 14 Sep 2026.
Read-only runtime secret retrieval from HashiCorp Vault via Keymaster for autonomous AI agents.
We read the source, 6 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
{ service: "telegram", key_name: "api_key", check_method: "GET", endpoint: "https://api.telegram.org/bot{KEY}/getMe", auth_type: "url" },
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add keymaster-mcp -e 'USER_KEYMASTER_URL=<USER_KEYMASTER_URL>' -e 'USER_KEYMASTER_TOKEN=<USER_KEYMASTER_TOKEN>' -- npx -y @akari-os/keymaster-mcp
{
"mcpServers": {
"keymaster-mcp": {
"command": "npx",
"args": [
"-y",
"@akari-os/keymaster-mcp"
],
"env": {
"USER_KEYMASTER_TOKEN": "<USER_KEYMASTER_TOKEN>",
"USER_KEYMASTER_URL": "<USER_KEYMASTER_URL>"
}
}
}
}
[mcp_servers.keymaster-mcp]
command = "npx"
args = ["-y", "@akari-os/keymaster-mcp"]
env = { USER_KEYMASTER_URL = "<USER_KEYMASTER_URL>", USER_KEYMASTER_TOKEN = "<USER_KEYMASTER_TOKEN>" }
{
"mcpServers": {
"keymaster-mcp": {
"command": "npx",
"args": [
"-y",
"@akari-os/keymaster-mcp"
],
"env": {
"USER_KEYMASTER_TOKEN": "<USER_KEYMASTER_TOKEN>",
"USER_KEYMASTER_URL": "<USER_KEYMASTER_URL>"
}
}
}
}
{
"servers": {
"keymaster-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@akari-os/keymaster-mcp"
],
"env": {
"USER_KEYMASTER_TOKEN": "<USER_KEYMASTER_TOKEN>",
"USER_KEYMASTER_URL": "<USER_KEYMASTER_URL>"
}
}
}
}
Put your own values in place of
<USER_KEYMASTER_URL> (Keymaster proxy URL), <USER_KEYMASTER_TOKEN> (Bearer token for Keymaster authentication).
The author’s registry entry marks them as required.
Encrypted secrets vault for AI agents. 27 MCP tools resolve secrets at runtime, never leaking them.
Local AES-256-GCM vault for AI agents. Secrets stay local, LLMs never see real API keys.
Local-first secret scanning, rotation, vault, and audit-log tools for AI agents.
Autonomous log surgery & secret redaction MCP server for AI coding agents.
Oracle Cloud discovery + Terraform generation for AI agents — read-only, secret-safe.
Guardian layer for AI agents: identity, secrets, audit via MCP.
Intent security pre-flight checks for autonomous AI agents.
OS keychain secrets for AI coding agents, over MCP.
Answers built from our own checks of this server.