Skip to main content
Glama
possibly6

safe-migrations-mcp

by possibly6

Related Servers

Alternatives to safe-migrations-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that puts a human approval gate in front of long-running autonomous processes, with tools for proposals, process control, logs, parameters, records, and optional EVM balance checks.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      This MCP server provides secure access to databases for AI agents, enforcing authentication, authorization, human approval, logging, and notifications to prevent dangerous actions.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides impact preview and approval workflow for AI agent actions, allowing users to see diffs and risk assessments before any changes are executed.
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      A governed MCP server that enforces a trust layer between AI agents and databases, requiring sign-off on joins and metrics and producing auditable receipts for every query.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server exposing scoped, read-only enterprise operations tools with fail-closed credential handling. It returns opaque approval IDs for mutations and requires a separate operator approval command to release one-time capabilities.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that acts as an authorization gateway between an AI agent and external systems, deterministically refusing actions that exceed granted authority and sealing every decision into an auditable chain of custody.
      -

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: proposing, simulating, applying, rolling back, inspecting config/schema, getting history, and cleanup. No overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern (e.g., apply_change, inspect_schema). Verbs are descriptive and standardized.

    Tool Count5/5

    8 tools is well-scoped for a migration server. It covers the core workflow without being excessive or insufficient.

    Completeness5/5

    The tool surface covers the full migration lifecycle: propose, simulate, apply, rollback, history, inspection, and cleanup. No obvious gaps for its intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues