Skip to main content
Glama
Hamzah-Muhammad

SafeDataBaseMCP

by Hamzah-Muhammad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to SafeDataBaseMCP

No user-submitted related servers found.

    Related Servers

    • sqlite-guard-mcp

      Brandon-35
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to safely work with SQLite databases by enforcing read/write separation, dry-run writes with confirmation, automatic backups, and an audit trail.
      MIT

    • db-mcp

      paulushcgcj
      A
      license
      B
      quality
      A
      maintenance
      Enables LLM agents to query databases with read-only access, while requiring human approval for writes through a token-based confirmation system.
      6
      GPL 3.0

    • Safe DB Gateway

      Chantichalla
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to query PostgreSQL databases securely with read-only defaults, PII masking, rate limiting, and human-approved, expiring mutation tokens.
      9
      1
      Apache 2.0

    • Safe MCP Server

      Rajnish9444
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read local business data and request database mutations, while requiring human approval before updates or deletions are executed. It provides read-only tools, approval workflows, and audit logging to prevent autonomous destructive changes.
      -

    • Database MCP Server

      tomtomjskim
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely interact with multiple databases (MySQL, PostgreSQL) via natural language queries, with cross-database querying and enterprise-grade security.
      5 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

    A4.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: schema discovery, read-only querying, and the two-phase write flow are separated without overlap. The read/write boundary between run_query and propose_change is especially well-defined.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern: list_tables, describe_table, run_query, propose_change, confirm_change, list_pending_changes. The naming makes the action and target immediately predictable.

    Tool Count5/5

    Six tools is a well-scoped size for a safe database interface. Each tool earns its place, covering schema browsing, read-only access, write previewing, confirmation, and pending-change inspection without unnecessary bloat.

    Completeness4/5

    The core workflow is complete: browse schema, query data, propose changes, review pending changes, and commit. The only notable gap is the lack of an explicit way to cancel a pending change, though expiration partially covers this.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources