Vouch MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 77 installs a week from pypi. Last commit 26 Oct 2026.
Sign and verify W3C Verifiable Credentials so AI agents can cryptographically authorize actions.
What the code does
We read the source, 7 d ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
(os.path.join("share", package_name), ["package.xml", "README.md"]),
result = subprocess.run(cmd, shell=True, cwd=cwd or ROOT)
result = subprocess.run(cmd, shell=True, cwd=cwd or ROOT)
"public_key_b64": "KyhfHgZx+iAbKYCb4u+f4Ba1ZG94odoQaRWKiGSR7tvgpzoRlb6M38o4nQZYBjRrjBqMI6H3zQ46RFLPPhuQfAz7tOvtHQF0tZ9BnOUHNf18vyKh1BXybsQ2Ew7t6Xpydx/aaKGykUFCa+idY5VSJMqPvnqm+w+gg5axZNtDySoFc86mxMuv4vSrOls6rXdKt7qrUfoMJ/CMCwh6egSiYCnUt+Ays83F4Zf0/5TDAOMpi4jO6juW6ViOAlN3l/2Ky…
…</code>, it:\n </p>\n\n <ol>\n <li>Generates a new Ed25519 signing key (or uses your existing one at <code>~/.ssh/id_ed25519</code>)\n </li>\n <li>Uploads the key to GitHub as a signing key (via <code>gh</code> CLI)\n </li>\n <li>Configures Git to s…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Nothing serious here today
Today is the operative word: we check Vouch MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
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 vouch-mcp -e 'VOUCH_PRIVATE_KEY=<VOUCH_PRIVATE_KEY>' -e 'VOUCH_DID=<VOUCH_DID>' -- uvx vouch-mcp{
"mcpServers": {
"vouch-mcp": {
"command": "uvx",
"args": [
"vouch-mcp"
],
"env": {
"VOUCH_DID": "<VOUCH_DID>",
"VOUCH_PRIVATE_KEY": "<VOUCH_PRIVATE_KEY>"
}
}
}
}[mcp_servers.vouch-mcp]
command = "uvx"
args = ["vouch-mcp"]
env = { VOUCH_PRIVATE_KEY = "<VOUCH_PRIVATE_KEY>", VOUCH_DID = "<VOUCH_DID>" }{
"mcpServers": {
"vouch-mcp": {
"command": "uvx",
"args": [
"vouch-mcp"
],
"env": {
"VOUCH_DID": "<VOUCH_DID>",
"VOUCH_PRIVATE_KEY": "<VOUCH_PRIVATE_KEY>"
}
}
}
}{
"servers": {
"vouch-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"vouch-mcp"
],
"env": {
"VOUCH_DID": "<VOUCH_DID>",
"VOUCH_PRIVATE_KEY": "<VOUCH_PRIVATE_KEY>"
}
}
}
}Put your own values in place of
<VOUCH_PRIVATE_KEY> (The agent's signing key as a JWK JSON string, held only in this server process), <VOUCH_DID> (The agent's DID, e.g. did:web:agent.example.com).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
VOUCH_MCP_TRANSPORT (Transport to serve: 'stdio' (default), 'http' (Streamable HTTP), or 'sse'), VOUCH_MCP_HOST (Bind host when VOUCH_MCP_TRANSPORT=http (default 127.0.0.1)), VOUCH_MCP_PORT (Bind port when VOUCH_MCP_TRANSPORT=http (default 8080)).
Alternatives to Vouch MCP
same job, measured the same wayCryptographic identity for AI agents: W3C DIDs, Verifiable Credentials, post-quantum crypto
Cryptographically sound randomness for agents, with verifiable commit-reveal.
Cryptographically verifiable receipts of an agent's delegated work, verified offline.
Cryptographic audit trail for AI agents. Sign, verify, export. GDPR/HIPAA/EU AI Act.
Agent-native storage with cryptographic verification on Solana. Keyless: clients sign and pay.
Authorize and prove autonomous x402/AP2 agent payments with cryptographic receipts.
Cryptographically verifiable blockchain data with Merkle proofs + ECDSA signing.
Portable cryptographic identity for AI agents. Ed25519 keypairs and signed manifests.
Vouch MCP — questions
Answers built from our own checks of this server.