Skip to main content
Glama
mahin1995

postgres-mcp-readonly

by mahin1995

Related Servers

Alternatives to postgres-mcp-readonly

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server for PostgreSQL that enables safe read-only database queries, table schema inspection, and query execution planning.
      6
      17
      BSD 3-Clause
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a read-only PostgreSQL MCP server with schema introspection. Enforces least-privilege database roles to prevent any writes, even from malicious SQL.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server for PostgreSQL that enables safe database introspection and querying via natural language.
      300
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Read-only PostgreSQL MCP server that enables running SELECT queries, listing tables and schemas, and describing columns, with built-in protection against writes and malicious SQL attacks.
      300
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for safe read-only PostgreSQL exploration and querying, enforced by three independent layers: startup privilege audit, lexical guard, and read-only transactions. Offers tools for querying, table listing, schema description, relationship mapping, and query explanation.
      18
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A secure MCP server that enables querying PostgreSQL databases through an SSH tunnel with enforced read-only access, connection pooling, and comprehensive data exploration tools.
      -

    TDQS

    A3.6/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (querying, counting, previewing, explaining, validating). However, validate_insert is a subset of validate_sql, and table_info can duplicate indexes/constraints/relationships for a single table, creating minor confusion.

    Naming Consistency4/5

    All tools use the same 'db.' prefix and snake_case, which is consistent. However, the second part mixes nouns (databases, schema, query) and verbs (validate_insert, explain, watch), so the pattern is not strictly verb_noun but still predictable.

    Tool Count5/5

    14 tools is well within the ideal range for a dedicated read-only database server. Each tool addresses a distinct need without excessive redundancy, and the count feels appropriate for the scope.

    Completeness5/5

    The server covers all typical read-only operations: listing databases, inspecting schema, querying, counting, previewing, sampling, explaining, and validating writes without executing. It also includes incremental polling, making it a comprehensive surface for a read-only Postgres MCP server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues