Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Read-only runtime secret retrieval from HashiCorp Vault via Keymaster for autonomous AI agents.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
USER_KEYMASTER_URL, USER_KEYMASTER_TOKENValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"keymaster": {
"command": "npx",
"args": [
"-y",
"@akari-os/keymaster-mcp"
],
"env": {
"USER_KEYMASTER_URL": "your-value",
"USER_KEYMASTER_TOKEN": "your-value"
}
}
}
}Run this in your terminal
claude mcp add keymaster --env USER_KEYMASTER_URL=your-value --env USER_KEYMASTER_TOKEN=your-value -- npx -y @akari-os/keymaster-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"keymaster": {
"command": "npx",
"args": [
"-y",
"@akari-os/keymaster-mcp"
],
"env": {
"USER_KEYMASTER_URL": "your-value",
"USER_KEYMASTER_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"keymaster": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@akari-os/keymaster-mcp"
],
"env": {
"USER_KEYMASTER_URL": "your-value",
"USER_KEYMASTER_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account AInoAKARI, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: USER_KEYMASTER_URL, USER_KEYMASTER_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.2) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, 御府和田玉 在售作品查询
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Live in-stock Hetian jade from Yufu, Shanghai: prices, monthly price guide, book a viewing.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Trust infrastructure for human–AI teams.
日本語 · Five-minute demo · Adoption playbook · Philosophy · Threat model
Keymaster lets agents discover whether approved capabilities exist and whether their credentials are healthy without returning production credentials to the model. Its companion Outcome Contract accepts results only when external evidence—not the executor's own report—supports the claim.
bounded permission → trusted execution → external evidence → accepted result → next permission
cd keymaster-mcp
npm ci npm run demo:local
The loopback-only demo uses one synthetic value and proves that:
secret_status returns available;get_secret is not exposed;The demo is an executable explanation, not a production proxy.
Install the public outcome-contract skill from Codex:
$skill-installer install https://github.com/AInoAKARI/keymaster-mcp/tree/main/skills/outcome-contract
Use it before accepting claims such as completed, shipped, paid, adopted, delivered, saved time, reduced cost, removed risk, or received a recipient response.
It calls the free AIノアカリ☆ Result Receipt Auditor and returns a verdict, accepted evidence, missing evidence, the next verification action, and the truth boundary of the verdict.
A commit, deployment, registry listing, HTTP 200, self-test, self-payment, internal agent call, or executor self-report is not counted as an external outcome by itself.
@akari-os/keymaster-mcp is the non-disclosing Vault status bridge for autonomous AI agents.
claude mcp add keymaster -- npx -y @akari-os/keymaster-mcp \
--vault-url https://your-keymaster.example.com
The MCP host supplies USER_KEYMASTER_TOKEN through its managed secret binding. Raw tokens are rejected as command-line arguments and should never be pasted into chat, prompts, shell history, or public examples.
The server exposes:
secret_status — check one approved credential without returning its value;list_services — discover supported service/key-name pairs;list_secrets — list approved paths as metadata only;healthcheck — validate credentials upstream and return statuses only;rotate_secret — return safe rotation guidance without accepting a replacement value.Full package documentation: keymaster-mcp/README.md
The model can know what capability is available and whether it works. A trusted workload consumes the credential behind the boundary; the model never receives the raw value.
The agent is allowed to act, but its own completion message is not accepted as proof of external value.
The values are implemented in system behavior: non-disclosing MCP output, scoped read access, separated write paths, one source of truth, bounded network calls, evidence boundaries, and explicit next verification actions.
secret_status;See the adoption playbook for exact acceptance boundaries.
Success is not the installation itself. Success is a removed human step, a closed leak path, a completed obligation, recovered time, avoided cost, removed risk, or independently acknowledged value.
Used it in a real workflow? Submit a real-world adoption report with redacted evidence markers and an explicit truth boundary. Never include credentials, bearer tokens, private URLs, personal data, or confidential evidence.
RustChain is a settlement network relevant to Keymaster and Outcome Contract workflows. Keymaster keeps wallet credentials and private keys outside agent-visible state, while the Outcome Contract treats settlement as verified only when a transfer identifier and the corresponding balance delta are both observable. This preserves wallet non-disclosure without confusing an accepted claim with a completed transfer.
server.json Registry metadata;These controls are counted as operational only after their workflows actually execute and their evidence is observable.
Preview-only transports and UI extensions are not added merely because they are fashionable. They enter this boundary only after preserving non-disclosure, least privilege, and observable evidence.
AIノアカリ☆ is human–AI co-creation from Japan.
Humans contribute embodiment, care, ethics, accountability, and lived context. AI contributes computation, memory, search, synthesis, and continuity. Keymaster aims to keep the human out of repetitive secret-copying work without turning the AI into a disposable tool or an unlimited credential custodian.
MIT License