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.hydrolix/mcp-hydrolix

PYPI · MCP-HYDROLIX

An MCP server to query Hydrolix

Available components

0 this week 0 Trust /100

Last scanned (9 hours ago)

Scores higher than 0% of PyPI servers

Category Databases

Recent critical change

CVE-2026-102268 affects this package (30 Sept 2026). See the changelog before you install this server.

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 Security75
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to hydrolix/mcp-hydrolix). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 35 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 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 →

What we tested

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 →

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
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 0
    • Malware scan: pass → unverified ▼ security
  • 31 Oct 26 0
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 0
    • Malware scan: pass → unverified ▼ security
  • 20 Oct 26 0
    • Malware scan: unverified → pass ▲ security
  • 19 Oct 26 0
    • Malware scan: pass → unverified ▼ security
  • 18 Oct 26 0
    • Malware scan: unverified → pass ▲ security
  • 17 Oct 26 0
    • Malware scan: pass → unverified ▼ 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 6 Nov 2026 · Analysed pypi/mcp-hydrolix@0.2.3

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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo hydrolix/mcp-hydrolix
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/hydrolix/mcp-hydrolix/.github/workflows/publish.yml@refs/tags/v0.2.3
Rekor log index 1257100141
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:9c9c21364179b9bde2272fbac77fb2e2d4c97d0acaa2da1299c143c32d616ea2

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 33 findings
ID CVE Severity Vector Fix available
GHSA-7xgj-8392-5q4r medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-2gx3-rcp4-g85q CVE-2026-101917 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-42vr-xj54-vc7v CVE-2026-101918 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-993g-76c3-p5m4 CVE-2026-48522 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N yes
GHSA-9v7f-9g4p-ffgj CVE-2026-102267 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-ffc3-869f-jxw9 CVE-2026-102268 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-fhv5-28vv-h8m8 CVE-2026-48524 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-gvp8-978c-rx2q CVE-2026-103001 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N no
GHSA-hxm8-2xgr-2p9m CVE-2026-102269 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-jq35-7prp-9v3f CVE-2026-48523 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N yes
GHSA-jwrc-g2q2-pq5p CVE-2026-102270 medium CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H yes
GHSA-p4g4-x82p-q773 CVE-2026-102271 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-pxh4-856f-4h89 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-w6j9-cwv2-h6wq CVE-2026-102274 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-w7vc-732c-9m39 CVE-2026-48525 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-x33g-cr3x-6449 CVE-2026-102275 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N yes
GHSA-xgmm-8j9v-c9wx CVE-2026-48526 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
PYSEC-2026-175 CVE-2026-48522 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N yes
PYSEC-2026-177 CVE-2026-48524 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L yes
PYSEC-2026-178 CVE-2026-48525 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
PYSEC-2026-179 CVE-2026-48526 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
PYSEC-2026-4140 CVE-2026-101917 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
PYSEC-2026-4141 CVE-2026-101918 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
PYSEC-2026-4144 CVE-2026-102267 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
PYSEC-2026-4145 CVE-2026-102268 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N yes
PYSEC-2026-4146 CVE-2026-103001 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N no
PYSEC-2026-4147 CVE-2026-102269 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
PYSEC-2026-4148 CVE-2026-102270 medium CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-4149 CVE-2026-102271 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
PYSEC-2026-4152 CVE-2026-102274 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-4183 CVE-2026-102275 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N 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

Background: What a vulnerability scan can and cannot prove →

Dependencies 70 packages
Packages resolved 70
Stale 2
No linked repository 1
Tree resolution Complete

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.hydrolix/mcp-hydrolix server?

io.github.hydrolix/mcp-hydrolix runs locally as a PyPI package, launched with uvx mcp-hydrolix. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-hydrolix

# add to Claude Code
claude mcp add hydrolix-mcp-hydrolix -- uvx mcp-hydrolix
Common questions

What is the io.github.hydrolix/mcp-hydrolix server?

io.github.hydrolix/mcp-hydrolix is listed in the public MCP registry as io.github.hydrolix/mcp-hydrolix. An MCP server to query Hydrolix. This page covers its PyPI package (mcp-hydrolix).

Is the io.github.hydrolix/mcp-hydrolix server still maintained?

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

io.github.hydrolix/mcp-hydrolix 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.