Skip to main content
Glama
vladshykanov

mcp-postgres-guard

by vladshykanov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-postgres-guard

No user-submitted related servers found.

    Related Servers

    • postgres-mcp-query-tool

      nskha101
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives an AI agent scoped, safe access to your Postgres databases with per-connection access control, row caps, timeouts, and defense-in-depth read-only enforcement.
      -

    • pgwarden-mcp

      gokiwitech
      A
      license
      A
      quality
      C
      maintenance
      A Postgres MCP server that enables AI agents to safely access production databases through deny-by-default YAML policies, PII masking, row limits, and required predicates. It also provides DBA capabilities like index tuning, health checks, and EXPLAIN plans, with support for multiple databases.
      10
      MIT

    • AgenticMCP

      mattma87
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides secure, role-based access to PostgreSQL databases for AI agents.
      MIT

    • pg-schema-scout

      AkshaySwami14
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that provides targeted PostgreSQL schema access to AI agents, retrieving only relevant tables for a question and enforcing read-only access through multiple layers.
      4
      MIT

    • db-access-mcp

      Rheopyrin
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that gives AI agents access to configured databases (PostgreSQL, MySQL, Redshift, SQL Server) with SSH/AWS SSM tunnels, pluggable secret providers, and strict per-instance isolation.
      10
      46 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.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct action: listing tables, describing schema, executing read queries, and performing safe mutations. There is no overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: list_tables, describe_table, query, execute. The naming is predictable and clear.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose of providing safe database access. Each tool plays a necessary role without redundancy.

    Completeness4/5

    Covers essential operations: schema exploration, reading, and safe writes. Minor gap for multi-statement transactions, but the guard design prioritizes safety.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources