Skip to main content
Glama
Svaca33

pgverdict

by Svaca33
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to pgverdict

No user-submitted related servers found.

    Related Servers

    • postgres-mcp

      Yash-0620
      A
      license
      A
      quality
      B
      maintenance
      A Postgres MCP server with index tuning, explain plans, health checks, and safe SQL execution for AI agents.
      9
      MIT

    • DB-Performance-MCP

      Srijan-120
      F
      license
      Not graded
      quality
      C
      maintenance
      A Python-based MCP server that analyzes PostgreSQL query plans, suggests indexes, and checks pagination safety to help optimize database performance.
      -

    • Postgres MCP Pro

      it-romanov
      A
      license
      B
      quality
      C
      maintenance
      An open-source MCP server for PostgreSQL that provides database health analysis, index tuning, query plan optimization, and safe SQL execution, suitable for both development and production environments.
      9
      MIT

    • postgres-mcp

      Leon-Achteresch
      A
      license
      A
      quality
      B
      maintenance
      MCP server for PostgreSQL that enables schema exploration, safe SQL execution, EXPLAIN analysis, health checks, and index recommendations across multiple databases.
      10
      67 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 8 tools

    Disambiguation5/5

    Each tool maps to a distinct stage of the PostgreSQL optimization workflow: profile selection, hotspot identification, plan explanation, dead index detection, candidate simulation, real verification, parameter recovery, and migration generation. The descriptions explicitly separate similar-sounding tools like propose_index and verify_index, leaving no real boundary ambiguity.

    Naming Consistency5/5

    All eight tool names follow the same snake_case verb_noun pattern: list_profiles, list_hotspots, explain_query, find_dead_weight, propose_index, verify_index, recover_parameters, generate_migration. The action verbs are predictable and each noun clearly indicates the target object.

    Tool Count5/5

    Eight tools is a well-scoped size for this domain. Each tool earns its place by covering a distinct phase of the query verification loop, with no obvious redundancy or bloat.

    Completeness4/5

    The core verification lifecycle is covered end-to-end: identify hotspots, explain plans, propose and verify indexes, recover real parameters, and generate migrations. Minor peripheral gaps exist, such as profile lifecycle management and an explicit verification-record listing tool, but they do not block the primary workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources