pg-cve-mcp 1.0.1__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright [yyyy] [name of copyright owner]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
@@ -0,0 +1,168 @@
1
+ Metadata-Version: 2.4
2
+ Name: pg-cve-mcp
3
+ Version: 1.0.1
4
+ Summary: PostgreSQL CVE & Release Intelligence MCP Server
5
+ Author: Meo Bogliolo
6
+ License: Apache-2.0
7
+ Project-URL: Homepage, https://github.com/meob/PG_CVE-MCP
8
+ Project-URL: Source, https://github.com/meob/PG_CVE-MCP
9
+ Project-URL: Tracker, https://github.com/meob/PG_CVE-MCP/issues
10
+ Keywords: postgresql,cve,security,mcp,database
11
+ Classifier: Development Status :: 4 - Beta
12
+ Classifier: Intended Audience :: System Administrators
13
+ Classifier: License :: OSI Approved :: Apache Software License
14
+ Classifier: Programming Language :: Python :: 3
15
+ Classifier: Programming Language :: Python :: 3.9
16
+ Classifier: Programming Language :: Python :: 3.10
17
+ Classifier: Programming Language :: Python :: 3.11
18
+ Classifier: Programming Language :: Python :: 3.12
19
+ Classifier: Programming Language :: Python :: 3.13
20
+ Classifier: Topic :: Database :: Database Engines/Servers
21
+ Classifier: Topic :: Security
22
+ Requires-Python: >=3.10
23
+ Description-Content-Type: text/markdown
24
+ License-File: LICENSE
25
+ Requires-Dist: mcp<2,>=1.0.0
26
+ Requires-Dist: packaging>=23.0
27
+ Provides-Extra: dev
28
+ Requires-Dist: pytest>=8; extra == "dev"
29
+ Requires-Dist: ruff>=0.6; extra == "dev"
30
+ Requires-Dist: mypy>=1.10; extra == "dev"
31
+ Dynamic: license-file
32
+
33
+ # pg-cve-mcp — PostgreSQL CVE & Release Intelligence for AI Agents
34
+
35
+ [![PyPI version](https://img.shields.io/pypi/v/pg-cve-mcp.svg)](https://pypi.org/project/pg-cve-mcp/)
36
+ [![Python versions](https://img.shields.io/pypi/pyversions/pg-cve-mcp.svg)](https://pypi.org/project/pg-cve-mcp/)
37
+ [![License](https://img.shields.io/github/license/meob/PG_CVE-MCP.svg)](https://github.com/meob/PG_CVE-MCP/blob/main/LICENSE)
38
+
39
+ <!-- mcp-name: io.github.meo/pg-cve-mcp -->
40
+
41
+ **Give your AI assistant direct access to PostgreSQL security intelligence: CVEs, yanked releases, known exploits, and upgrade paths for any version — queried, not browsed.**
42
+
43
+ ---
44
+
45
+ ## Why pg-cve-mcp?
46
+
47
+ Browsing a CVE dashboard is a human habit. **Agents need answers, not pages.**
48
+
49
+ `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.
50
+
51
+ Unlike raw NVD feeds, the PG_CVE dataset is **manually curated** to carry the same judgment a careful DBA would apply:
52
+
53
+ - **Yanked releases** flagged with the real reason (e.g. *"Data corruption using CONCURRENTLY"*)
54
+ - **Known exploits** confirmed to exist in the wild
55
+ - **EOL branches** marked, with a synthetic `CVE-EOL-WARNING` (CVSS 10.0) prepended to unsupported reports
56
+ - **Verified CVEs** — no false positives from automated scraping
57
+
58
+ ### What your agent can now do
59
+
60
+ | Prompt to your agent | Tool used | Result |
61
+ |---|---|---|
62
+ | "Is PostgreSQL 15.8 safe?" | `get_cves("15.8")` | EOL/yanked flags, full CVE list sorted by CVSS |
63
+ | "Compare 16.3 vs 16.4" | `compare_versions("16.3", "16.4")` | fixed / new / still-present CVEs |
64
+ | "Should I upgrade from 14.10?" | `get_upgrade_path("14.10")` | recommended target + the CVEs it fixes |
65
+ | "Any known exploits right now?" | `get_exploits()` | all exploitable CVEs, sorted by CVSS |
66
+ | "What does this database track?" | `get_summary()` | stats, EOL and yanked-release overview |
67
+
68
+ ### Agent-first design
69
+
70
+ Every tool returns **structured JSON**, sorted by CVSS (highest first). Tools flag *yanked* and *EOL* state explicitly on the version metadata, and `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.
71
+
72
+ See real tool outputs in the [live demo](docs/demo.md).
73
+
74
+ ---
75
+
76
+ ## Quick Start
77
+
78
+ ```bash
79
+ pip install pg-cve-mcp
80
+ pg-cve-mcp
81
+ ```
82
+
83
+ Or with `npx` (no install):
84
+
85
+ ```bash
86
+ npx -y pg-cve-mcp
87
+ ```
88
+
89
+ ## MCP Tools
90
+
91
+ | Tool | Description |
92
+ |------|-------------|
93
+ | `get_cves(version)` | Complete security report for a version: EOL/yanked status, stats, CVEs sorted by CVSS (a synthetic `CVE-EOL-WARNING` at 10.0 is prepended for unsupported releases) |
94
+ | `compare_versions(v1, v2)` | Side-by-side CVE comparison (fixed/new/still present) with yanked & EOL flags |
95
+ | `get_upgrade_path(from_version)` | Recommended upgrade (minor by default; major when EOL or next-to-EOL) with fixed CVEs |
96
+ | `get_exploits()` | All CVEs with known public exploits, sorted by CVSS |
97
+ | `get_summary()` | Overview of the tracked CVE database incl. yanked releases |
98
+
99
+ ## Transports
100
+
101
+ ### stdio (default)
102
+
103
+ Run locally over stdio for opencode, Claude Desktop, and other stdio MCP clients:
104
+
105
+ ```bash
106
+ pip install -e .
107
+ pg-cve-mcp
108
+ ```
109
+
110
+ ### Streamable HTTP (self-hosted)
111
+
112
+ For remote or enterprise deployments, serve the same tools over HTTP. Run
113
+ `python run_server.py` (or build the Dockerfile); the server listens on `$PORT`
114
+ (default 8000) at path `/mcp`:
115
+
116
+ ```bash
117
+ python run_server.py
118
+ # MCP endpoint: http://127.0.0.1:8000/mcp
119
+ ```
120
+
121
+ Configure any MCP client with the URL, e.g. in `opencode.json`:
122
+
123
+ ```json
124
+ {
125
+ "mcp": {
126
+ "pg-cve-mcp": {
127
+ "type": "remote",
128
+ "url": "http://127.0.0.1:8000/mcp"
129
+ }
130
+ }
131
+ }
132
+ ```
133
+
134
+ ## Configuration
135
+
136
+ | Env Var | Default | Description |
137
+ |---------|---------|-------------|
138
+ | `PG_CVE_MCP_TTL` | `86400` | Cache TTL in seconds for CVE data |
139
+ | `PG_CVE_MCP_DATA_URL` | `https://meob.github.io/PG_CVE/postgresql_cves.json` | CVE data source URL |
140
+ | `PORT` | `8000` | HTTP port for the Streamable HTTP server (`run_server.py`) |
141
+
142
+ ## Development
143
+
144
+ Run the test suite and linters:
145
+
146
+ ```bash
147
+ python -m pytest
148
+ ruff check src tests
149
+ mypy src
150
+ ```
151
+
152
+ ## Data Source
153
+
154
+ 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.
155
+
156
+ ## Example Prompts
157
+
158
+ > "What CVEs affect PostgreSQL 16.4?"
159
+ >
160
+ > "Is PostgreSQL 15.8 safe to use?"
161
+ >
162
+ > "Compare CVEs in 16.3 vs 16.4"
163
+ >
164
+ > "What's the upgrade path from PostgreSQL 14.10?"
165
+
166
+ ## License
167
+
168
+ Apache 2.0
@@ -0,0 +1,136 @@
1
+ # pg-cve-mcp — PostgreSQL CVE & Release Intelligence for AI Agents
2
+
3
+ [![PyPI version](https://img.shields.io/pypi/v/pg-cve-mcp.svg)](https://pypi.org/project/pg-cve-mcp/)
4
+ [![Python versions](https://img.shields.io/pypi/pyversions/pg-cve-mcp.svg)](https://pypi.org/project/pg-cve-mcp/)
5
+ [![License](https://img.shields.io/github/license/meob/PG_CVE-MCP.svg)](https://github.com/meob/PG_CVE-MCP/blob/main/LICENSE)
6
+
7
+ <!-- mcp-name: io.github.meo/pg-cve-mcp -->
8
+
9
+ **Give your AI assistant direct access to PostgreSQL security intelligence: CVEs, yanked releases, known exploits, and upgrade paths for any version — queried, not browsed.**
10
+
11
+ ---
12
+
13
+ ## Why pg-cve-mcp?
14
+
15
+ Browsing a CVE dashboard is a human habit. **Agents need answers, not pages.**
16
+
17
+ `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.
18
+
19
+ Unlike raw NVD feeds, the PG_CVE dataset is **manually curated** to carry the same judgment a careful DBA would apply:
20
+
21
+ - **Yanked releases** flagged with the real reason (e.g. *"Data corruption using CONCURRENTLY"*)
22
+ - **Known exploits** confirmed to exist in the wild
23
+ - **EOL branches** marked, with a synthetic `CVE-EOL-WARNING` (CVSS 10.0) prepended to unsupported reports
24
+ - **Verified CVEs** — no false positives from automated scraping
25
+
26
+ ### What your agent can now do
27
+
28
+ | Prompt to your agent | Tool used | Result |
29
+ |---|---|---|
30
+ | "Is PostgreSQL 15.8 safe?" | `get_cves("15.8")` | EOL/yanked flags, full CVE list sorted by CVSS |
31
+ | "Compare 16.3 vs 16.4" | `compare_versions("16.3", "16.4")` | fixed / new / still-present CVEs |
32
+ | "Should I upgrade from 14.10?" | `get_upgrade_path("14.10")` | recommended target + the CVEs it fixes |
33
+ | "Any known exploits right now?" | `get_exploits()` | all exploitable CVEs, sorted by CVSS |
34
+ | "What does this database track?" | `get_summary()` | stats, EOL and yanked-release overview |
35
+
36
+ ### Agent-first design
37
+
38
+ Every tool returns **structured JSON**, sorted by CVSS (highest first). Tools flag *yanked* and *EOL* state explicitly on the version metadata, and `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.
39
+
40
+ See real tool outputs in the [live demo](docs/demo.md).
41
+
42
+ ---
43
+
44
+ ## Quick Start
45
+
46
+ ```bash
47
+ pip install pg-cve-mcp
48
+ pg-cve-mcp
49
+ ```
50
+
51
+ Or with `npx` (no install):
52
+
53
+ ```bash
54
+ npx -y pg-cve-mcp
55
+ ```
56
+
57
+ ## MCP Tools
58
+
59
+ | Tool | Description |
60
+ |------|-------------|
61
+ | `get_cves(version)` | Complete security report for a version: EOL/yanked status, stats, CVEs sorted by CVSS (a synthetic `CVE-EOL-WARNING` at 10.0 is prepended for unsupported releases) |
62
+ | `compare_versions(v1, v2)` | Side-by-side CVE comparison (fixed/new/still present) with yanked & EOL flags |
63
+ | `get_upgrade_path(from_version)` | Recommended upgrade (minor by default; major when EOL or next-to-EOL) with fixed CVEs |
64
+ | `get_exploits()` | All CVEs with known public exploits, sorted by CVSS |
65
+ | `get_summary()` | Overview of the tracked CVE database incl. yanked releases |
66
+
67
+ ## Transports
68
+
69
+ ### stdio (default)
70
+
71
+ Run locally over stdio for opencode, Claude Desktop, and other stdio MCP clients:
72
+
73
+ ```bash
74
+ pip install -e .
75
+ pg-cve-mcp
76
+ ```
77
+
78
+ ### Streamable HTTP (self-hosted)
79
+
80
+ For remote or enterprise deployments, serve the same tools over HTTP. Run
81
+ `python run_server.py` (or build the Dockerfile); the server listens on `$PORT`
82
+ (default 8000) at path `/mcp`:
83
+
84
+ ```bash
85
+ python run_server.py
86
+ # MCP endpoint: http://127.0.0.1:8000/mcp
87
+ ```
88
+
89
+ Configure any MCP client with the URL, e.g. in `opencode.json`:
90
+
91
+ ```json
92
+ {
93
+ "mcp": {
94
+ "pg-cve-mcp": {
95
+ "type": "remote",
96
+ "url": "http://127.0.0.1:8000/mcp"
97
+ }
98
+ }
99
+ }
100
+ ```
101
+
102
+ ## Configuration
103
+
104
+ | Env Var | Default | Description |
105
+ |---------|---------|-------------|
106
+ | `PG_CVE_MCP_TTL` | `86400` | Cache TTL in seconds for CVE data |
107
+ | `PG_CVE_MCP_DATA_URL` | `https://meob.github.io/PG_CVE/postgresql_cves.json` | CVE data source URL |
108
+ | `PORT` | `8000` | HTTP port for the Streamable HTTP server (`run_server.py`) |
109
+
110
+ ## Development
111
+
112
+ Run the test suite and linters:
113
+
114
+ ```bash
115
+ python -m pytest
116
+ ruff check src tests
117
+ mypy src
118
+ ```
119
+
120
+ ## Data Source
121
+
122
+ 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.
123
+
124
+ ## Example Prompts
125
+
126
+ > "What CVEs affect PostgreSQL 16.4?"
127
+ >
128
+ > "Is PostgreSQL 15.8 safe to use?"
129
+ >
130
+ > "Compare CVEs in 16.3 vs 16.4"
131
+ >
132
+ > "What's the upgrade path from PostgreSQL 14.10?"
133
+
134
+ ## License
135
+
136
+ Apache 2.0
@@ -0,0 +1,61 @@
1
+ [build-system]
2
+ requires = ["setuptools>=75"]
3
+ build-backend = "setuptools.build_meta"
4
+
5
+ [project]
6
+ name = "pg-cve-mcp"
7
+ version = "1.0.1"
8
+ description = "PostgreSQL CVE & Release Intelligence MCP Server"
9
+ readme = "README.md"
10
+ license = {text = "Apache-2.0"}
11
+ authors = [
12
+ {name = "Meo Bogliolo"},
13
+ ]
14
+ requires-python = ">=3.10"
15
+ dependencies = [
16
+ "mcp>=1.0.0,<2",
17
+ "packaging>=23.0",
18
+ ]
19
+ keywords = ["postgresql", "cve", "security", "mcp", "database"]
20
+ classifiers = [
21
+ "Development Status :: 4 - Beta",
22
+ "Intended Audience :: System Administrators",
23
+ "License :: OSI Approved :: Apache Software License",
24
+ "Programming Language :: Python :: 3",
25
+ "Programming Language :: Python :: 3.9",
26
+ "Programming Language :: Python :: 3.10",
27
+ "Programming Language :: Python :: 3.11",
28
+ "Programming Language :: Python :: 3.12",
29
+ "Programming Language :: Python :: 3.13",
30
+ "Topic :: Database :: Database Engines/Servers",
31
+ "Topic :: Security",
32
+ ]
33
+
34
+ [project.urls]
35
+ Homepage = "https://github.com/meob/PG_CVE-MCP"
36
+ Source = "https://github.com/meob/PG_CVE-MCP"
37
+ Tracker = "https://github.com/meob/PG_CVE-MCP/issues"
38
+
39
+ [project.scripts]
40
+ pg-cve-mcp = "pg_cve_mcp.__main__:main"
41
+
42
+ [project.optional-dependencies]
43
+ dev = ["pytest>=8", "ruff>=0.6", "mypy>=1.10"]
44
+
45
+ [tool.setuptools.packages.find]
46
+ where = ["src"]
47
+
48
+ [tool.setuptools.package-data]
49
+ pg_cve_mcp = ["data/*.json"]
50
+
51
+ [tool.ruff]
52
+ line-length = 100
53
+ target-version = "py310"
54
+
55
+ [tool.ruff.lint]
56
+ select = ["E", "F", "W", "I", "UP", "B"]
57
+
58
+ [tool.mypy]
59
+ python_version = "3.10"
60
+ check_untyped_defs = true
61
+ warn_unused_ignores = true
@@ -0,0 +1,4 @@
1
+ [egg_info]
2
+ tag_build =
3
+ tag_date = 0
4
+
File without changes
@@ -0,0 +1,10 @@
1
+ from pg_cve_mcp.server import mcp
2
+
3
+
4
+ def main():
5
+ mcp.run()
6
+
7
+
8
+ if __name__ == "__main__":
9
+ main()
10
+