Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.sparta2025/postgres-mcp

PYPI · POSTGRES-MCP-PRO · SCANNED SEP 20

PostgreSQL MCP server with 15 tools (SQL, EXPLAIN, health, indexes) plus a Gradio UI with LLM chat.

Available components

pypi · postgres-mcp-pro 59
+4 this week 59 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security32
  • Malware scan not yet available for this package.Unverified
  • CVE check failed: a known high-severity CVE affects gradio 5.50.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 9 of 112 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1509 tokens (~100/item across 15 items; 15 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_sql" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.sparta2025/postgres-mcp server?

io.github.sparta2025/postgres-mcp runs locally as a PyPI package, launched with uvx postgres-mcp-pro. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · postgres-mcp-pro

# add to Claude Code
claude mcp add sparta2025-postgres-mcp -- uvx postgres-mcp-pro
// .cursor/mcp.json
{
  "mcpServers": {
    "sparta2025-postgres-mcp": {
      "command": "uvx",
      "args": [
        "postgres-mcp-pro"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "sparta2025-postgres-mcp": {
      "command": "uvx",
      "args": [
        "postgres-mcp-pro"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add sparta2025-postgres-mcp -- uvx postgres-mcp-pro
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sparta2025-postgres-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "postgres-mcp-pro"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add sparta2025-postgres-mcp --command uvx --arg postgres-mcp-pro
# ~/.hermes/config.yaml
mcp_servers:
  sparta2025-postgres-mcp:
    command: "uvx"
    args: ["postgres-mcp-pro"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "sparta2025-postgres-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "postgres-mcp-pro"
      ]
    }
  }
}
# add to Vellum
assistant mcp add sparta2025-postgres-mcp -t stdio -c uvx -a postgres-mcp-pro
// mcp.json
{
  "mcpServers": {
    "sparta2025-postgres-mcp": {
      "command": "uvx",
      "args": [
        "postgres-mcp-pro"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1
    • CVE-2026-54274 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-25990 affects this package: high ▼ security
    • CVE-2026-59200 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-48817 affects this package: high ▼ security
    • CVE-2026-28416 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-54283 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-49119 affects this package: high ▼ security
    • CVE-2026-27167 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-54058 affects this package: high ▼ security
    • CVE-2026-54282 affects this package: high ▼ security
    • CVE-2026-59205 affects this package: high ▼ security
    • CVE-2026-59198 affects this package: high ▼ security
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-48710 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-42311 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-59204 affects this package: high ▼ security
    • CVE-2026-42310 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-10783 affects this package: high ▼ security
    • CVE-2026-42309 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-28415 affects this package: high ▼ security
    • CVE-2026-48545 affects this package: high ▼ security
    • CVE-2026-54060 affects this package: high ▼ security
    • CVE-2026-48818 affects this package: high ▼ security
    • CVE-2026-28414 affects this package: high ▼ security
    • CVE-2026-59197 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-40192 affects this package: high ▼ security
    • CVE-2026-42308 affects this package: high ▼ security
    • CVE-2026-55380 affects this package: high ▼ security
    • CVE-2026-59881 affects this package: high ▼ security
    • Stability: 0.97 → pass security
  • 19 Sept 26 0
    • CVE-2026-49119 affects this package: high ▼ security
    • CVE-2026-40192 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-59197 affects this package: high ▼ security
    • CVE-2026-28414 affects this package: high ▼ security
    • CVE-2026-48818 affects this package: high ▼ security
    • CVE-2026-54060 affects this package: high ▼ security
    • CVE-2026-48545 affects this package: high ▼ security
    • CVE-2026-28415 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-42309 affects this package: high ▼ security
    • CVE-2026-10783 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-42310 affects this package: high ▼ security
    • CVE-2026-59204 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-42311 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-48710 affects this package: high ▼ security
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-59198 affects this package: high ▼ security
    • CVE-2026-59205 affects this package: high ▼ security
    • CVE-2026-54282 affects this package: high ▼ security
    • CVE-2026-54058 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-27167 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-54283 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-28416 affects this package: high ▼ security
    • CVE-2026-48817 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-59200 affects this package: high ▼ security
    • CVE-2026-25990 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-42308 affects this package: high ▼ security
    • CVE-2026-55380 affects this package: high ▼ security
    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
  • 18 Sept 26 +1
    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-55380 affects this package: high ▼ security
    • CVE-2026-40192 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-59197 affects this package: high ▼ security
    • CVE-2026-28414 affects this package: high ▼ security
    • CVE-2026-48818 affects this package: high ▼ security
    • CVE-2026-54060 affects this package: high ▼ security
    • CVE-2026-48545 affects this package: high ▼ security
    • CVE-2026-28415 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-42309 affects this package: high ▼ security
    • CVE-2026-10783 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-42310 affects this package: high ▼ security
    • CVE-2026-59204 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-42311 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-48710 affects this package: high ▼ security
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-59198 affects this package: high ▼ security
    • CVE-2026-59205 affects this package: high ▼ security
    • CVE-2026-54282 affects this package: high ▼ security
    • CVE-2026-54058 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-27167 affects this package: high ▼ security
    • CVE-2026-49119 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-54283 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-28416 affects this package: high ▼ security
    • CVE-2026-48817 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-59200 affects this package: high ▼ security
    • CVE-2026-25990 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-42308 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
  • 17 Sept 26 0
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-40192 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-59197 affects this package: high ▼ security
    • CVE-2026-28414 affects this package: high ▼ security
    • CVE-2026-48818 affects this package: high ▼ security
    • CVE-2026-54060 affects this package: high ▼ security
    • CVE-2026-48545 affects this package: high ▼ security
    • CVE-2026-28415 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-42309 affects this package: high ▼ security
    • CVE-2026-10783 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-42310 affects this package: high ▼ security
    • CVE-2026-59204 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-42311 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-48710 affects this package: high ▼ security
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-59198 affects this package: high ▼ security
    • CVE-2026-59205 affects this package: high ▼ security
    • CVE-2026-54282 affects this package: high ▼ security
    • CVE-2026-54058 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-27167 affects this package: high ▼ security
    • CVE-2026-49119 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-54283 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-28416 affects this package: high ▼ security
    • CVE-2026-48817 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-59200 affects this package: high ▼ security
    • CVE-2026-25990 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-42308 affects this package: high ▼ security
    • CVE-2026-55380 affects this package: high ▼ security
    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
  • 16 Sept 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
    • CVE-2026-55380 affects this package: high ▼ security
    • CVE-2026-42308 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-25990 affects this package: high ▼ security
    • CVE-2026-59200 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-48817 affects this package: high ▼ security
    • CVE-2026-28416 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-54283 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
  • 14 Sept 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 12 Sept 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 10 Sept 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed pypi/postgres-mcp-pro@0.4.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 89 findings
ID CVE Severity Vector Fix available
GHSA-2fqr-mr3j-6wp8 CVE-2026-54279 low yes
GHSA-4fvr-rgm6-gqmc CVE-2026-54273 medium yes
GHSA-4m7w-qmgq-4wj5 CVE-2026-54275 low yes
GHSA-63hw-fmq6-xxg2 CVE-2026-54277 medium yes
GHSA-9x8q-7h8h-wcw9 CVE-2026-54280 low yes
GHSA-cq5v-8q36-5273 CVE-2026-69244 high yes
GHSA-g3cq-j2xw-wf74 CVE-2026-54278 medium yes
GHSA-hg6j-4rv6-33pg CVE-2026-47265 medium yes
GHSA-hpj7-wq8m-9hgp CVE-2026-54276 medium yes
GHSA-jg22-mg44-37j8 CVE-2026-34993 medium CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:H/A:L yes
GHSA-m6qw-4cw2-hm4m CVE-2026-50269 low yes
GHSA-mfx4-hv73-q22v CVE-2026-69243 medium yes
GHSA-mq44-7p77-q5h7 CVE-2026-59881 medium yes
GHSA-xcgm-r5h9-7989 CVE-2026-54274 medium yes
PYSEC-2026-2104 CVE-2026-34993 high CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H yes
PYSEC-2026-2105 CVE-2026-47265 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
PYSEC-2026-2106 CVE-2026-50269 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2107 CVE-2026-54273 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2108 CVE-2026-54274 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2109 CVE-2026-54276 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
PYSEC-2026-2110 CVE-2026-54277 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2111 CVE-2026-54278 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2112 CVE-2026-54279 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2113 CVE-2026-54280 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-237 CVE-2026-54275 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-3545 CVE-2026-69244 none yes
PYSEC-2026-3546 CVE-2026-69243 none yes
PYSEC-2026-3547 CVE-2026-59881 none yes
GHSA-39mp-8hj3-5c49 CVE-2026-28414 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-6655-8ph2-63j3 CVE-2026-10783 low CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N yes
GHSA-7hp7-4p35-3cx2 CVE-2026-48545 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N yes
GHSA-h3h8-3v2v-rg7m CVE-2026-27167 none CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:N yes
GHSA-jmh7-g254-2cq9 CVE-2026-28416 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-pfjf-5gxr-995x CVE-2026-28415 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N yes
PYSEC-2026-211 CVE-2026-10783 low CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N no
PYSEC-2026-2178 CVE-2026-48545 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N yes
PYSEC-2026-2179 CVE-2026-49119 none yes
PYSEC-2026-63 CVE-2026-27167 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N yes
PYSEC-2026-64 CVE-2026-28414 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
PYSEC-2026-65 CVE-2026-28415 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N yes
PYSEC-2026-66 CVE-2026-28416 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N yes
GHSA-45hq-cxwh-f6vc CVE-2026-55379 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4x4j-2g7c-83w6 CVE-2026-55798 medium CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L yes
GHSA-5x94-69rx-g8h2 CVE-2026-54060 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-5xmw-vc9v-4wf2 CVE-2026-42309 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
GHSA-62p4-gmf7-7g93 CVE-2026-54058 high yes
GHSA-6r8x-57c9-28j4 CVE-2026-59199 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8v84-f9pq-wr9x CVE-2026-54059 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-9hw9-ch79-4vh6 CVE-2026-59205 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-cfh3-3jmp-rvhc CVE-2026-25990 high yes

Showing 50 of 89 vulnerabilities.

Background: What a vulnerability scan can and cannot prove →

Dependencies 112 packages
Packages resolved 112
Stale 7
No linked repository 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 15 exposed · ~1,509 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_db_health ~86

Database health overview. Args: health_type: Принимается для совместимости со старой схемой инструмента, но пока не используется — отчёт всегда включает все проверки (default: "all"). database_url: Database URL (optional, uses DATABASE_URL from .env if omitted).

NameTypeReqDescription
database_url–––
health_typestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

analyze_index_performance ~67

Analyze index usage and find unused/duplicate indexes. Args: schema_name: Schema to analyze (default: "public"). database_url: Database URL (optional, uses DATABASE_URL from .env if omitted).

NameTypeReqDescription
database_url–––
schema_namestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

execute_sql ~54

Execute a SQL query. Args: sql: SQL statement to execute. database_url: Database URL (optional, uses DATABASE_URL from .env if omitted).

NameTypeReqDescription
database_url–––
sqlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

explain_query ~118

Get query execution plan. Args: sql: SQL statement to explain. analyze: If true, actually executes the query for real timing data (default: value of EXPLAIN_ANALYZE in .env, normally false). WARNING: true really runs the query, including any INSERT/UPDATE/DELETE it contains — use with care. database_url: Database URL (optional, uses DATABASE_URL from .env if omitted).

NameTypeReqDescription
analyze–––
database_url–––
sqlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

format_sql_query ~37

Format/beautify a SQL query for readability. Args: sql: Raw SQL text to format.

NameTypeReqDescription
sqlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_active_queries ~43

List currently running queries and their duration. Args: database_url: Database URL (optional, uses DATABASE_URL from .env if omitted).

NameTypeReqDescription
database_url–––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_database_info ~49

Get general database information: version, size, extensions, server settings. Args: database_url: Database URL (optional, uses DATABASE_URL from .env if omitted).

NameTypeReqDescription
database_url–––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_database_locks ~44

Show current database locks and blocking queries. Args: database_url: Database URL (optional, uses DATABASE_URL from .env if omitted).

NameTypeReqDescription
database_url–––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_object_details ~77

Get columns of a table or view. Args: schema_name: Schema containing the object. object_name: Table or view name. database_url: Database URL (optional, uses DATABASE_URL from .env if omitted).

NameTypeReqDescription
database_url–––
object_namestringyes–
schema_namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_table_sizes ~95

Show table sizes including indexes and total. Args: schema_name: Schema to analyze (default: "public"). sort_by: Sort order — "total", "table", or "indexes" (default: "total"). database_url: Database URL (optional, uses DATABASE_URL from .env if omitted).

NameTypeReqDescription
database_url–––
schema_namestring––
sort_bystring––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_top_queries ~126

Top queries by resource usage (requires pg_stat_statements extension). Args: limit: How many queries to return (optional, defaults to TOP_QUERIES_DEFAULT_LIMIT from .env). sort_by: Принимается для совместимости со старой схемой инструмента, но пока не используется — сортировка всегда по total_exec_time (default: "resources"). database_url: Database URL (optional, uses DATABASE_URL from .env if omitted).

NameTypeReqDescription
database_url–––
limit–––
sort_bystring––
NameTypeReqDescription
resultstringyes–

No examples provided.

list_objects ~93

List tables/views/sequences in a schema. Args: schema_name: Name of the schema to list objects from. object_type: One of "table", "view", "sequence" (default: "table"). database_url: Database URL (optional, uses DATABASE_URL from .env if omitted).

NameTypeReqDescription
database_url–––
object_typestring––
schema_namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

list_schemas ~42

List all schemas in the database. Args: database_url: Database URL (optional, uses DATABASE_URL from .env if omitted).

NameTypeReqDescription
database_url–––
NameTypeReqDescription
resultstringyes–

No examples provided.

list_tools ~75

List all available MCP tools of this server with their descriptions. Returns a JSON array with one entry per tool: name, description and inputSchema (parameters). Does NOT require a database connection — useful for discovering capabilities at runtime. Returns: JSON string: [{"name": ..., "description": ..., "parameters": ...}, ...]

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

manage_encryption_key ~503

Manage the Data Encryption Certificate (Fernet key) for stored secrets. Args: action: One of: - "status" (default) — list all certs with metadata, no changes. - "generate" — create a new cert, set as active. ttl_days applies. - "rotate" — create a new cert (version+1), set as active, previous one becomes ROTATING (decrypt still works in grace period). - "rekey" — re-encrypt connections.json and llm_connections.json with the new active cert (run after rotation). - "revoke" — mark cert by `kid` as REVOKED (compromised). Decrypt NO longer works for it. - "validate" — same as status, but also tries to decrypt a known secret (currently no-op placeholder, returns status). ttl_days: Certificate lifetime for generate/rotate (default 90). subject: Subject CN for new certs (default "postgres-mcp secrets"). use_passphrase: If true, new cert will be passphrase-protected (raw key encrypted with PBKDF2(passphrase)). Passphrase is read from env CERT_PASSPHRASE. kid: For action="revoke" — which certificate to revoke. reason: Free-text reason recorded in audit log and cert notes. Returns: JSON with details of the operation. For "status" — list of certs. For generate/rotate — new cert metadata. For revoke — boolean. For rekey — statistics {scanned, rekeyed, skipped, errors}. Examples: # See current state action="status" # Create a new cert (auto-active) action="generate" ttl_days=90 # Rotate (new active, old → ROTATING for grace period) action="rotate" # Re-encrypt connections files with new cert action="rekey" # Revoke a compromised cert action="revoke" kid="dec-abc123..." reason="leaked on GitHub"

NameTypeReqDescription
actionstring––
kidstring––
reasonstring––
subjectstring––
ttl_daysinteger––
use_passphraseboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

Common questions

What is the io.github.sparta2025/postgres-mcp server?

io.github.sparta2025/postgres-mcp is listed in the public MCP registry as io.github.sparta2025/postgres-mcp. PostgreSQL MCP server with 15 tools (SQL, EXPLAIN, health, indexes) plus a Gradio UI with LLM chat. This page covers its PyPI package (postgres-mcp-pro).

Is the io.github.sparta2025/postgres-mcp server safe to use?

io.github.sparta2025/postgres-mcp scores 59 out of 100 on VerifyMCP. We recorded 89 known advisories against it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.sparta2025/postgres-mcp server expose?

io.github.sparta2025/postgres-mcp exposes 15 tools: list_schemas, list_objects, get_object_details, execute_sql, explain_query, and 10 more. Their descriptions and schemas cost roughly 1,509 tokens of context every time the server is loaded.

Is the io.github.sparta2025/postgres-mcp server still maintained?

io.github.sparta2025/postgres-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.