English Français العربية

PostgreSQL CVE & Release Intelligence

Official registry Data and databases

PostgreSQL security for AI agents: CVEs, yanked releases, exploits, and upgrade paths

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

PYPI package pg-cve-mcp
Claude Code 
claude mcp add postgresql-cve-release-intelligence -e 'PG_CVE_MCP_TTL=<PG_CVE_MCP_TTL>' -e 'PG_CVE_MCP_DATA_URL=<PG_CVE_MCP_DATA_URL>' -- uvx pg-cve-mcp==1.0.4
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "postgresql-cve-release-intelligence": {
            "command": "uvx",
            "args": [
                "pg-cve-mcp==1.0.4"
            ],
            "env": {
                "PG_CVE_MCP_TTL": "<PG_CVE_MCP_TTL>",
                "PG_CVE_MCP_DATA_URL": "<PG_CVE_MCP_DATA_URL>"
            }
        }
    }
}

Environment variables

  • PG_CVE_MCP_TTL Cache TTL in seconds for CVE data refresh (default: 86400)
  • PG_CVE_MCP_DATA_URL URL of the PostgreSQL CVE JSON data (default: PG_CVE GitHub Pages)

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. pg-cve-mcp — PostgreSQL CVE & Release Intelligence for AI Agents
  2. Why pg-cve-mcp?
  3. Quick Start
  4. MCP Tools
  5. Transports
  6. Configuration
  7. Development
  8. Data Source
  9. Example Prompts
  10. License

pg-cve-mcp — PostgreSQL CVE & Release Intelligence for AI Agents

Give your AI assistant direct access to PostgreSQL security intelligence: CVEs, yanked releases, known exploits, and upgrade paths for any version — queried, not browsed.

Why pg-cve-mcp?

Browsing a CVE dashboard is a human habit. Agents need answers, not pages.

pg-cve-mcp turns the curated dataset of the **PG_CVE** project — the same one powering the PostgreSQL CVE Dashboard — into MCP tools that any AI assistant (opencode, Claude Desktop, etc.) can call directly. What was a static page becomes a first-class, programmatic part of your AI workflow.

Unlike raw NVD feeds, the PG_CVE dataset is manually curated to carry the same judgment a careful DBA would apply:

  • Yanked releases flagged with the real reason (e.g. "Data corruption using CONCURRENTLY")
  • Known exploits confirmed to exist in the wild
  • EOL branches marked, with a synthetic CVE-EOL-WARNING (CVSS 10.0) prepended to unsupported reports
  • Verified CVEs — no false positives from automated scraping
What your agent can now do
Prompt to your agentTool usedResult
"Is PostgreSQL 15.8 safe?"get_cves("15.8")EOL/yanked flags, release date, full CVE list sorted by CVSS
"Compare 16.3 vs 16.4"compare_versions("16.3", "16.4")fixed / new / still-present CVEs with release dates
"Should I upgrade from 14.10?"get_upgrade_path("14.10")recommended target + the CVEs it fixes + release dates
"Any known exploits right now?"get_exploits()all exploitable CVEs, sorted by CVSS, with release dates
"What does this database track?"get_summary()stats, EOL and yanked-release overview
Agent-first design

Every tool returns structured JSON, sorted by CVSS (highest first). Tools flag yanked and EOL state explicitly on the version metadata, and include release dates for every version. get_upgrade_path distinguishes a safe minor upgrade from a forced major one when a branch is at or near end-of-life — so the agent can give advice, not just data.

See real tool outputs in the live demo.

Quick Start

pip install pg-cve-mcp
pg-cve-mcp

Or with npx (no install):

npx -y pg-cve-mcp

MCP Tools

ToolDescription
get_cves(version)Complete security report for a version: EOL/yanked status, release date, stats, CVEs sorted by CVSS (a synthetic CVE-EOL-WARNING at 10.0 is prepended for unsupported releases)
compare_versions(v1, v2)Side-by-side CVE comparison (fixed/new/still present) with yanked & EOL flags and release dates
get_upgrade_path(from_version)Recommended upgrade (minor by default; major when EOL or next-to-EOL) with fixed CVEs and release dates
get_exploits()All CVEs with known public exploits, sorted by CVSS, with release dates
get_summary()Overview of the tracked CVE database incl. yanked releases

Transports

stdio (default)

Run locally over stdio for opencode, Claude Desktop, and other stdio MCP clients:

pip install -e .
pg-cve-mcp
Streamable HTTP (self-hosted)

For remote or enterprise deployments, serve the same tools over HTTP. Run python run_server.py (or build the Dockerfile); the server listens on $PORT (default 8000) at path /mcp:

python run_server.py
# MCP endpoint: http://127.0.0.1:8000/mcp

Configure any MCP client with the URL, e.g. in opencode.json:

{
  "mcp": {
    "pg-cve-mcp": {
      "type": "remote",
      "url": "http://127.0.0.1:8000/mcp"
    }
  }
}

Configuration

Env VarDefaultDescription
PG_CVE_MCP_TTL86400Cache TTL in seconds for CVE data
PG_CVE_MCP_DATA_URLhttps://meob.github.io/PG_CVE/postgresql_cves.jsonCVE data source URL
PORT8000HTTP port for the Streamable HTTP server (run_server.py)

Development

Run the test suite and linters:

python -m pytest
ruff check src tests
mypy src

Data Source

Data is fetched from the PG_CVE project's GitHub Pages with local caching. Falls back to a bundled copy if the network is unavailable.

Example Prompts

"What CVEs affect PostgreSQL 16.4?"

"Is PostgreSQL 15.8 safe to use?"

"Compare CVEs in 16.3 vs 16.4"

"What's the upgrade path from PostgreSQL 14.10?"

License

Apache 2.0

Frequently asked questions

What is PostgreSQL CVE & Release Intelligence?

PostgreSQL security for AI agents: CVEs, yanked releases, exploits, and upgrade paths

How do I install PostgreSQL CVE & Release Intelligence?

It runs on your machine. In Claude Code: claude mcp add postgresql-cve-release-intelligence -e 'PG_CVE_MCP_TTL=<PG_CVE_MCP_TTL>' -e 'PG_CVE_MCP_DATA_URL=<PG_CVE_MCP_DATA_URL>' -- uvx pg-cve-mcp==1.0.4. For other clients, paste the JSON configuration from this page into their MCP settings.

Does PostgreSQL CVE & Release Intelligence need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is PostgreSQL CVE & Release Intelligence open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains PostgreSQL CVE & Release Intelligence?

It is published by meob. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.