MCP.Market

VibeRevert MCP server

by viberevert.com·com.viberevert/viberevert·v0.7.1-beta.4

Local MCP server for AI coding safety: risk checks, sessions, checkpoints, and fix prompts.

A86/100grade A
What users say
No reviews yet
Be the first
Safety scan
A86/100

full report

Adoption
Growing

0 stars241 downloads/wk

Reviews

Write one

Nobody has reviewed VibeRevert yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

VibeRevert tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • Code scan7 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 57 days ago12/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace7/10
Overall 86/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How VibeRevert compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
86/100
higher than 72% of 48,255 servers
Downloads a week
241
more than 78% of 12,191 servers with a package

Install VibeRevert in Claude Code, Cursor or VS Code

Runs npx -y viberevert on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add viberevert -- npx -y viberevert
Add to Cursor

What the publisher says

From the VibeRevert repository's README, as published. We do not edit it. Read it on GitHub

VibeRevert

Protect the project you're actually working on.

Record · Check · Fix · Restore.

VibeRevert is the project-integrity layer for AI coding. It records the real working state before an agent starts, flags risky changes with deterministic rules, and lets you remove the agent work you don't want without giving up the rest.

An agent changed 80 files. 75 are useful. Remove the 5 you don't.

No AI judges the AI: risk findings are reproducible, explainable, and based on rules you can inspect.

The working state you already had is part of the project. Staged work, unstaged edits and pre-existing untracked files are recorded before the session starts and preserved through recovery. You don't have to package your work into commits before letting an agent help with it.

Keep using your coding agent. VibeRevert works alongside Claude Code, Cursor, and other coding-agent workflows. Git worktrees give an agent an isolated checkout; VibeRevert protects and selectively recovers the working state an agent actually changes. They solve different problems and can be used together.

AI broke your project? Undo the session, not your week. Whole-session rollback is still one command.

See it work

The actual CLI, condensed from a real beta payment run — check flags it, and rollback previews what it will change before you --apply:

$ viberevert check
risk: CRITICAL · payments
  app/api/checkout/route.ts          payments   (critical)
  app/api/webhooks/stripe/route.ts   payments   (critical)

$ viberevert rollback <session>        # preview — nothing changed yet
  package.json                       tracked_restored
  app/page.tsx                       tracked_restored
  app/api/checkout/route.ts          untracked_deleted
  app/api/webhooks/stripe/route.ts   untracked_deleted
  lib/stripe.ts                      untracked_deleted
  .gitignore  README.md  (your uncommitted work)   skipped_unchanged

Proof, not promises

3 real AI coding sessions. 3 exact project-file restorations. Payments, database migrations, and deployment infrastructure — all with pre-existing uncommitted work preserved. Read the beta report →

Quickstart

Works inside a Git repository and requires Node.js 22+. VibeRevert keeps its records on your machine and requires no VibeRevert account or hosted service.

npm install -g viberevert@beta
viberevert init                # one-time setup in your project
viberevert run <your-agent>    # records the session and saves your files' starting state
viberevert check               # see what changed and what looks risky
viberevert rollback <session>  # preview putting your files back; add --apply to restore

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

VibeRevert: common questions

Is VibeRevert MCP server safe?
Yes, by our scan: it is graded A (86/100). Read the VibeRevert safety report
How do I install VibeRevert?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does VibeRevert need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is VibeRevert maintained?
The last commit was 58 days ago (2026-09-07). The latest release is v0.7.1-beta.4.
What can I use instead of VibeRevert?
Servers from other publishers that do the same job: Deja Vu MCP server.
How does VibeRevert compare with other MCP servers?
safety score 86/100 (higher than 72% of 48,255 servers); downloads a week 241 (more than 78% of 12,191 servers with a package). Full comparison.

Alternatives to VibeRevert

Same job from other publishers: the closest match first, then the best rated.

  • Deja Vu
    deja-vu: local memory over the session histories of forty-three coding agents.
    A