io.github.sijunkim/db-gateway
NPM · DB-GATEWAY
145+ tools across 8 databases: MySQL, PostgreSQL, Redshift, MongoDB, Redis, Kafka, and more
Available components
Last scanned (16 hours ago)
Scores higher than 38% 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 Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 46 of 171 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to sijunkim/db-gateway). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 103 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
- Instruction-quality not yet verified: the AI judgement didn't run.Unverified
- Nothing to assess: this server exposes no tool/resource definitions to measure a footprint for. See how to fix → Fail
- Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage0
- Nothing to assess: this server exposes no tools, so there are no tool definitions to check for coverage.Fail
Tool Safety0
- Injection markers not yet verified: our capture carried no server instructions, tool names or descriptions for the scan to read.Unverified
- Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.Unverified
- Manipulation not yet verified: our capture carried no tool text for a judge to read, so we will not certify text no model has read as clean.Unverified
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- MCP protocol
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.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
- Schema quality in Schema Quality & AI UsabilityInstruction-quality not yet verified: the AI judgement didn't run.
- Injection markers in Tool Safety (scores 0 for this)Injection markers not yet verified: our capture carried no server instructions, tool names or descriptions for the scan to read.
- Destructive annotations in Tool Safety (scores 0 for this)Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.
- Judged manipulation in Tool Safety (scores 0 for this)Manipulation not yet verified: our capture carried no tool text for a judge to read, so we will not certify text no model has read as clean.
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.
- 21 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 20 Nov 26 0
- Stability: 0.97 → pass security
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 −1
- Stability: pass → 0.93 functional
- 14 Nov 26 0
- Package version: 1.0.2 → 1.0.4 functional
- 12 Nov 26 0
- Stability: 0.97 → pass security
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 −1
- Stability: pass → 0.90 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 21 Nov 2026 · Analysed npm/db-gateway@1.0.4
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 | sijunkim/db-gateway |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sijunkim/db-gateway/.github/workflows/release.yml@refs/tags/v1.0.4 |
| Rekor log index | 2396037395 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ed6be6e4272570ffd1a79cd1d38dff062769ed750c18da75c8a14728f049558f14b94033e09c865ea6e27cb2cdcf6cd9306e6d1f2ac05a4e4e76af881 |
Background: How many MCP packages publish verified provenance →
Dependencies 171 packages
| Packages resolved | 171 |
|---|---|
| Stale | 46 |
| 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 →
The sandbox run completed and this package exposed no tools.
How do I install the io.github.sijunkim/db-gateway MCP server?
io.github.sijunkim/db-gateway runs locally as an npm package, launched with npx -y db-gateway. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · db-gateway
claude mcp add sijunkim-db-gateway -- npx -y db-gateway
What is the io.github.sijunkim/db-gateway MCP server?
io.github.sijunkim/db-gateway is an MCP server listed in the public MCP registry as io.github.sijunkim/db-gateway. 145+ tools across 8 databases: MySQL, PostgreSQL, Redshift, MongoDB, Redis, Kafka, and more. This page covers its npm package (db-gateway).
Is the io.github.sijunkim/db-gateway MCP server safe to use?
io.github.sijunkim/db-gateway scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting 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.
What tools does the io.github.sijunkim/db-gateway MCP server expose?
io.github.sijunkim/db-gateway exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.
Is the io.github.sijunkim/db-gateway MCP server still maintained?
io.github.sijunkim/db-gateway 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 io.github.sijunkim/db-gateway MCP server under?
io.github.sijunkim/db-gateway 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 io.github.sijunkim/db-gateway MCP server?
VerifyMCP ran 12 checks on io.github.sijunkim/db-gateway, covering Malware scan, Known CVEs, Install scripts, Dependency health and 8 more. 5 items could not be completed, a gap on our side rather than a finding about io.github.sijunkim/db-gateway: Security disclosure, Schema quality, Injection markers, Destructive annotations and 1 more. One category scores 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.