Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Vestige

by samvallad33version 4.2.0i★ –iRuns on your computer
Registry nameio.github.samvallad33/vestige

Install

Overview

Description from the maker (original English)

Causal Proof Engine for AI agents: signed log, zero vectors, failures traced to their cause.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

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

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).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx 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": {
    "vestige": {
      "command": "npx",
      "args": [
        "-y",
        "vestige-mcp-server"
      ]
    }
  }
}

Run this in your terminal

claude mcp add vestige -- npx -y vestige-mcp-server

Open in Cursor

Or copy the settings yourself

Paste 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.

Open in VS Code

Or copy the settings yourself

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.

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 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account samvallad33, 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 18353 servers in this category
  • Published to the registry more recently than 66% of the other 18353 servers in this category
  • Basic checks equal to or better than 100% of the other 18353 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 Vestige 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?

The registry does not list a required key, though some servers ask you to sign in on first use.

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 (4.2.0) reached the registry 23 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Date Math

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

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

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 2 days ago
Install

Date Math

by JowenDelaPena

Date/time math for agents: business days, holidays, time zones, cron, RRULE. 25 free calls/day.

Computer or 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.

VESTIGE v6.2

The Ring-0 Autonomic Execution Kernel & World's First Causal Proof Engine for AI Agents

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


🚨 The Industry Lie: Memory Is Not a Search Engine

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:

  1. The 3:00 PM stack trace (ConnectionPoolExhaustedException) shares 0% semantic similarity with the 9:00 AM config edit (max_idle_time = 0).
  2. Cosine similarity retrieves plausible-looking decoys instead of the causal ancestor.
  3. The agent guesses, edits the wrong file, fails again, and enters a $50,000 infinite retry loop.

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.


⚡ Quick Start (30 Seconds)

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

🏛️ S.T.R.A.T.A. — The World's First Causal Proof Engine

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:

  • Sequential (`BLAKE3` + `Ed25519`): Every memory write, tool call, and gate stop is recorded as an immutable frame carrying the BLAKE3 hash of the frame before it. Nightly segments are sealed with Ed25519 signatures.
  • Topological (`causal_walk`): Memories are indexed by exact handles (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.
  • Reasoning (`FSRS-6` + `Retroactive Salience Backfill`):
  • FSRS-6 Decay (Precision Forgetting): Unverified, unreferenced session noise automatically decays out of working memory so context windows stay razor-sharp.
  • Retroactive Salience Backfill (Runtime Credit Assignment): When a downstream failure or high-salience constraint lands, Vestige immediately walks the topological DAG backward on save, rescues the quiet upstream root-cause memory from FSRS-6 decay, boosts its salience, and writes a reversible cryptographic receipt.
  • Autonomous (`reflex.sock`): A zero-lock Unix Domain Socket (~/.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.
  • Transaction Authorization (`Operator` + `prove`): Every agent action is treated as an untrusted transaction that must pass 114 pre-execution rules before running and can be verified post-fix via deterministic git-bisect test witnesses (causal_walk(action="prove")).

🧠 The Autonomic Dual-Tier Architecture

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) │ └────────────────────────┘


⚡ The 4 Autonomic Reflex Arcs (0-Turn Cognitive Injection)

  1. `Reflex::SessionStart` (Active Handle Map Injection): On boot, resume, or context compaction, Vestige queries the local Git index against the hot Strata graph and injects the Top 5 Hot Entity Handles (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.
  2. `Reflex::PreToolUse` (114 Gate Rules + Landmine Interception): Before 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.
  3. `Reflex::PostToolUse` (Auto-Failure Capture + Inline Backfill): Whenever a command exits with 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.
  4. `Reflex::PreCommit` (Proof-Carrying PR Enforcement): When an agent runs 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.

🛠️ The 6-Verb MCP Surface

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 ToolCognitive IntentKey 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

Ask PopNx