Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Causal Proof Engine for AI agents: signed log, zero vectors, failures traced to their cause.
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.
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": {
"vestige": {
"command": "npx",
"args": [
"-y",
"vestige-mcp-server"
]
}
}
}Run this in your terminal
claude mcp add vestige -- npx -y vestige-mcp-serverPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"vestige": {
"command": "npx",
"args": [
"-y",
"vestige-mcp-server"
]
}
}
}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": {
"vestige": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"vestige-mcp-server"
]
}
}
}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 samvallad33, 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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 (4.2.0) reached the registry 23 days 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, Date Math
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.
Date/time math for agents: business days, holidays, time zones, cron, RRULE. 25 free calls/day.
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.
Think before doing. Prove before saving. Memory is root cause, not search.
Quick Start · Why We Ripped Out Vectors · S.T.R.A.T.A. Engine · The 6 MCP Verbs · Reflex Hooks · Vestige Operator
Every other AI memory tool on the market is a passive scrapbook built on unordered vector soup. Every other AI security tool is a stateless bouncer with complete amnesia.
When an autonomous coding agent breaks a build at 3:00 PM because a configuration flag was silently flipped at 9:00 AM, Vector RAG fails 100% of the time:
ConnectionPoolExhaustedException) shares 0% semantic similarity with the 9:00 AM config edit (max_idle_time = 0).Vestige v6.2 ends the guessing game. We ripped out ONNX, deleted vector embeddings, deleted keyword search, and deleted SQLite. In their place is a ~7.8 MB, 100% offline-verified Rust execution kernel that unifies pre-execution security gating, autonomic lifecycle hooks (reflex.sock), and backward causal credit assignment into a single closed-loop nervous system.
An Independent Study of 757 Agent Memory Systems ([Agent Memory Atlas](https://github.com/samvallad33/vestige)):
*"Every system in this atlas builds the ascent (extraction and retrieval). Almost none completes the descent (correction and forgetting)."*
Vestige is built for the descent.
One command installs the vestige-mcp Rust daemon, wires the 4 autonomic Reflex hooks into your IDE (Claude Code, Cursor, Codex, Windsurf, Gemini CLI), and replays your last 30 days of agent transcripts against our 114-rule gate to show every destructive command or failure loop Vestige would have stopped.
Operator is the guard for your agent's tool calls. npx @vestige/init --guard installs 102 STOP rules, OP-000 through OP-114, with OP-086–OP-097 and OP-100 reserved. It stops force pushes, dropped tables, recursive deletes, production deploys, credential reads and the rest of that closed list before they run, even when the command is disguised. Classification is deterministic: no model call and no network call. Operator Lite (numbered rules OP-000 through OP-025) is pinned beside the gate and judges every call too. An existing ~/.operator/gate/operator-gate.py is left in place.
npx @vestige/init
Verify your live cryptographic store and 6-tool surface at any time:
vestige precedent --query verify_log
The 102-rule gate is in this repository and is what --guard installs. See operator/README.md. board, letter, almost-forgot, onboard and briefing load companion modules when those files sit next to the gate. Buy Vestige Operator is the owner's copy of those companions: $149 once, every later version included, and a 30-day refund.
Underneath Vestige sits S.T.R.A.T.A. (*Sequential Topological Reasoning for Autonomous Transaction Authorization*)—an append-only, cryptographic execution ledger that replaces fuzzy similarity with mathematical provenance:
BLAKE3 hash of the frame before it. Nightly segments are sealed with Ed25519 signatures.id, tag, commit: , hunk-level touched file edges, and interned stack-trace symbols). Free-text guessing is refused—and on refusal, Handle Discovery automatically parses your query to return exact candidate handles found in your words.~/.vestige/reflex.sock) bridges external shell hooks directly into the hot in-memory Strata graph in <0.2ms—eliminating .serve.lock contention across multiple concurrent IDE windows.causal_walk(action="prove")).Standard MCP servers wait passively for an LLM to remember to call a tool. Vestige operates like a human nervous system: Reflex Hooks act as the spinal cord (firing automatically in 0 LLM turns and <0.2ms), while the 6 MCP Tools act as the deliberate prefrontal cortex.
┌────────────────────────────────────────┐
│ Model Prefrontal Cortex (6 Verbs) │ │ session · remember · recall · │ │ causal_walk · curate · precedent │ └──────────────────┬─────────────────────┘ │ stdio / JSON-RPC ▼ ┌──────────────────────┐ Unix Domain Socket ┌────────────────────────────────────────┐ │ Reflex Hooks Engine │ ◄───────────────────► │ vestige-mcp Server Daemon │ │ (Spinal Cord) │ ~/.vestige/reflex.sock│ ┌───────────────────────────────────┐ │ │ │ (<0.2ms Zero-Lock) │ │ In-Memory Strata Graph (Hot RAM) │ │ │ • SessionStart │ │ │ • FSRS-6 scheduler state │ │ │ • PreToolUse (114) │ │ │ • Exact Handle & Symbol Index │ │ │ • PostToolUse (RSB) │ │ │ • Causal DAG & Backfill Engine │ │ │ • PreCommit (Prove) │ │ └─────────────────┬─────────────────┘ │ └──────────────────────┘ │ Exclusive Write Lock ▼ ┌────────────────────────┐ │ Append-Only Strata Log │ │ (BLAKE3 + Ed25519) │ └────────────────────────┘
id, tag, last_touched_file, and FSRS-6 retrievability) plus pinned repo rules. Your agent starts Turn 1 already holding the exact handles it needs.Bash, Edit, or Write executes, Vestige runs 114 deterministic security rules (catching obfuscated shell commands, r''m, $IFS, ANSI-C quoting, base64 pipes, destructive SQL/git, and multi-step credential exfiltration) AND checks if the target file is linked to an un-recalled failure node in Strata. If a landmine exists, Reflex warns the agent with the exact handle (mem-xxxx) *before* it repeats a mistake.exit_code != 0, Reflex automatically records a signed failure frame in Strata, triggers Retroactive Salience Backfill across upstream touched nodes, surfaces any faded forgotten_lesson (retrievability < 0.5), and appends the exact causal_walk command directly to the tool output.git commit or gh pr create after a logged failure in the current trajectory, Reflex verifies that a cryptographically signed prove bisect witness exists for the fix.Most MCP servers drown agents in 18–30 overlapping tool schemas—burning ~2,500 prompt tokens per turn and confusing smaller models. In v6.2, Vestige compresses its entire capability set into 6 flat-JSON cognitive verbs (while preserving internal backward-compatible aliases for all 18 legacy tool names):
| MCP Tool | Cognitive Intent | Key Actions & Capabilities |
|---|
| `1. session` | *Boot, Plan & Project* | action: "start" \| "status" \| "set_intention" \| "check_intentions" \| "complete_intention" \| "project" Manages cross-session prospective intentions, store health/stats, and compiles lock-free CLAUDE.md / AGENTS.md context fences directly from RAM. | | `2. remember` | *The Single Gated Write* | Flat parameters: content, tags, repo_path, files, is_decision. Automatically anchors codebase records when repo_path/files are present, runs inline Retroactive Salience Backfill (returning backfilled_handles), and auto-updates CLAUDE.md when tagged "pinned". | | `3. recall` | *Exact-Handle Read* | Flat parameters: handle, detail_level, query. Resolves exact IDs, prefixes, tags, or repo context (get_context). Returns structured discovered_handles: [...] if free text is passed so the agent self-corrects on the immediate next turn. | | `4. causal_walk` | *Root Cause & Bisect Proof* | action: "walk" \| "prove", from_handle, good_ref, bad_ref, test_cmd. • "walk": Auto-gathers GitHub issue/PR windows, walks hunk-level touched and git log -L ancestry backward, and auto-attaches faded forgotten_lesson nodes. • "prove": Executes a frozen-protocol git bisect against test_cmd and writes a signed Strata witness card. | | `5. curate` | *Graph & State Mutation* | action: "promote" \| "demote" \| "edit" \| "link" \| "bridge" \| "connect_identities" \| "suppress" Adjusts FSRS-6 stability weights, wires explicit causal links, bridges cross-project structural similarities (ghostlink), joins shared entity identities, or permanently suppresses invalid records with a signed audit receipt. | | `6. precedent` | *Receipts & Integrity Audit* | query: "stops" \| "receipt" \| "replay" \| "verify_log" \| "scan_secrets" \| "selftest" Inspects Operator gate stops, replays write receipts, scans for credent
Only the beginning is shown; read the rest in the repo