pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for PostgreSQL MCP Server by neverinfamous

Pod holds 17 of 18 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to PostgreSQL MCP Server by neverinfamous.

Most discussed

[BUG] SSE connection is not working

Description

I'm trying to use it as a remote MCP SSE server, but it's never initialized.

Steps to Reproduce

  1. Run MCP server:
docker run --rm -i --network host -e MCP_TRANSPORT -e POSTGRES_HOST -e POSTGRES_PORT -e POSTGRES_USER -e POSTGRES_PASSWORD -e POSTGRES_DATABASE writenotenow/postgres-mcp:latest dist/cli.js --tool-filter pg_read_only,-codemode --transport http --port 3000
  1. Connect using a simple client:
import asyncio
from mcp import ClientSession
from mcp.client.ss

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/65) · 2026-03-03 · closed · external user · 7 comments

### Feature Request: Align MCP instructions with --tool-filter (reduce ~9K wasted tokens)

# Feature Request: Align MCP instructions with --tool-filter

## Problem

When using `--tool-filter` to limit exposed tools, the MCP server correctly filters the tools available to the client. However, the **server instructions** sent via the MCP protocol still include documentation for ALL tool groups, regardless of the filter.

This means the AI client receives ~14,600 tokens of instructions in its system prompt, but ~8,800 tokens (61%) are for tool groups that aren't even exposed.

##

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/77) · 2026-03-15 · closed · external user · 2 comments

### [FEATURE] allow adjustment of mcp server host binding

## Feature

Add an option for changing the server's host/bind parameter away from localhost.

## Use Case

I want to be able to run this inside a container - right now that doesn't work b/c the mcp server is only listening on localhost, and ignores messages coming in through exposed ports. I can get around by running a proxy inside the container alongside postgresql-mcp but that seems silly to be necessary

## Proposed Solution

new cli argument for mcp server configuration

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/30) · 2026-02-03 · closed · external user · 2 comments

### 🚨 Security vulnerabilities detected in Docker images

## Security Alert

  Trivy has detected security vulnerabilities in our Docker images.

  **Action Required:**
  1. Review the security scan results in the Actions tab
  2. Update base images and dependencies
  3. Test the fixes
  4. Deploy updated images

  **Scan Details:**
  - Workflow run: https://github.com/neverinfamous/postgres-mcp/actions/runs/26350585462
  - Triggered by: Weekly security scan
  - Scan Date: 0 2 * * 0

  **Next Steps:**
  - [ ] Review vulnerability details
  - [ ] Update

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/158) · 2026-05-24 · open · external user · 0 comments

### 🚨 Security vulnerabilities detected in Docker images

## Security Alert

  Trivy has detected security vulnerabilities in our Docker images.

  **Action Required:**
  1. Review the security scan results in the Actions tab
  2. Update base images and dependencies
  3. Test the fixes
  4. Deploy updated images

  **Scan Details:**
  - Workflow run: https://github.com/neverinfamous/postgres-mcp/actions/runs/25661644363
  - Triggered by: Weekly security scan
  - Scan Date: Manual trigger

  **Next Steps:**
  - [ ] Review vulnerability details
  - [ ] U

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/150) · 2026-05-11 · closed · external user · 0 comments

### 🚨 Security vulnerabilities detected in Docker images

## Security Alert

  Trivy has detected security vulnerabilities in our Docker images.

  **Action Required:**
  1. Review the security scan results in the Actions tab
  2. Update base images and dependencies
  3. Test the fixes
  4. Deploy updated images

  **Scan Details:**
  - Workflow run: https://github.com/neverinfamous/postgres-mcp/actions/runs/25661635103
  - Triggered by: Weekly security scan
  - Scan Date: Manual trigger

  **Next Steps:**
  - [ ] Review vulnerability details
  - [ ] U

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/149) · 2026-05-11 · closed · external user · 0 comments

### 🚨 Security vulnerabilities detected in Docker images

## Security Alert

  Trivy has detected security vulnerabilities in our Docker images.

  **Action Required:**
  1. Review the security scan results in the Actions tab
  2. Update base images and dependencies
  3. Test the fixes
  4. Deploy updated images

  **Scan Details:**
  - Workflow run: https://github.com/neverinfamous/postgres-mcp/actions/runs/25618512343
  - Triggered by: Weekly security scan
  - Scan Date: 0 2 * * 0

  **Next Steps:**
  - [ ] Review vulnerability details
  - [ ] Update

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/141) · 2026-05-10 · closed · external user · 0 comments

### 🚨 Security vulnerabilities detected in Docker images

## Security Alert

  Trivy has detected security vulnerabilities in our Docker images.

  **Action Required:**
  1. Review the security scan results in the Actions tab
  2. Update base images and dependencies
  3. Test the fixes
  4. Deploy updated images

  **Scan Details:**
  - Workflow run: https://github.com/neverinfamous/postgres-mcp/actions/runs/24297514445
  - Triggered by: Weekly security scan
  - Scan Date: 0 2 * * 0

  **Next Steps:**
  - [ ] Review vulnerability details
  - [ ] Update

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/117) · 2026-04-12 · closed · external user · 0 comments

## Most recent

### 🚨 Security vulnerabilities detected in Docker images

## Security Alert

  Trivy has detected security vulnerabilities in our Docker images.

  **Action Required:**
  1. Review the security scan results in the Actions tab
  2. Update base images and dependencies
  3. Test the fixes
  4. Deploy updated images

  **Scan Details:**
  - Workflow run: https://github.com/neverinfamous/postgres-mcp/actions/runs/24162372215
  - Triggered by: Weekly security scan
  - Scan Date: Manual trigger

  **Next Steps:**
  - [ ] Review vulnerability details
  - [ ] U

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/115) · 2026-04-08 · closed · external user · 0 comments

### 🚨 Security vulnerabilities detected in Docker images

## Security Alert

  Trivy has detected security vulnerabilities in our Docker images.

  **Action Required:**
  1. Review the security scan results in the Actions tab
  2. Update base images and dependencies
  3. Test the fixes
  4. Deploy updated images

  **Scan Details:**
  - Workflow run: https://github.com/neverinfamous/postgres-mcp/actions/runs/22597456973
  - Triggered by: Weekly security scan
  - Scan Date: Manual trigger

  **Next Steps:**
  - [ ] Review vulnerability details
  - [ ] U

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/62) · 2026-03-02 · closed · external user · 0 comments

### 🚨 Security vulnerabilities detected in Docker images

## Security Alert

  Trivy has detected security vulnerabilities in our Docker images.

  **Action Required:**
  1. Review the security scan results in the Actions tab
  2. Update base images and dependencies
  3. Test the fixes
  4. Deploy updated images

  **Scan Details:**
  - Workflow run: https://github.com/neverinfamous/postgres-mcp/actions/runs/22597363005
  - Triggered by: Weekly security scan
  - Scan Date: Manual trigger

  **Next Steps:**
  - [ ] Review vulnerability details
  - [ ] U

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/61) · 2026-03-02 · closed · external user · 0 comments

### 🚨 Security vulnerabilities detected in Docker images

## Security Alert

  Trivy has detected security vulnerabilities in our Docker images.

  **Action Required:**
  1. Review the security scan results in the Actions tab
  2. Update base images and dependencies
  3. Test the fixes
  4. Deploy updated images

  **Scan Details:**
  - Workflow run: https://github.com/neverinfamous/postgres-mcp/actions/runs/22597291549
  - Triggered by: Weekly security scan
  - Scan Date: Manual trigger

  **Next Steps:**
  - [ ] Review vulnerability details
  - [ ] U

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/60) · 2026-03-02 · closed · external user · 0 comments

### 🚨 Security vulnerabilities detected in Docker images

## Security Alert

  Trivy has detected security vulnerabilities in our Docker images.

  **Action Required:**
  1. Review the security scan results in the Actions tab
  2. Update base images and dependencies
  3. Test the fixes
  4. Deploy updated images

  **Scan Details:**
  - Workflow run: https://github.com/neverinfamous/postgresql-mcp/actions/runs/22534763849
  - Triggered by: Weekly security scan
  - Scan Date: 0 2 * * 0

  **Next Steps:**
  - [ ] Review vulnerability details
  - [ ] Upda

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/58) · 2026-03-01 · closed · external user · 0 comments

### 🚨 Security vulnerabilities detected in Docker images

## Security Alert

  Trivy has detected security vulnerabilities in our Docker images.

  **Action Required:**
  1. Review the security scan results in the Actions tab
  2. Update base images and dependencies
  3. Test the fixes
  4. Deploy updated images

  **Scan Details:**
  - Workflow run: https://github.com/neverinfamous/postgresql-mcp/actions/runs/21873981749
  - Triggered by: Weekly security scan
  - Scan Date: Manual trigger

  **Next Steps:**
  - [ ] Review vulnerability details
  - [ ]

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/42) · 2026-02-10 · closed · external user · 0 comments

### 🚨 Security vulnerabilities detected in Docker images

## Security Alert

  Trivy has detected security vulnerabilities in our Docker images.

  **Action Required:**
  1. Review the security scan results in the Actions tab
  2. Update base images and dependencies
  3. Test the fixes
  4. Deploy updated images

  **Scan Details:**
  - Workflow run: https://github.com/neverinfamous/postgresql-mcp/actions/runs/21816364595
  - Triggered by: Weekly security scan
  - Scan Date: Manual trigger

  **Next Steps:**
  - [ ] Review vulnerability details
  - [ ]

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/40) · 2026-02-09 · closed · external user · 0 comments

### 🚨 Security vulnerabilities detected in Docker images

## Security Alert

  Trivy has detected security vulnerabilities in our Docker images.

  **Action Required:**
  1. Review the security scan results in the Actions tab
  2. Update base images and dependencies
  3. Test the fixes
  4. Deploy updated images

  **Scan Details:**
  - Workflow run: https://github.com/neverinfamous/postgresql-mcp/actions/runs/21816364137
  - Triggered by: Weekly security scan
  - Scan Date: Manual trigger

  **Next Steps:**
  - [ ] Review vulnerability details
  - [ ]

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/39) · 2026-02-09 · closed · external user · 0 comments

### 🚨 Security vulnerabilities detected in Docker images

## Security Alert

  Trivy has detected security vulnerabilities in our Docker images.

  **Action Required:**
  1. Review the security scan results in the Actions tab
  2. Update base images and dependencies
  3. Test the fixes
  4. Deploy updated images

  **Scan Details:**
  - Workflow run: https://github.com/neverinfamous/postgresql-mcp/actions/runs/21816288338
  - Triggered by: Weekly security scan
  - Scan Date: Manual trigger

  **Next Steps:**
  - [ ] Review vulnerability details
  - [ ]

[Read the thread](https://github.com/neverinfamous/postgres-mcp/issues/38) · 2026-02-09 · closed · external user · 0 comments

The remaining reports are on [the project's issue tracker](https://github.com/neverinfamous/postgres-mcp.git/issues).