Skip to main content
Glama
Vvkmnn

claude-vigil-mcp

by Vvkmnn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to claude-vigil-mcp

No user-submitted related servers found.

    Related Servers

    • checkpointer

      IronKommander
      F
      license
      B
      quality
      C
      maintenance
      MCP server for file checkpointing and undo, enabling AI agents to safely read, write, and edit files with full snapshot history and revert capabilities.
      10
      -

    • Claude Memory

      AmmarJawad
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides Claude Code with persistent memory across sessions, including session checkpoints, image persistence, and bidirectional sync with claude.ai projects.
      1
      MIT

    • AgentOps Guardian MCP

      RZFL
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides on-demand safety for AI coding workflows, enabling inspection, review, checkpointing, and rollback of risky actions.
      24 npm
      1
      MIT

    • agentvc

      nintechio
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to checkpoint workspace state, branch parallel attempts, inspect diffs, and roll back to known-good states mid-task through MCP tools, with automatic safety checkpoints to prevent data loss.
      9 npm
      MIT

    • Memory Bank MCP

      spideynolove
      A
      license
      C
      quality
      D
      maintenance
      An MCP server that enables persistent memory, structured thinking sessions, and project-based knowledge management for Claude. It includes specialized coding tools for package discovery and reinvention prevention by validating code against existing libraries and APIs.
      17
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct operation on checkpoints: save, list, diff, restore, delete. There is no functional overlap, and descriptions clearly differentiate them.

    Naming Consistency5/5

    All tools follow the 'vigil_verb' pattern with snake_case (e.g., vigil_save, vigil_list). The naming convention is uniform and predictable.

    Tool Count5/5

    With 5 tools, the server is well-scoped for checkpoint management. Each tool covers a core function without redundancy or missing essential operations.

    Completeness5/5

    The tool set provides full lifecycle coverage: create (save), read (list), inspect (diff), update (restore), and delete. No obvious gaps for the domain of checkpoint management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources