# io.github.sparta2025/postgres-mcp (pypi · postgres-mcp-pro) PostgreSQL MCP server with 15 tools (SQL, EXPLAIN, health, indexes) plus a Gradio UI with LLM chat. - Trust score: 59/100 (low) - Change this week: +4 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-20 ## Components - pypi · `postgres-mcp-pro`: 59/100 (this document), [markdown](https://verifymcp.io/servers/sparta2025-postgres-mcp/postgres-mcp-pro.md), [page](https://verifymcp.io/servers/sparta2025-postgres-mcp/postgres-mcp-pro) ## Channel facts - Registry: `pypi` - Package: `postgres-mcp-pro` - Version: `0.4.2` - Transport: `stdio` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-09-20. - **Supply Chain Security**: 32/100 - Malware scan not yet available for this package. - CVE check failed: a known high-severity CVE affects gradio 5.50.0, a direct dependency. A fixed version is available. - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. - 9 of 112 dependencies flagged as unhealthy. - **Provenance & Transparency**: 32/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - License check failed: no license is declared. - Actively maintained (last published 29 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 80/100 - AI-judged instruction clarity (excellent). - Tool/resource definitions use about 1509 tokens (~100/item across 15 items; 15 tools + 0 resources), lean. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 100/100 - No destabilizing schema changes in the last 30 days. - **Tool Coverage**: 71/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 0% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Tool Safety**: 75/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - 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. - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## 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. ### Claude ```bash claude mcp add sparta2025-postgres-mcp -- uvx postgres-mcp-pro ``` ### Cursor ```json { "mcpServers": { "sparta2025-postgres-mcp": { "command": "uvx", "args": [ "postgres-mcp-pro" ] } } } ``` ### VS Code ```json { "servers": { "sparta2025-postgres-mcp": { "command": "uvx", "args": [ "postgres-mcp-pro" ] } } } ``` ### Codex ```bash 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 } } } ``` ### OpenClaw ```bash openclaw mcp add sparta2025-postgres-mcp --command uvx --arg postgres-mcp-pro ``` ### Hermes ```yaml mcp_servers: sparta2025-postgres-mcp: command: "uvx" args: ["postgres-mcp-pro"] ``` ### Netclaw ```json { "McpServers": { "sparta2025-postgres-mcp": { "Transport": "stdio", "Command": "uvx", "Arguments": [ "postgres-mcp-pro" ] } } } ``` ### Vellum ```bash assistant mcp add sparta2025-postgres-mcp -t stdio -c uvx -a postgres-mcp-pro ``` ### Other ```json { "mcpServers": { "sparta2025-postgres-mcp": { "command": "uvx", "args": [ "postgres-mcp-pro" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-09-20 (score 59, +1) - [security regression] CVE-2026-54274 affects this package: high - [security regression] CVE-2026-50269 affects this package: high - [security regression] CVE-2026-25990 affects this package: high - [security regression] CVE-2026-59200 affects this package: high - [security regression] CVE-2026-54273 affects this package: high - [security regression] CVE-2026-55798 affects this package: high - [security regression] CVE-2026-55379 affects this package: high - [security regression] CVE-2026-48817 affects this package: high - [security regression] CVE-2026-28416 affects this package: high - [security regression] CVE-2026-54276 affects this package: high - [security regression] CVE-2026-59199 affects this package: high - [security regression] CVE-2026-54059 affects this package: high - [security regression] CVE-2026-54283 affects this package: high - [security regression] CVE-2026-54278 affects this package: high - [security regression] CVE-2026-49119 affects this package: high - [security regression] CVE-2026-27167 affects this package: high - [security regression] CVE-2026-69243 affects this package: high - [security regression] CVE-2026-54058 affects this package: high - [security regression] CVE-2026-54282 affects this package: high - [security regression] CVE-2026-59205 affects this package: high - [security regression] CVE-2026-59198 affects this package: high - [security regression] CVE-2026-47265 affects this package: high - [security regression] CVE-2026-48710 affects this package: high - [security regression] CVE-2026-69244 affects this package: high - [security regression] CVE-2026-54279 affects this package: high - [security regression] CVE-2026-42311 affects this package: high - [security regression] CVE-2026-54277 affects this package: high - [security regression] CVE-2026-25645 affects this package: high - [security regression] CVE-2026-59204 affects this package: high - [security regression] CVE-2026-42310 affects this package: high - [security regression] CVE-2026-54275 affects this package: high - [security regression] CVE-2026-10783 affects this package: high - [security regression] CVE-2026-42309 affects this package: high - [security regression] CVE-2026-54280 affects this package: high - [security regression] CVE-2026-28415 affects this package: high - [security regression] CVE-2026-48545 affects this package: high - [security regression] CVE-2026-54060 affects this package: high - [security regression] CVE-2026-48818 affects this package: high - [security regression] CVE-2026-28414 affects this package: high - [security regression] CVE-2026-59197 affects this package: high - [security regression] CVE-2026-34993 affects this package: high - [security regression] CVE-2026-40192 affects this package: high - [security regression] CVE-2026-42308 affects this package: high - [security regression] CVE-2026-55380 affects this package: high - [security regression] CVE-2026-59881 affects this package: high - [security] Stability: 0.97 → pass ### 2026-09-19 (score 58, 0) - [security regression] CVE-2026-49119 affects this package: high - [security regression] CVE-2026-40192 affects this package: high - [security regression] CVE-2026-34993 affects this package: high - [security regression] CVE-2026-59197 affects this package: high - [security regression] CVE-2026-28414 affects this package: high - [security regression] CVE-2026-48818 affects this package: high - [security regression] CVE-2026-54060 affects this package: high - [security regression] CVE-2026-48545 affects this package: high - [security regression] CVE-2026-28415 affects this package: high - [security regression] CVE-2026-54280 affects this package: high - [security regression] CVE-2026-42309 affects this package: high - [security regression] CVE-2026-10783 affects this package: high - [security regression] CVE-2026-54275 affects this package: high - [security regression] CVE-2026-42310 affects this package: high - [security regression] CVE-2026-59204 affects this package: high - [security regression] CVE-2026-25645 affects this package: high - [security regression] CVE-2026-54277 affects this package: high - [security regression] CVE-2026-42311 affects this package: high - [security regression] CVE-2026-54279 affects this package: high - [security regression] CVE-2026-69244 affects this package: high - [security regression] CVE-2026-48710 affects this package: high - [security regression] CVE-2026-47265 affects this package: high - [security regression] CVE-2026-59198 affects this package: high - [security regression] CVE-2026-59205 affects this package: high - [security regression] CVE-2026-54282 affects this package: high - [security regression] CVE-2026-54058 affects this package: high - [security regression] CVE-2026-69243 affects this package: high - [security regression] CVE-2026-27167 affects this package: high - [security regression] CVE-2026-54278 affects this package: high - [security regression] CVE-2026-54283 affects this package: high - [security regression] CVE-2026-54059 affects this package: high - [security regression] CVE-2026-59199 affects this package: high - [security regression] CVE-2026-54276 affects this package: high - [security regression] CVE-2026-28416 affects this package: high - [security regression] CVE-2026-48817 affects this package: high - [security regression] CVE-2026-55379 affects this package: high - [security regression] CVE-2026-55798 affects this package: high - [security regression] CVE-2026-54273 affects this package: high - [security regression] CVE-2026-59200 affects this package: high - [security regression] CVE-2026-25990 affects this package: high - [security regression] CVE-2026-50269 affects this package: high - [security regression] CVE-2026-42308 affects this package: high - [security regression] CVE-2026-55380 affects this package: high - [security regression] CVE-2026-59881 affects this package: high - [security regression] CVE-2026-54274 affects this package: high ### 2026-09-18 (score 58, +1) - [security regression] CVE-2026-59881 affects this package: high - [security regression] CVE-2026-55380 affects this package: high - [security regression] CVE-2026-40192 affects this package: high - [security regression] CVE-2026-34993 affects this package: high - [security regression] CVE-2026-59197 affects this package: high - [security regression] CVE-2026-28414 affects this package: high - [security regression] CVE-2026-48818 affects this package: high - [security regression] CVE-2026-54060 affects this package: high - [security regression] CVE-2026-48545 affects this package: high - [security regression] CVE-2026-28415 affects this package: high - [security regression] CVE-2026-54280 affects this package: high - [security regression] CVE-2026-42309 affects this package: high - [security regression] CVE-2026-10783 affects this package: high - [security regression] CVE-2026-54275 affects this package: high - [security regression] CVE-2026-42310 affects this package: high - [security regression] CVE-2026-59204 affects this package: high - [security regression] CVE-2026-25645 affects this package: high - [security regression] CVE-2026-54277 affects this package: high - [security regression] CVE-2026-42311 affects this package: high - [security regression] CVE-2026-54279 affects this package: high - [security regression] CVE-2026-69244 affects this package: high - [security regression] CVE-2026-48710 affects this package: high - [security regression] CVE-2026-47265 affects this package: high - [security regression] CVE-2026-59198 affects this package: high - [security regression] CVE-2026-59205 affects this package: high - [security regression] CVE-2026-54282 affects this package: high - [security regression] CVE-2026-54058 affects this package: high - [security regression] CVE-2026-69243 affects this package: high - [security regression] CVE-2026-27167 affects this package: high - [security regression] CVE-2026-49119 affects this package: high - [security regression] CVE-2026-54278 affects this package: high - [security regression] CVE-2026-54283 affects this package: high - [security regression] CVE-2026-54059 affects this package: high - [security regression] CVE-2026-59199 affects this package: high - [security regression] CVE-2026-54276 affects this package: high - [security regression] CVE-2026-28416 affects this package: high - [security regression] CVE-2026-48817 affects this package: high - [security regression] CVE-2026-55379 affects this package: high - [security regression] CVE-2026-55798 affects this package: high - [security regression] CVE-2026-54273 affects this package: high - [security regression] CVE-2026-59200 affects this package: high - [security regression] CVE-2026-25990 affects this package: high - [security regression] CVE-2026-50269 affects this package: high - [security regression] CVE-2026-42308 affects this package: high - [security regression] CVE-2026-54274 affects this package: high ### 2026-09-17 (score 57, 0) - [security regression] CVE-2026-54276 affects this package: high - [security regression] CVE-2026-40192 affects this package: high - [security regression] CVE-2026-34993 affects this package: high - [security regression] CVE-2026-59197 affects this package: high - [security regression] CVE-2026-28414 affects this package: high - [security regression] CVE-2026-48818 affects this package: high - [security regression] CVE-2026-54060 affects this package: high - [security regression] CVE-2026-48545 affects this package: high - [security regression] CVE-2026-28415 affects this package: high - [security regression] CVE-2026-54280 affects this package: high - [security regression] CVE-2026-42309 affects this package: high - [security regression] CVE-2026-10783 affects this package: high - [security regression] CVE-2026-54275 affects this package: high - [security regression] CVE-2026-42310 affects this package: high - [security regression] CVE-2026-59204 affects this package: high - [security regression] CVE-2026-25645 affects this package: high - [security regression] CVE-2026-54277 affects this package: high - [security regression] CVE-2026-42311 affects this package: high - [security regression] CVE-2026-54279 affects this package: high - [security regression] CVE-2026-69244 affects this package: high - [security regression] CVE-2026-48710 affects this package: high - [security regression] CVE-2026-47265 affects this package: high - [security regression] CVE-2026-59198 affects this package: high - [security regression] CVE-2026-59205 affects this package: high - [security regression] CVE-2026-54282 affects this package: high - [security regression] CVE-2026-54058 affects this package: high - [security regression] CVE-2026-69243 affects this package: high - [security regression] CVE-2026-27167 affects this package: high - [security regression] CVE-2026-49119 affects this package: high - [security regression] CVE-2026-54278 affects this package: high - [security regression] CVE-2026-54283 affects this package: high - [security regression] CVE-2026-54059 affects this package: high - [security regression] CVE-2026-59199 affects this package: high - [security regression] CVE-2026-28416 affects this package: high - [security regression] CVE-2026-48817 affects this package: high - [security regression] CVE-2026-55379 affects this package: high - [security regression] CVE-2026-55798 affects this package: high - [security regression] CVE-2026-54273 affects this package: high - [security regression] CVE-2026-59200 affects this package: high - [security regression] CVE-2026-25990 affects this package: high - [security regression] CVE-2026-50269 affects this package: high - [security regression] CVE-2026-42308 affects this package: high - [security regression] CVE-2026-55380 affects this package: high - [security regression] CVE-2026-59881 affects this package: high - [security regression] CVE-2026-54274 affects this package: high ### 2026-09-16 (score 57, +1) We did not load change detail this far back for this component, so this day may have recorded more than is shown. - [security regression] CVE-2026-59881 affects this package: high - [security regression] CVE-2026-54274 affects this package: high - [security regression] CVE-2026-55380 affects this package: high - [security regression] CVE-2026-42308 affects this package: high - [security regression] CVE-2026-50269 affects this package: high - [security regression] CVE-2026-25990 affects this package: high - [security regression] CVE-2026-59200 affects this package: high - [security regression] CVE-2026-54273 affects this package: high - [security regression] CVE-2026-55798 affects this package: high - [security regression] CVE-2026-55379 affects this package: high - [security regression] CVE-2026-48817 affects this package: high - [security regression] CVE-2026-28416 affects this package: high - [security regression] CVE-2026-54276 affects this package: high - [security regression] CVE-2026-59199 affects this package: high - [security regression] CVE-2026-54059 affects this package: high - [security regression] CVE-2026-54283 affects this package: high - [security regression] CVE-2026-54278 affects this package: high ### 2026-09-14 (score 56, +1) We did not load change detail this far back for this component, so this day may have recorded more than is shown. ### 2026-09-12 (score 55, +1) We did not load change detail this far back for this component, so this day may have recorded more than is shown. ### 2026-09-10 (score 54, +1) We did not load change detail this far back for this component, so this day may have recorded more than is shown. ## MCP tools (15) ### `list_schemas` (~42 tokens) List all schemas in the database. Args: database_url: Database URL (optional, uses DATABASE_URL from .env if omitted). Input parameters: - `database_url` Output parameters: - `result` (string) ### `list_objects` (~93 tokens) 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). Input parameters: - `database_url` - `object_type` (string) - `schema_name` (string, required) Output parameters: - `result` (string) ### `get_object_details` (~77 tokens) 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). Input parameters: - `database_url` - `object_name` (string, required) - `schema_name` (string, required) Output parameters: - `result` (string) ### `execute_sql` (~54 tokens) Execute a SQL query. Args: sql: SQL statement to execute. database_url: Database URL (optional, uses DATABASE_URL from .env if omitted). Input parameters: - `database_url` - `sql` (string, required) Output parameters: - `result` (string) ### `explain_query` (~118 tokens) 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). Input parameters: - `analyze` - `database_url` - `sql` (string, required) Output parameters: - `result` (string) ### `analyze_db_health` (~86 tokens) Database health overview. Args: health_type: Принимается для совместимости со старой схемой инструмента, но пока не используется — отчёт всегда включает все проверки (default: "all"). database_url: Database URL (optional, uses DATABASE_URL from .env if omitted). Input parameters: - `database_url` - `health_type` (string) Output parameters: - `result` (string) ### `get_top_queries` (~126 tokens) 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). Input parameters: - `database_url` - `limit` - `sort_by` (string) Output parameters: - `result` (string) ### `analyze_index_performance` (~67 tokens) 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). Input parameters: - `database_url` - `schema_name` (string) Output parameters: - `result` (string) ### `get_active_queries` (~43 tokens) List currently running queries and their duration. Args: database_url: Database URL (optional, uses DATABASE_URL from .env if omitted). Input parameters: - `database_url` Output parameters: - `result` (string) ### `get_table_sizes` (~95 tokens) 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). Input parameters: - `database_url` - `schema_name` (string) - `sort_by` (string) Output parameters: - `result` (string) ### `get_database_locks` (~44 tokens) Show current database locks and blocking queries. Args: database_url: Database URL (optional, uses DATABASE_URL from .env if omitted). Input parameters: - `database_url` Output parameters: - `result` (string) ### `format_sql_query` (~37 tokens) Format/beautify a SQL query for readability. Args: sql: Raw SQL text to format. Input parameters: - `sql` (string, required) Output parameters: - `result` (string) ### `get_database_info` (~49 tokens) Get general database information: version, size, extensions, server settings. Args: database_url: Database URL (optional, uses DATABASE_URL from .env if omitted). Input parameters: - `database_url` Output parameters: - `result` (string) ### `manage_encryption_key` (~503 tokens) 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" Input parameters: - `action` (string) - `kid` (string) - `reason` (string) - `subject` (string) - `ttl_days` (integer) - `use_passphrase` (boolean) Output parameters: - `result` (string) ### `list_tools` (~75 tokens) 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": ...}, ...] Output parameters: - `result` (string) ## Diagnostics Captured diagnostic sections: Provenance, Install scripts, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/sparta2025-postgres-mcp/postgres-mcp-pro#diagnostics ## Score history - 2026-09-20: 59 - 2026-09-19: 58 - 2026-09-18: 58 - 2026-09-17: 57 - 2026-09-16: 57 - 2026-09-15: 56 - 2026-09-14: 56 - 2026-09-13: 55 - 2026-09-12: 55 - 2026-09-11: 54 - 2026-09-10: 54 - 2026-09-09: 53 - 2026-09-08: 68 - 2026-09-07: 53 - 2026-09-06: 67 - 2026-09-05: 67 - 2026-09-04: 66 - 2026-09-03: 51 - 2026-09-02: 50 - 2026-09-01: 50 - 2026-08-31: 64 - 2026-08-30: 64 - 2026-08-29: 63 - 2026-08-28: 63 - 2026-08-27: 60 - 2026-08-26: 60 - 2026-08-25: 59 - 2026-08-24: 59 - 2026-08-23: 59 - 2026-08-22: 59 ## 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. ## Links - PyPI project: https://pypi.org/project/postgres-mcp-pro/ - Socket report: https://socket.dev/pypi/package/postgres-mcp-pro - Repository: https://github.com/sparta2025/postgres-mcp - Changelog RSS feed: https://verifymcp.io/servers/sparta2025-postgres-mcp/postgres-mcp-pro.xml - Changelog JSON feed: https://verifymcp.io/servers/sparta2025-postgres-mcp/postgres-mcp-pro.json - HTML version of this page: https://verifymcp.io/servers/sparta2025-postgres-mcp/postgres-mcp-pro