Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Causal Proof Engine for AI agents: signed log, zero vectors, failures traced to their cause.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"vestige": {
"command": "npx",
"args": [
"-y",
"vestige-mcp-server"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add vestige -- npx -y vestige-mcp-serverPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"vestige": {
"command": "npx",
"args": [
"-y",
"vestige-mcp-server"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"vestige": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"vestige-mcp-server"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub samvallad33, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (4.2.0) llegó al registro hace 22 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, First Sale Scout
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Playbooks and a 14-day checklist for founders winning their first paying customers.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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
Solo se muestra el principio; lee el resto en el repo