io.github.Optisol-Business/db-metadata-extractor-mcp
PYPI · DB-METADATA-EXTRACTOR-MCP · 2 COMPONENTS · SCANNED SEP 20
Extract database metadata from PostgreSQL, Snowflake, SQL Server, BigQuery, and Oracle.
Recent critical change
CVE-2026-15925 affects this package (1 Sept 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security75
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 85 of 86 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 156 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the io.github.Optisol-Business/db-metadata-extractor-mcp server?
io.github.Optisol-Business/db-metadata-extractor-mcp runs locally as a PyPI package, launched with uvx db-metadata-extractor-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · db-metadata-extractor-mcp
claude mcp add optisol-business-db-metadata-extractor-mcp -- uvx db-metadata-extractor-mcp
{
"mcpServers": {
"optisol-business-db-metadata-extractor-mcp": {
"command": "uvx",
"args": [
"db-metadata-extractor-mcp"
]
}
}
} {
"servers": {
"optisol-business-db-metadata-extractor-mcp": {
"command": "uvx",
"args": [
"db-metadata-extractor-mcp"
]
}
}
} codex mcp add optisol-business-db-metadata-extractor-mcp -- uvx db-metadata-extractor-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"optisol-business-db-metadata-extractor-mcp": {
"type": "local",
"command": [
"uvx",
"db-metadata-extractor-mcp"
],
"enabled": true
}
}
} openclaw mcp add optisol-business-db-metadata-extractor-mcp --command uvx --arg db-metadata-extractor-mcp
mcp_servers:
optisol-business-db-metadata-extractor-mcp:
command: "uvx"
args: ["db-metadata-extractor-mcp"] {
"McpServers": {
"optisol-business-db-metadata-extractor-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"db-metadata-extractor-mcp"
]
}
}
} assistant mcp add optisol-business-db-metadata-extractor-mcp -t stdio -c uvx -a db-metadata-extractor-mcp
{
"mcpServers": {
"optisol-business-db-metadata-extractor-mcp": {
"command": "uvx",
"args": [
"db-metadata-extractor-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Sept 26 0
- CVE-2026-15925 affects this package: high ▼ critical
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Aug 26 0
- Malware scan: unverified → pass ▲ security
- 20 Aug 26 0
- Malware scan: pass → unverified ▼ security
- 12 Aug 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
- Malware scan: pass → unverified ▼ security
- 4 Aug 26 0
- CVE-2026-27459 affects this package: high ▼ critical
- Known CVEs: unverified → fail ▼ critical
- Score status: scored → failed ▼ critical
- Malware scan: unverified → pass ▲ security
- Dependency health: unverified → partial ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/db-metadata-extractor-mcp@0.1.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 29 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-537c-gmf6-5ccf | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-g6cj-pr64-35w5 | CVE-2026-69247 | high | yes | |
| GHSA-jwv3-5hgf-82ww | CVE-2026-69249 | high | yes | |
| GHSA-m959-cc7f-wv43 | CVE-2026-34073 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-r6ph-v2qm-q3c2 | CVE-2026-26007 | high | yes | |
| PYSEC-2026-2141 | CVE-2026-26007 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N | yes |
| PYSEC-2026-35 | CVE-2026-34073 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| PYSEC-2026-3552 | CVE-2026-69247 | none | yes | |
| PYSEC-2026-3553 | CVE-2026-69249 | none | yes | |
| PYSEC-2026-3554 | CVE-2026-69248 | none | yes | |
| GHSA-m2h6-j472-rp4c | CVE-2026-69248 | medium | yes | |
| GHSA-5pwr-322w-8jr4 | CVE-2026-27459 | high | yes | |
| GHSA-vp96-hxj8-p424 | CVE-2026-27448 | low | yes | |
| PYSEC-2026-2268 | CVE-2026-27448 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| PYSEC-2026-2269 | CVE-2026-27459 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-mf9w-mj56-hr94 | CVE-2026-28684 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H | yes |
| PYSEC-2026-2270 | CVE-2026-28684 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H | yes |
| GHSA-5cc2-282f-jjq2 | CVE-2026-15925 | critical | yes | |
| PYSEC-2026-3920 | CVE-2026-15925 | none | yes | |
| GHSA-2xpw-w6gg-jr37 | CVE-2025-66471 | high | yes | |
| GHSA-38jv-5279-wg99 | CVE-2026-21441 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-gm62-xv2j-4w53 | CVE-2025-66418 | high | yes | |
| GHSA-pq67-6m6q-mj2v | CVE-2025-50181 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-qccp-gfcp-xxvc | CVE-2026-44431 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| PYSEC-2026-141 | CVE-2026-44431 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| PYSEC-2026-1994 | CVE-2025-66471 | none | yes | |
| PYSEC-2026-1996 | CVE-2026-21441 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-1998 | CVE-2025-66418 | none | yes | |
| PYSEC-2026-1999 | CVE-2025-50181 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 85 packages
| Packages resolved | 85 |
|---|---|
| Stale | 4 |
| No linked repository | 1 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.