Skip to main content
Glama
BerkantACUN

pg-guard-mcp

by BerkantACUN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to pg-guard-mcp

No user-submitted related servers found.

    Related Servers

    • postgres-mcp

      nicolas-canfrere
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables safe interaction with PostgreSQL databases through read-only queries, schema exploration, and performance analysis.
      152 npm
      MIT

    • PostgreSQL MCP Server

      DemeoStep
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides secure, read-only access to PostgreSQL databases for schema inspection and data querying. It enables users to list tables, describe structures, and execute SELECT statements while strictly blocking destructive operations.
      7 npm
      1
      MIT

    • MCP PostgreSQL Read-Only

      japentaca
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables secure read-only access to PostgreSQL databases through SELECT queries only, with tools for exploring schemas, listing tables, and executing common queries while preventing any data modification operations.
      993 npm
      MIT

    • postgres-mcp

      pleware
      A
      license
      A
      quality
      B
      maintenance
      Enables read-only PostgreSQL interaction with enforced SQL security policies, including query validation, row limits, and timeouts.
      4
      MIT

    • postgres-explorer

      mathewsls
      F
      license
      A
      quality
      C
      maintenance
      Enables safe read-only exploration and querying of a PostgreSQL database, listing tables and executing SELECT statements.
      2
      -
    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.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: executing read-only queries, explaining query plans, listing tables, describing table schemas, and checking write privileges. There is no functional overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow the same pg_ prefix with a consistent verb_noun pattern: run_query, explain_query, list_tables, check_privileges, describe_table. The naming is uniform and predictable.

    Tool Count5/5

    Five tools is well-scoped for a PostgreSQL guard/observer server. Each tool serves a clear, non-redundant purpose and the set feels complete without being bloated.

    Completeness5/5

    The tool surface covers the core read-only workflow: exploring available tables, inspecting schemas, validating query plans, running queries, and verifying the security posture. No obvious dead ends or missing security-relevant operations are apparent.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources