Skip to main content
Glama
SafeDataBaseMCP

SafeDataBaseMCP

Related Servers

Alternatives to SafeDataBaseMCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to safely explore and query SQL databases through read-only, AST-checked SQL, database-enforced read-only transactions, timeouts, row caps, PII masking, and audit logging.
      MIT
    • A
      license
      Not graded
      quality
      D
      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
    • A
      license
      B
      quality
      B
      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
    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to explore and query a SQL database safely, answering questions with real data while blocking writes, hiding protected columns, restricting results to one tenant's rows, and logging every call to an audit trail.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to safely query and operate SQL databases with per-statement risk grading, two-phase confirmation for dangerous operations, and access-level enforcement. Every action is recorded in a tamper-evident hash-chain audit log with integrity verification.
      MIT

    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

    ActivityStale
    ResponsivenessNo recent community issues