Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.kalehdoo/warehouse-mcp

NPM · WAREHOUSE-MCP

Production MCP server for Postgres, Oracle, Snowflake, BigQuery, Redshift, DuckDB, MotherDuck.

Available components

npm · warehouse-mcp 33
0 this week 33 Trust /100

Last scanned (45 minutes ago)

Scores higher than 5% of npm servers

Category Databases

Trust breakdown (7 categories)

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 Security79
  • 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
  • Dependency health was assessed across the 400 of 562 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency48
  • 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
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 182 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 →

Changelog

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.

  • 5 Nov 26 0
    • CVE-2026-63376 affects this package: high ▼ security
    • CVE-2026-114141 affects this package: high ▼ security
    • CVE-2026-114144 affects this package: high ▼ security
    • CVE-2026-41650 affects this package: high ▼ security
    • CVE-2026-26960 affects this package: high ▼ security
    • CVE-2026-118773 affects this package: high ▼ security
    • CVE-2026-29786 affects this package: high ▼ security
    • CVE-2026-59892 affects this package: high ▼ security
    • CVE-2026-73566 affects this package: high ▼ security
    • CVE-2025-24791 affects this package: high ▼ security
    • CVE-2026-23745 affects this package: high ▼ security
    • CVE-2026-118764 affects this package: high ▼ security
    • CVE-2026-86597 affects this package: high ▼ security
    • CVE-2026-59871 affects this package: high ▼ security
    • CVE-2026-24842 affects this package: high ▼ security
    • CVE-2026-31802 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-53655 affects this package: high ▼ security
    • CVE-2026-54285 affects this package: high ▼ security
    • CVE-2026-77465 affects this package: high ▼ security
    • CVE-2026-114142 affects this package: high ▼ security
    • CVE-2026-59873 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • CVE-2025-46328 affects this package: high ▼ security
    • CVE-2026-23950 affects this package: high ▼ security
    • CVE-2026-114143 affects this package: high ▼ security
    • CVE-2026-59874 affects this package: high ▼ security
    • CVE-2026-59875 affects this package: high ▼ security
  • 4 Nov 26 0
    • CVE-2026-63376 affects this package: high ▼ security
    • CVE-2026-114141 affects this package: high ▼ security
    • CVE-2026-114144 affects this package: high ▼ security
    • CVE-2026-41650 affects this package: high ▼ security
    • CVE-2026-26960 affects this package: high ▼ security
    • CVE-2026-118773 affects this package: high ▼ security
    • CVE-2026-29786 affects this package: high ▼ security
    • CVE-2026-59892 affects this package: high ▼ security
    • CVE-2026-73566 affects this package: high ▼ security
    • CVE-2025-24791 affects this package: high ▼ security
    • CVE-2026-23745 affects this package: high ▼ security
    • CVE-2026-118764 affects this package: high ▼ security
    • CVE-2026-86597 affects this package: high ▼ security
    • CVE-2026-59871 affects this package: high ▼ security
    • CVE-2026-24842 affects this package: high ▼ security
    • CVE-2026-31802 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-53655 affects this package: high ▼ security
    • CVE-2026-54285 affects this package: high ▼ security
    • CVE-2026-77465 affects this package: high ▼ security
    • CVE-2026-114142 affects this package: high ▼ security
    • CVE-2026-59873 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • CVE-2025-46328 affects this package: high ▼ security
    • CVE-2026-23950 affects this package: high ▼ security
    • CVE-2026-114143 affects this package: high ▼ security
    • CVE-2026-59874 affects this package: high ▼ security
    • CVE-2026-59875 affects this package: high ▼ security
  • 3 Nov 26 0
    • CVE-2026-63376 affects this package: high ▼ security
    • CVE-2026-114141 affects this package: high ▼ security
    • CVE-2026-114144 affects this package: high ▼ security
    • CVE-2026-41650 affects this package: high ▼ security
    • CVE-2026-26960 affects this package: high ▼ security
    • CVE-2026-118773 affects this package: high ▼ security
    • CVE-2026-29786 affects this package: high ▼ security
    • CVE-2026-59892 affects this package: high ▼ security
    • CVE-2026-73566 affects this package: high ▼ security
    • CVE-2025-24791 affects this package: high ▼ security
    • CVE-2026-23745 affects this package: high ▼ security
    • CVE-2026-118764 affects this package: high ▼ security
    • CVE-2026-86597 affects this package: high ▼ security
    • CVE-2026-59871 affects this package: high ▼ security
    • CVE-2026-24842 affects this package: high ▼ security
    • CVE-2026-31802 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-53655 affects this package: high ▼ security
    • CVE-2026-54285 affects this package: high ▼ security
    • CVE-2026-77465 affects this package: high ▼ security
    • CVE-2026-114142 affects this package: high ▼ security
    • CVE-2026-59873 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • CVE-2025-46328 affects this package: high ▼ security
    • CVE-2026-23950 affects this package: high ▼ security
    • CVE-2026-114143 affects this package: high ▼ security
    • CVE-2026-59874 affects this package: high ▼ security
    • CVE-2026-59875 affects this package: high ▼ security
  • 2 Nov 26 0
    • CVE-2026-63376 affects this package: high ▼ security
    • CVE-2026-114141 affects this package: high ▼ security
    • CVE-2026-114144 affects this package: high ▼ security
    • CVE-2026-41650 affects this package: high ▼ security
    • CVE-2026-26960 affects this package: high ▼ security
    • CVE-2026-118773 affects this package: high ▼ security
    • CVE-2026-29786 affects this package: high ▼ security
    • CVE-2026-59892 affects this package: high ▼ security
    • CVE-2026-73566 affects this package: high ▼ security
    • CVE-2025-24791 affects this package: high ▼ security
    • CVE-2026-23745 affects this package: high ▼ security
    • CVE-2026-118764 affects this package: high ▼ security
    • CVE-2026-86597 affects this package: high ▼ security
    • CVE-2026-59871 affects this package: high ▼ security
    • CVE-2026-24842 affects this package: high ▼ security
    • CVE-2026-31802 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-53655 affects this package: high ▼ security
    • CVE-2026-54285 affects this package: high ▼ security
    • CVE-2026-77465 affects this package: high ▼ security
    • CVE-2026-114142 affects this package: high ▼ security
    • CVE-2026-59873 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • CVE-2025-46328 affects this package: high ▼ security
    • CVE-2026-23950 affects this package: high ▼ security
    • CVE-2026-114143 affects this package: high ▼ security
    • CVE-2026-59874 affects this package: high ▼ security
    • CVE-2026-59875 affects this package: high ▼ security
  • 1 Nov 26 0
    • CVE-2026-63376 affects this package: high ▼ security
    • CVE-2026-114141 affects this package: high ▼ security
    • CVE-2026-114144 affects this package: high ▼ security
    • CVE-2026-41650 affects this package: high ▼ security
    • CVE-2026-26960 affects this package: high ▼ security
    • CVE-2026-118773 affects this package: high ▼ security
    • CVE-2026-29786 affects this package: high ▼ security
    • CVE-2026-59892 affects this package: high ▼ security
    • CVE-2026-73566 affects this package: high ▼ security
    • CVE-2025-24791 affects this package: high ▼ security
    • CVE-2026-23745 affects this package: high ▼ security
    • CVE-2026-118764 affects this package: high ▼ security
    • CVE-2026-86597 affects this package: high ▼ security
    • CVE-2026-59871 affects this package: high ▼ security
    • CVE-2026-24842 affects this package: high ▼ security
    • CVE-2026-31802 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-53655 affects this package: high ▼ security
    • CVE-2026-54285 affects this package: high ▼ security
    • CVE-2026-77465 affects this package: high ▼ security
    • CVE-2026-114142 affects this package: high ▼ security
    • CVE-2026-59873 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • CVE-2025-46328 affects this package: high ▼ security
    • CVE-2026-23950 affects this package: high ▼ security
    • CVE-2026-114143 affects this package: high ▼ security
    • CVE-2026-59874 affects this package: high ▼ security
    • CVE-2026-59875 affects this package: high ▼ security
  • 31 Oct 26 0
    • CVE-2026-118773 affects this package: high ▼ security
    • CVE-2026-118764 affects this package: high ▼ security
  • 27 Oct 26 0
    • CVE-2026-114142 affects this package: high ▼ security
  • 24 Oct 26 −2
    • CVE-2023-54404 affects this package: high ▼ security
Diagnostics

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 5 Nov 2026 · Analysed npm/warehouse-mcp@0.4.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 28 findings
ID CVE Severity Vector Fix available
GHSA-8988-4f7v-96qf CVE-2026-54285 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-45rx-2jwx-cxfr CVE-2026-59892 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-gh4j-gqv2-49f6 CVE-2026-41650 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-3g3m-2fjr-6pw4 CVE-2026-118773 medium yes
GHSA-g3hv-75wg-m249 CVE-2026-118764 medium yes
GHSA-qqj6-54q6-cxv6 CVE-2026-86597 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N yes
GHSA-wmjq-jrm2-9wfr CVE-2025-46328 low CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N yes
GHSA-xfhv-wqj6-rx99 CVE-2025-24791 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N yes
GHSA-23hp-3jrh-7fpw CVE-2026-59873 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-34x7-hfp2-rc4v CVE-2026-24842 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N yes
GHSA-83g3-92jg-28cx CVE-2026-26960 high CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N yes
GHSA-8qq5-rm4j-mr97 CVE-2026-23745 high yes
GHSA-8x88-c5mf-7j5w CVE-2026-59874 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-9ppj-qmqm-q256 CVE-2026-31802 high yes
GHSA-gvwx-54wh-qm9j CVE-2026-59875 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-qffp-2rhf-9h96 CVE-2026-29786 high yes
GHSA-r292-9mhp-454m CVE-2026-73566 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-r6q2-hw4h-h46w CVE-2026-23950 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L yes
GHSA-vmf3-w455-68vh CVE-2026-53655 medium yes
GHSA-w8wr-v893-vjvp CVE-2026-59871 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-4qx8-w7c3-pj3p CVE-2026-114141 high yes
GHSA-82x6-q7mm-w9cf CVE-2026-77465 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-9j65-hcg3-gc64 CVE-2026-114143 high yes
GHSA-9qmh-m7c6-f92p CVE-2026-114144 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-h895-cgqg-jf52 CVE-2026-114142 high yes
GHSA-v5mp-jgw5-2x6j CVE-2026-63376 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N 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 400 packages
Packages resolved 400
Deprecated 16
Stale 125
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools

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.

Install

How do I install the io.github.kalehdoo/warehouse-mcp server?

io.github.kalehdoo/warehouse-mcp runs locally as an npm package, launched with npx -y warehouse-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · warehouse-mcp

# add to Claude Code
claude mcp add kalehdoo-warehouse-mcp -- npx -y warehouse-mcp
Common questions

What is the io.github.kalehdoo/warehouse-mcp server?

io.github.kalehdoo/warehouse-mcp is listed in the public MCP registry as io.github.kalehdoo/warehouse-mcp. Production MCP server for Postgres, Oracle, Snowflake, BigQuery, Redshift, DuckDB, MotherDuck. This page covers its npm package (warehouse-mcp).

Is the io.github.kalehdoo/warehouse-mcp server safe to use?

io.github.kalehdoo/warehouse-mcp scores 33 out of 100 on VerifyMCP. We recorded 28 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.kalehdoo/warehouse-mcp server still maintained?

io.github.kalehdoo/warehouse-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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.kalehdoo/warehouse-mcp server under?

io.github.kalehdoo/warehouse-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.