pg-cve-mcp
Related Servers
Alternatives to pg-cve-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to perform PostgreSQL database operations, monitoring, and management through natural language, including performance analysis, bloat detection, lock/deadlock monitoring, autovacuum and schema inspection, and maintenance recommendations across PostgreSQL 12-18.-

Vulners MCP Serverofficial
FlicenseNot gradedqualityBmaintenanceEnables AI assistants to query the Vulners vulnerability database for CVEs, security bulletins, and software package audits through natural language.149 PyPI7-- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to perform PostgreSQL database operations and monitoring through natural language, including performance analysis, bloat detection, lock and deadlock monitoring, autovacuum and schema inspection across PostgreSQL 12-18.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to perform PostgreSQL database operations, monitoring, and management through natural language, including performance analysis, bloat detection, lock/deadlock monitoring, autovacuum and schema inspection, with no extensions required.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to safely interact with PostgreSQL databases, perform queries, inspect schemas, and analyze query performance.2ISC
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to perform PostgreSQL database operations and monitoring through natural language, including performance analysis, bloat detection, lock/deadlock monitoring, autovacuum checks, and schema inspection across PostgreSQL 12–18 without extensions.-
TDQS
Scored across 8 tools
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.
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.
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.
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.