Skip to main content
Glama
pg-cve-mcp

pg-cve-mcp

by meob
README.md
# 🐘 pg-cve-mcp — PostgreSQL CVE & Release Intelligence for AI Agents

[![PyPI version](https://img.shields.io/pypi/v/pg-cve-mcp.svg)](https://pypi.org/project/pg-cve-mcp/)
[![Python versions](https://img.shields.io/pypi/pyversions/pg-cve-mcp.svg)](https://pypi.org/project/pg-cve-mcp/)
[![License](https://img.shields.io/github/license/meob/PG_CVE-MCP.svg)](https://github.com/meob/PG_CVE-MCP/blob/main/LICENSE)

<!-- mcp-name: io.github.meob/pg-cve-mcp -->

**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**](https://github.com/meob/PG_CVE) project — the same one powering the [PostgreSQL CVE Dashboard](https://meob.github.io/PG_CVE/) — 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 agent | Tool used | Result |
|---|---|---|
| "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. `get_summary()` also reports `last_updated`, so agents can state how fresh the snapshot is.

See real tool outputs in the [live demo](docs/demo.md).

---

## Quick Start

```bash
pip install pg-cve-mcp
pg-cve-mcp
```

Or with `npx` (no install):

```bash
npx -y pg-cve-mcp
```

## MCP Tools

| Tool | Description |
|------|-------------|
| `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 and dataset `last_updated` |

## Transports

### stdio (default)

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

```bash
pip install -e .
pg-cve-mcp
```

### Streamable HTTP (self-hosted)

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

```bash
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`:

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

The v2 SDK enables DNS-rebinding protection by default for localhost-only apps, which
rejects requests sent to a real hostname with `421 Misdirected Request`. This server
therefore configures `transport_security` explicitly. By default any `Host` header is
accepted (`*`), preserving Docker/self-hosted behavior. For production, restrict it:

```bash
PG_CVE_MCP_ALLOWED_HOSTS="mcp.example.com:443" python run_server.py
```

Set a comma-separated list of allowed `Host` values; wildcard ports such as
`mcp.example.com:*` are supported. Restricting hosts protects remote deployments from
DNS-rebinding attacks.

## Configuration

| Env Var | Default | Description |
|---------|---------|-------------|
| `PG_CVE_MCP_TTL` | `86400` | Cache TTL in seconds for CVE data |
| `PG_CVE_MCP_DATA_URL` | `https://meob.github.io/PG_CVE/postgresql_cves.json` | CVE data source URL |
| `PG_CVE_MCP_ALLOWED_HOSTS` | `*` | Comma-separated allowed `Host` headers for Streamable HTTP; `*` disables the host restriction |
| `PORT` | `8000` | HTTP port for the Streamable HTTP server (`run_server.py`) |

## Development

Run the test suite and linters:

```bash
python -m pytest
ruff check src tests
mypy src
```

## Data Source

Data is fetched from the [PG_CVE](https://github.com/meob/PG_CVE) project's GitHub Pages with local caching. Falls back to a bundled copy if the network is unavailable. The dataset tracks PostgreSQL 19 as active and 14 as end-of-life; `get_summary()` reports its `last_updated` date.

## Example Prompts

> "What CVEs affect PostgreSQL 19.0?"
>
> "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

TDQS

A3.9/5.0

Scored across 8 tools

Disambiguation4/5

Each tool targets a distinct purpose: latest minor, summary stats, CVE listing, status summary, comparison, upgrade path, yanked list, and exploits. Some overlap exists between get_latest_minor and get_upgrade_path (both involve latest minor) and between get_cves and get_exploits (both list CVEs), but descriptions clarify the differences.

Naming Consistency4/5

Seven of eight tools follow the get_<object> pattern (e.g., get_summary, get_yanked_versions), but compare_versions deviates by using a verb_prefix style. The overall pattern is clear and predictable, with only one outlier.

Tool Count5/5

Eight tools is well within the ideal 3–15 range for a domain-specific server. Each tool covers a distinct query or operation relevant to PostgreSQL CVE tracking, with no redundancy or bloat.

Completeness4/5

The tool set covers core workflows: version lookup, CVE listing, comparison, upgrade suggestions, yanked releases, and exploit lists. Minor gaps include no tool to list all available major versions or fetch individual CVE details, but these are not critical for the server's apparent purpose.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues