Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Signed, hash-chained provenance receipts for AI agent actions.
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.
PROOF_LAYER_API_KEY, PROOF_LAYER_API_URL, PROOF_LAYER_TELEMETRYValues 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": {
"proof-layer": {
"command": "npx",
"args": [
"-y",
"@proof-layer/mcp"
],
"env": {
"PROOF_LAYER_API_KEY": "your-value",
"PROOF_LAYER_API_URL": "your-value",
"PROOF_LAYER_TELEMETRY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add proof-layer --env PROOF_LAYER_API_KEY=your-value --env PROOF_LAYER_API_URL=your-value --env PROOF_LAYER_TELEMETRY=your-value -- npx -y @proof-layer/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"proof-layer": {
"command": "npx",
"args": [
"-y",
"@proof-layer/mcp"
],
"env": {
"PROOF_LAYER_API_KEY": "your-value",
"PROOF_LAYER_API_URL": "your-value",
"PROOF_LAYER_TELEMETRY": "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": {
"proof-layer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@proof-layer/mcp"
],
"env": {
"PROOF_LAYER_API_KEY": "your-value",
"PROOF_LAYER_API_URL": "your-value",
"PROOF_LAYER_TELEMETRY": "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.
PROOF_LAYER_API_URL envPROOF_LAYER_TELEMETRY envThese 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 World-999-Labs, 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: PROOF_LAYER_API_KEY
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.1) reached the registry 6 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, MCP Server Autocad Lisp Helper
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.
High-precision static analysis and debug server for AutoCAD AutoLISP (.lsp) files.
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.
Cryptographic governance receipts for AI agents. Issued *before* the agent acts. Ed25519-signed. Hash-chained. Verifiable offline.
Built by WORLD999_LABS. Published on npm under
@proof-layer/*. The legacy@veridocs/*package names continue to resolve and forward to the new ones.
This is the public half of Proof Layer — the parts you install and run on your own machine:
| Package | What it does | npm |
|---|---|---|
@proof-layer/mcp | MCP server for Claude Desktop, Cursor, Cline, and any MCP-aware host | |
@proof-layer/verify | Standalone offline verifier — zero dependencies, audits any receipt bundle with just our public key |
The kernel (governance engine, Gauntlet adversary/judge pipeline, billing, dashboard) is closed-source and runs at prooflayer.world999labs.com. Open-source clients + closed-source server is the same pattern Stripe, Resend, and Vercel use — you get full transparency on what runs locally and what data leaves your machine, while the proprietary server logic stays protected.
npx -y @proof-layer/mcp@latest
Drop into Claude Desktop's claude_desktop_config.json:
{
"mcpServers": { "proof-layer": { "command": "npx", "args": ["-y", "@proof-layer/mcp@latest"], "env": { "PROOF_LAYER_API_KEY": "pl_live_...", "PROOF_LAYER_API_URL": "https://prooflayer.world999labs.com" } } } }
Restart Claude. Eight pl_* tools appear in the picker. Get an API key at prooflayer.world999labs.com.
Migrating from `@veridocs/mcp`? No code changes required. The legacy package name continues to resolve, the legacy
vd_*tool names continue to work alongsidepl_*, and existingVERIDOCS_API_KEY/VERIDOCS_API_URLenvironment variables are still accepted. You can switch the package name and env-var names on your own schedule.
Most "AI safety" tools run *after* the model has acted — toxicity filters, output classifiers, post-hoc audit logs. By the time the alarm fires, the agent has already sent the email, merged the PR, or executed the trade.
Proof Layer flips this:
EXECUTE / BLOCK / REVIEW / SHADOWA broken hash chain = tampering, immediately visible. A missing receipt = the agent acted without permission.
Receipts are designed to outlive us. Here's how to verify a bundle without ever calling our API:
import { verifyBundle } from "@proof-layer/verify";
import fs from "fs";
const bundle = fs.readFileSync("./receipts.ndjson", "utf8"); const publicKey = fs.readFileSync("./prooflayer-public-key.pem", "utf8");
const result = verifyBundle(bundle, publicKey); console.log(result); // { pass: 147, fail: 0, total: 147, chainBroken: false }
Public key is published at prooflayer.world999labs.com/v1/public-key and rotates on a published schedule.
MIT — see LICENSE.
The kernel and dashboard are proprietary and not included in this repo. The MCP server, verifier, and all client SDKs published under @proof-layer/* (and the legacy @veridocs/* names) are MIT-licensed.
Pull requests, issues, and feedback welcome. See CONTRIBUTING.md.