Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Vouch MCP
Overview
Description from the maker (original English)
Sign and verify W3C Verifiable Credentials so AI agents can cryptographically authorize actions.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
- You need to fill in: VOUCH_PRIVATE_KEY, VOUCH_DID
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
VOUCH_PRIVATE_KEY,VOUCH_DID,VOUCH_MCP_TRANSPORT,VOUCH_MCP_HOST,VOUCH_MCP_PORT
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- PyPIPython’s uv installed (for the uvx command)
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": {
"vouch": {
"command": "uvx",
"args": [
"vouch-mcp"
],
"env": {
"VOUCH_PRIVATE_KEY": "your-value",
"VOUCH_DID": "your-value",
"VOUCH_MCP_TRANSPORT": "your-value",
"VOUCH_MCP_HOST": "your-value",
"VOUCH_MCP_PORT": "your-value"
}
}
}
}Run this in your terminal
claude mcp add vouch --env VOUCH_PRIVATE_KEY=your-value --env VOUCH_DID=your-value --env VOUCH_MCP_TRANSPORT=your-value --env VOUCH_MCP_HOST=your-value --env VOUCH_MCP_PORT=your-value -- uvx vouch-mcpFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"vouch": {
"command": "uvx",
"args": [
"vouch-mcp"
],
"env": {
"VOUCH_PRIVATE_KEY": "your-value",
"VOUCH_DID": "your-value",
"VOUCH_MCP_TRANSPORT": "your-value",
"VOUCH_MCP_HOST": "your-value",
"VOUCH_MCP_PORT": "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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"vouch": {
"type": "stdio",
"command": "uvx",
"args": [
"vouch-mcp"
],
"env": {
"VOUCH_PRIVATE_KEY": "your-value",
"VOUCH_DID": "your-value",
"VOUCH_MCP_TRANSPORT": "your-value",
"VOUCH_MCP_HOST": "your-value",
"VOUCH_MCP_PORT": "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.
Values you fill in
- The agent's signing key as a JWK JSON string, held only in this server process.
- The agent's DID, e.g. did:web:agent.example.com
VOUCH_MCP_TRANSPORTenvTransport to serve: 'stdio' (default), 'http' (Streamable HTTP), or 'sse'.VOUCH_MCP_HOSTenvBind host when VOUCH_MCP_TRANSPORT=http (default 127.0.0.1).VOUCH_MCP_PORTenvBind port when VOUCH_MCP_TRANSPORT=http (default 8080).
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account vouch-protocol, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32466 servers in this category
- Published to the registry more recently than 16% of the other 32466 servers in this category
- Basic checks equal to or better than 100% of the other 32466 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Vouch MCP safe?
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.
What keys or codes does it need?
You need to fill in: VOUCH_PRIVATE_KEY, VOUCH_DID
Does it run on my computer or in the cloud?
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).
Is it still maintained?
The GitHub repo last changed –, and the latest version (2.0.1) reached the registry 4 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush
Alternatives
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
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
HotCodePush
by hotcodepush-team
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
Runs in the cloudUpdated today
Install
README from the maker
Open the README
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.
Vouch Protocol™
Vouch Protocol™ is a common-law trademark.
The Open Standard for Identity & Provenance of AI Agents
Quick Start
# Install (Linux and macOS). On Windows, use: pip install vouch-protocolcurl -fsSL https://vouch-protocol.com/install.sh | sh
Run vouch with no arguments and pick what you want to do
vouch
Prefer to do it by hand? It is three commands:
pip install vouch-protocolOne command to configure SSH signing + Vouch branding
vouch git init
All future commits are now signed and show ✅ Verified on GitHub
git commit -m "Secure commit"
Setting up an agent instead of git signing? vouch onboard --quick generates a working identity, allow-list, verifier, and heartbeat config in one command.
What's New in v1.0
Vouch Protocol v1.0 aligns directly with the open standard:
- Verifiable Credentials as the credential format (replacing v0.x JWS tokens).
- Data Integrity proofs with the
eddsa-jcs-2022cryptosuite (no JOSE, no Base64-wrapped payload, the credential remains human-readable JSON). - Multikey verification methods in DID Documents (algorithm-agnostic, ML-DSA-44 ready).
- Post-quantum profile as a Data Integrity proof set: the credential carries two independent proofs,
eddsa-jcs-2022andmldsa44-jcs-2024, an optional add-on for regulated deployments aligning with NIST CNSA 2.0 / NSM-10 timelines. - Three-way cross-implementation interop verified across Python, TypeScript, and Go.
Credentials are issued with Signer.sign() and checked with Verifier.verify(). See the Specification at vouch-protocol.com/specs/SPEC/ for the full specification.
The Open Standard for AI Agent Identity & Accountability
When Anthropic launched MCP, they solved "how agents call tools."
They didn't solve "how we TRUST those agents."
Vouch Protocol is the SSL certificate for AI agents.
Vouch is not one tool, it is a set of them. Here is the whole map.
On the command line
- `vouch init` generate an agent identity (a DID and keypair).
- `vouch sign` / `vouch verify` sign a payload and verify it.
- `vouch git` sign every git commit cryptographically, set up in one command, with a verified badge for your README.
- `vouch scan` find leaked Vouch key material in your code before it ships (a private key in a file, a seed in an env var, a DID document that accidentally carries a private key).
- `vouch attribute` separate who wrote which line. When an AI assistant and a human both edit a file, this records the AI's lines under the AI's own key and your lines under yours, so when a line causes an incident you can prove which of you wrote it. See the Claude Code integration.
- `vouch media` sign images, with C2PA support.
For your agents
- MCP server (`vouch-mcp`) a standalone Model Context Protocol server so any MCP client (Claude Desktop, Cursor, any agent) can create an identity, sign and verify credentials, scan for leaked keys, and decode DIDs, out of the box.
- Identity Sidecar keeps signing keys out of the model's context, so a prompt injection cannot read them.
- Vouch Shield a runtime check that inspects every tool call against your rules, like a customs officer at the door.
- Continuous trust heartbeats and session vouchers, so trust is a live signal that has to be renewed, not a badge that is issued once and trusted forever.
- Authority freshness a signed authority state with a counter that only goes up, so a state change (a fraud signal, a suspended mandate) collapses the acceptable freshness window to now for a high-consequence action, even when time-decay trust still passes. See docs/authority-freshness.md.
Framework integrations
Standalone packages that drop Vouch into the agent framework you already use. Each one issues a verifiable credential for a tool call, with optional delegation back to a human principal.
- `vouch-langchain` a LangChain tool that signs each tool call before it leaves the agent.
- `vouch-langgraph` signs LangGraph tool calls and graph nodes, so a signed trail runs across the whole graph.
- `vouch-crewai` a CrewAI tool, with supervisor-to-worker delegation that can only narrow authority, never widen it.
- `vouch-a2a` binds an A2A (Agent2Agent) Agent Card to a Vouch identity, so two agents can verify each other before they collaborate.
- `vouch-goose` registers the Vouch MCP server as an extension for Block's Goose agent, so a Goose session can sign and verify out of the box.
- `vouch-mlflow` signs an MLflow model artifact at registration time, bound to a content digest so any change to the weights breaks the signature.
- `vouch-safetensors` embeds a credential in a
.safetensorsheader, complementary to OpenSSF Model Signing, so a model carries who produced it.
The standalone `vouch-mcp` package above ships alongside these.
SDKs, in the language you use
Python, TypeScript, and Go are the full reference implementations. A Rust core with idiomatic Swift, JVM (Java and Kotlin), .NET, and C wrappers shares one codebase, so every language produces byte-identical output, verified against shared test vectors. A WebAssembly build is included for the browser and the edge. See the table further down for status per language.
Robots and embodied agents
A robot is an agent with a body, so identity and accountability matter even more once it can cause physical harm. The vouch.robotics module ships six capabilities on the same eddsa-jcs-2022 credentials as the rest of Vouch: hardware-rooted identity (bound to a TPM or secure element, so it cannot be cloned to other hardware), model and config provenance (re-signable on every OTA update), physical capability scope (force, speed, a tighter cap near humans, allowed zones, and shift windows, checked before each actuation, with narrow-only delegation), a robot-to-robot trust handshake, an encrypted tamper-evident black box with a verifiable kill switch, and a scannable offline passport. All six are implemented in Python, TypeScript, Go, and the Rust core, which flows to the Swift, Kotlin/JVM, .NET, C/C++, and WebAssembly wrappers, so a robotics credential signed in one language verifies in every other. Fifteen further capabilities round out the set: a living-trust heartbeat (a signed per-interval motion summary whose trust decays unless it is renewed in-envelope), two-level credential revocation (per-credential status lists and whole-DID kill), an accountable safety record (a tamper-evident incident ledger summarized into a portable signed record), signed perception provenance (each captured sensor frame's hash bound to the robot's key and hash-linked, so a robot can prove what its sensors saw and a substituted frame is detectable), an offline delegation lease (a short-lived, scope-bounded grant a disconnected robot verifies and acts on with no network call, nesting across vendors), a physical quorum (a cryptographic two-person rule requiring M of N attested approvers for a high-consequence action), lifecycle credentials (ownership transfer that chains into a verifiable chain of custody, key rotation that forms a key history, and a signed decommission that retires the robot), a regulatory conformance profile (a machine-checkable mapping from a robot's credentials to the clauses of ISO 10218 and 15066, the EU Machinery Regulation, the EU AI Act, and UL 3300, with a deterministic checker and a signed conformance attestation), post-quantum signing by default (robot credentials carry a proof set with an Ed25519 proof and an ML-DSA-44 proof, with backward-compatible verification, so a robot stays unforgeable across its decade-long life), and cross-embodiment identity continuity (an agent identity that moves between robot bodies, with an embodiment credential re-binding to each body's hardware root and a continuity chain that proves the same accountable agent persisted, plus a fork check), a physical custody handoff chain (a signed record of who accepted custody of a task or object at each hop across human and robot actors, so an incident traces to the exact hop and an attested condition localizes damage to the holder responsible), bounded infrastructure access (an operator-signed grant naming a resource, its permitted operations, an optional zone, and a time window, which a robot pairs with a signed request the resource authorizes offline, so a robot can open a door or dock at a charger with a tamper-evident, attributable, shrink-only record), fused-sensor provenance (a signed attestation binding a robot's fused world model to the exact set of input frame hashes and the fusion method that produced it, so a manipulated fusion result or a dropped input is detectable and every fused input traces to a frame the robot recorded), wear and degradation attest
Only the beginning is shown; read the rest in the repo