Skip to main content
Glama
owen-25-AI

TripWire MCP Server

by owen-25-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to TripWire MCP Server

No user-submitted related servers found.

    Related Servers

    • ContextLock

      LutaElbert
      A
      license
      Not graded
      quality
      A
      maintenance
      A local-first MCP safety layer that blocks dangerous files and redacts secrets before AI agents can access them, ensuring safe vibe coding.
      9 npm
      Apache 2.0

    • mcp-shield

      zsvvv
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP servers and local AI agents to safely interact with host environments by blocking indirect prompt injections, directory traversal, and malicious shell commands.
      MIT

    • airlock

      cjaston
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that vets package installations and shell commands to block dangerous actions by AI coding agents.
      6 npm
      1
      MIT

    • mcp-confirm

      les-k
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enforces single-use human confirmations for sensitive tool calls, sanitizes prompts against prompt injection, and re-validates file paths before destructive actions.
      MIT

    • guardian-mcp

      devmango1128
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to avoid irreversible mistakes by intercepting risky deletions, overwrites, and commands before execution, applying path, pattern, and blast-radius safeguards with quarantine backups.
      3
      9 npm
      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

    C2.4/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools have clearly distinct purposes: safe_exec routes commands into a sandbox, while rollback restores snapshots. There is no ambiguity between executing a command and restoring an earlier state.

    Naming Consistency3/5

    Both names use a single-word verb (safe_exec, rollback) without a noun component, showing some inconsistency with the typical verb_noun pattern. They're readable and somewhat consistent in being commands, but 'safe_exec' mixes an adjective+verb while 'rollback' is a single verb.

    Tool Count3/5

    Two tools is on the thin side even for a focused sandbox MCP server. The domain (sandbox command execution and snapshot management) could reasonably warrant a few more operations like listing snapshots or checking sandbox state.

    Completeness2/5

    There is no way to inspect snapshot state before executing or understand what command is being routed, and no visibility into sandbox status. The surface covers execution and rollback but leaves out key supporting operations that agents would need to make informed decisions.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources