MCP DB Connect
NPM · MCP-DB-CONNECT
MCP server for Oracle, MSSQL, PostgreSQL, MySQL, SQLite, MongoDB, and Qdrant vector search access.
Available components
Last scanned (13 hours ago)
Scores higher than 20% of npm servers
Category Databases
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 69 of 241 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to phatngoit/MCP-DB). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 107 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox 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 →
Checks we ran (9)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
Checks we could not complete (5)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 30 Oct 26 0
- CVE-2026-109461 no longer affects this package ▲ security
- 28 Oct 26 0
- CVE-2026-109932 affects this package: high ▼ security
- CVE-2026-109829 affects this package: high ▼ security
- CVE-2026-87018 affects this package: high ▼ security
- CVE-2026-109383 affects this package: high ▼ security
- CVE-2026-87029 affects this package: high ▼ security
- 24 Oct 26 −6
- CVE-2026-109461 affects this package: high ▼ security
- CVE-2026-109869 affects this package: high ▼ security
- CVE-2026-109841 affects this package: high ▼ security
- CVE-2026-109924 affects this package: high ▼ security
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 50
- CVE-2026-97058 no longer affects this package ▲ security
- Known CVEs: partial → pass ▲ security
- 22 Oct 26 0
- CVE-2026-97058 affects this package ▼ security
- CVE-2026-19534 no longer affects this package ▲ security
- CVE-2026-85014 no longer affects this package ▲ security
- CVE-2026-84947 no longer affects this package ▲ security
- CVE-2026-84933 no longer affects this package ▲ security
- CVE-2026-84890 no longer affects this package ▲ security
- CVE-2026-18149 no longer affects this package ▲ security
- CVE-2026-18540 no longer affects this package ▲ security
- CVE-2026-85008 no longer affects this package ▲ security
- CVE-2026-84961 no longer affects this package ▲ security
- CVE-2026-85024 no longer affects this package ▲ security
- Known CVEs: fail → partial ▲ security
- 13 Oct 26 0
- Security disclosure: unverified → pass ▲ functional
- 11 Oct 26 0
- Security disclosure: pass → unverified ▼ functional
- 30 Sept 26 0
- CVE-2026-84933 affects this package: high ▼ security
- CVE-2026-18149 affects this package: high ▼ security
- CVE-2026-84947 affects this package: high ▼ security
- CVE-2026-84890 affects this package: high ▼ security
- CVE-2026-85014 affects this package: high ▼ security
- CVE-2026-85008 affects this package: high ▼ security
- CVE-2026-18540 affects this package: high ▼ security
- CVE-2026-19534 affects this package: high ▼ security
- CVE-2026-84961 affects this package: high ▼ security
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 21 Nov 2026 · Analysed npm/mcp-db-connect@0.1.21
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | phatngoit/MCP-DB |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/phatngoit/MCP-DB/.github/workflows/publish.yml@refs/tags/v0.1.21 |
| Rekor log index | 2348518548 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4e4e27fb13b69ef4b2cd232ad03f5868f3ef01d59e84f510d77fc5d3bde2ad2646501fe53c1e7808b570dc135ced9e681ba7c30444bb70031164b4b39 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 9 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-2m5v-pch6-74hx | CVE-2026-109383 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-4qv8-2p9j-2685 | CVE-2026-109924 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-4w7w-5xrc-9h26 | CVE-2026-109829 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-55wc-3pg8-jfw6 | CVE-2026-87029 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-9fm3-97px-rjf6 | CVE-2026-109932 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-f72v-6w45-q472 | CVE-2026-109841 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-qrxm-fqhp-jwvm | CVE-2026-87018 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-xjj6-f33q-929c | CVE-2026-109869 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 241 packages
| Packages resolved | 241 |
|---|---|
| Stale | 69 |
| Tree resolution | Complete |
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.
How do I install the MCP DB Connect server?
MCP DB Connect runs locally as an npm package, launched with npx -y mcp-db-connect start. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-db-connect
claude mcp add phatngoit-mcp-db-connect -- npx -y mcp-db-connect start
What is the MCP DB Connect server?
MCP DB Connect is listed in the public MCP registry as io.github.phatngoit/mcp-db-connect. MCP server for Oracle, MSSQL, PostgreSQL, MySQL, SQLite, MongoDB, and Qdrant vector search access. This page covers its npm package (mcp-db-connect).
Is the MCP DB Connect server safe to use?
MCP DB Connect scores 44 out of 100 on VerifyMCP. We recorded 9 known advisories against it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the MCP DB Connect server still maintained?
MCP DB Connect is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MCP DB Connect server under?
MCP DB Connect declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the MCP DB Connect server?
VerifyMCP ran 9 checks on MCP DB Connect, covering Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 5 items could not be completed, a gap on our side rather than a finding about MCP DB Connect: Schema quality, Stability, Tool coverage, Tool safety and 1 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.