postgresql-ssh-mcp (Zlash65/postgresql-ssh-mcp) is an MCP server listed on the M8ven Trust Index. It scores 70 out of 100, grade C. It declares 12 tools. No publisher has claimed this listing.

C
Caution
70/100
24 days ago

postgresql-ssh-mcp

PostgreSQL MCP server with SSH tunneling for Claude Desktop and ChatGPT

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Zlash65

Source: github_topic · also listed on Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Known vulnerabilities in dependencies: 1 critical, 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 2 credentials: SSH_PASSWORD, SSH_STRICT_HOST_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical2 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@2.1.9GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

high@modelcontextprotocol/sdk@1.25.1GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.25.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAUTH0_AUDIENCEYes Auth0 API identifier / audience
configAUTH0_DOMAINYes Auth0 tenant domain (e.g., tenant.us.auth0.com)
configDATABASE_PORTNo 5432 Database port
configDATABASE_SSLAuto true or false. Auto-enabled for non-localhost.
configDATABASE_SSL_CAPath to CA certificate bundle
configDATABASE_SSL_REJECT_UNAUTHORIZEDtrue Set false to allow self-signed certificates
configDATABASE_URI"": "postgresql://user:password@localhost:5432/mydb"
configMAX_CONCURRENT_QUERIES10 Maximum concurrent queries
configMAX_ROWSexecute_query Execute SQL with parameterized queries. Results capped by .
configMCP_ALLOWED_HOSTSComma-separated allowed Host headers
configMCP_ALLOWED_ORIGINSComma-separated allowed CORS origins ( for any)
configMCP_AUTH_MODEnone Authentication mode: none or oauth
configMCP_HOST0.0.0.0 HTTP server bind address
configMCP_RESOURCE_DOCUMENTATIONNo URL to API documentation (RFC 9728)
configMCP_SERVER_POOL_SIZE4 Server instances for stateless mode
configMCP_SESSION_CLEANUP_INTERVAL_MS300000 Session cleanup interval
configMCP_SESSION_TTL_MINUTES30 Session TTL for stateful mode
configMCP_STATELESStrue Stateless mode (each request re-initializes)
configPOOL_DRAIN_TIMEOUT_MS5000 Timeout for draining pool during reconnect
configQUERY_TIMEOUT30000 Query timeout in milliseconds
configREAD_ONLYtrue Block data modifications. Set false to allow writes.
configSSH_KEEPALIVE_INTERVALNo 10000 Keepalive interval in milliseconds
configSSH_KNOWN_HOSTS_PATHNo ~/.ssh/known_hosts Custom known_hosts file
configSSH_MAX_RECONNECT_ATTEMPTSNo 5 Max reconnect attempts (-1 for unlimited)
🔐 secretSSH_PASSWORDYes — SSH password (alternative to key)
configSSH_PORTNo 22 SSH server port
configSSH_PRIVATE_KEY_PASSPHRASENo — Passphrase for encrypted keys
configSSH_PRIVATE_KEY_PATHYes — Path to private key file
🔐 secretSSH_STRICT_HOST_KEYNo true Verify host key against known_hosts
configSSH_TRUST_ON_FIRST_USENo true Auto-add unknown hosts (when strict is enabled)
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

12/12 tools missing one or more hints — get_connection_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_active_connections (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_long_running_queries (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +9 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

9/12 tool handlers declare input schemas (75%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Secrets not logged

2 secret values sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 2 high severity in production deps — @modelcontextprotocol/sdk@1.25.1 (high), @modelcontextprotocol/sdk@1.25.1 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/zlash65/postgresql-ssh-mcp?variant=verified)](https://m8ven.ai/mcp/zlash65/postgresql-ssh-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 2a350d45d464820df349c9b21cb178dcb74cc230
code hash: 2fa630af4d97e1c98cdaaa1dc08f4db783624f9d73894d35720df8c7ee32aea8
verified: 8/17/2026, 3:47:05 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client