viberevert
Related Servers
Alternatives to viberevert
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceAI code reviews and git activity digests with machine-readable risk scoring, available as an MCP server for use within an agent session.1MIT
- AlicenseNot gradedqualityCmaintenanceLocal-first code intelligence and safety layer for AI coding agents. MCP server exposes dependency graph, impact analysis, and AST-compressed repo context, backed by typed local memory, patch-scope safety gates, and git-independent transaction rollback.1MIT
- AlicenseCqualityDmaintenanceSecurity scanner and MCP server that catches dangerous patterns in MCP servers and AI agent projects, such as leaked secrets, shell execution, and prompt-injection text. Runs as both a CLI and MCP server with CI-friendly severity gates.21MIT
- AlicenseNot gradedqualityAmaintenanceA secure, local-first MCP server for read-only inspection and troubleshooting of development environments, exposing narrow, typed, auditable capabilities for repository inspection, log summarization, Docker review, and security scanning without granting unrestricted machine access.MIT
- AlicenseNot gradedqualityCmaintenanceOpen-source AI code review MCP server for local git diff auditing with deterministic security rules and AI-powered analysis using any OpenAI-compatible model.4MIT
- AlicenseCqualityBmaintenanceA policy-aware MCP server for GitHub and GitHub Actions that enables safe AI-assisted infrastructure workflows—inspecting repositories, preparing branches and pull requests, and constrained remote mutations behind explicit preview-bound approval tokens.18MIT
TDQS
Scored across 8 tools
Most tools have clearly distinct roles (create checkpoint, run checks, configure policy, start session), and the report-consuming tools produce different outputs. However, create_checkpoint and start_session overlap in checkpoint creation, and explain_diff, classify_risk, and list_risky_files all operate on check reports, requiring careful reading to choose the right one.
All tool names follow a consistent verb_noun snake_case pattern: create_checkpoint, check_repo, explain_diff, classify_risk, list_risky_files, get_policy, start_session, generate_fix_prompt. There is no mixed casing, vague single-word verbs, or inconsistent naming style.
Eight tools is a well-scoped surface for a checkpoint and safety-reporting server. Each tool covers a recognizable stage of the workflow, and none feel like duplicates or padding.
The server can create checkpoints, start sessions, run checks, and analyze reports, but there is no end/abort session tool, no revert or rollback operation despite the server being named VibeRevert, and no way to manage checkpoints beyond creating them. These are significant gaps that leave core workflows incomplete.