Skip to main content
Glama
narekmalk

safedb-mcp

by narekmalk

Related Servers

Alternatives to safedb-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      B
      maintenance
      An MCP server that enables AI agents to securely interact with PostgreSQL databases with least-privilege scopes, PII masking, and human approval for writes.
      4
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides safe, read-only SQL access for AI agents to query databases (PostgreSQL, MySQL, SQLite) with schema awareness and guardrails.
      1 npm
      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
      B
      maintenance
      A security-first, read-only MCP server for AI assistants to safely query MySQL, PostgreSQL, and Redis with layered safety checks.
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      A governed analytics MCP server that provides LLM agents with safe, read-only access to data warehouses through a layered safety pipeline including AST validation, column/row governance, PII masking, cost limits, and audit.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides a read-only SQL MCP server with guard rails including table visibility, column masking, row and time caps, and an audit trail, enabling safe database access for agents without granting full write permissions.
      MIT

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of database safety: listing schemas/tables, describing columns, running queries, explaining queries, and retrieving policy. No overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (describe_table, explain_query, get_safedb_policy, list_schemas, list_tables, run_readonly_query). No deviations.

    Tool Count5/5

    Six tools cover the core functionality of a read-only safe database interface without being excessive or sparse. Each tool serves a clear and necessary role.

    Completeness5/5

    The tool set provides full lifecycle for read-only access: listing schemas/tables, describing structure, executing queries with EXPLAIN, and fetching policy. No obvious gaps for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues