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.
Agenten stärken
Der eigene Befehl des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
uvx pg-cve-mcp==1.0.4Claude Code hat keinen Installationslink für einen lokalen Befehl. Kopieren Sie den Befehl unten und führen Sie ihn in einem Terminal aus.
PG_CVE_MCP_TTL=<value> PG_CVE_MCP_DATA_URL=<value> claude mcp add io.github.meob-pg-cve-mcp -- uvx pg-cve-mcp==1.0.4In einem Terminal ausführen.
{ "mcpServers": { "io.github.meob-pg-cve-mcp": { "command": "uvx", "args": [ "pg-cve-mcp==1.0.4" ], "env": { "PG_CVE_MCP_TTL": "<value>", "PG_CVE_MCP_DATA_URL": "<value>" } } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
Give your AI assistant direct access to PostgreSQL security intelligence: CVEs, yanked releases, known exploits, and upgrade paths for any version — queried, not browsed.
PostgreSQL security for AI agents: CVEs, yanked releases, exploits, and upgrade paths
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:
CVE-EOL-WARNING (CVSS 10.0) prepended to unsupported reportsEvery 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.
pip install pg-cve-mcp
pg-cve-mcp
Or with npx (no install):
npx -y pg-cve-mcp
Run locally over stdio for opencode, Claude Desktop, and other stdio MCP clients:
pip install -e .
pg-cve-mcp
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"
}
}
}
Run the test suite and linters:
python -m pytest
ruff check src tests
mypy src
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.
"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?"
Apache 2.0
PostgreSQL security for AI agents: CVEs, yanked releases, exploits, and upgrade paths
{ "mcpServers": { "io.github.meob-pg-cve-mcp": { "command": "uvx", "args": [ "pg-cve-mcp==1.0.4" ], "env": { "PG_CVE_MCP_TTL": "<value>", "PG_CVE_MCP_DATA_URL": "<value>" } } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Der Herausgeber nennt diese Umgebungsvariablen: PG_CVE_MCP_TTL, PG_CVE_MCP_DATA_URL.
PostgreSQL CVE & Release Intelligence läuft lokal über stdio.
Zuletzt geprüft: 2026-11-09. PostgreSQL security for AI agents: CVEs, yanked releases, exploits, and upgrade paths