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.

HydraDNS

OCI · GHCR.IO/HYDRADNS/HYDRA-CLI:0.1.0

Manage a self-hosted DNS firewall: block domains, create policies, read query logs and metrics.

Available components

oci · ghcr.io/hydradns/hydra-cli:0.1.0 6
0 this week 6 Trust /100

Last scanned (11 hours ago)

Scores higher than 10% of OCI servers

Category Security

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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: we could not find this package in its registry.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we could not find this package in its registry.Unverified
Provenance & Transparency29
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: 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.

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.

  • 2 Oct 26 −32
    • Stability: 0.33 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 1 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Sept 26 −3
    • Provenance: Provenance check failed: the declared version isn't published, so its provenance can't be verified. security
    • Maintenance: pass → unverified ▼ functional
    • License: pass → fail ▼ functional
    • Licence: GPL-3.0 functional
  • 28 Sept 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
  • 27 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 +2
    • Stability: unverified → 0.13 ▲ functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 21 Sept 26 37

    First indexed and scored.

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 19 Oct 2026 · Analysed oci/ghcr.io/hydradns/hydra-cli:0.1.0

Provenance Version not published

The package exists but this version is not published, so there is no artifact to attest.

Result Version not published
Ecosystem oci
Reason No trust root

Background: How many MCP packages publish verified provenance →

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 HydraDNS MCP server?

HydraDNS runs locally as a container image, launched with docker run --rm -i -e HYDRA_API_URL -e HYDRA_TOKEN -e MCP_ROLE ghcr.io/hydradns/hydra-cli:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/hydradns/hydra-cli:0.1.0

# add to Claude Code
claude mcp add hydradns-hydra-mcp -- docker run --rm -i -e HYDRA_API_URL -e HYDRA_TOKEN -e MCP_ROLE ghcr.io/hydradns/hydra-cli:0.1.0

This image reads HYDRA_API_URL, HYDRA_TOKEN and MCP_ROLE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

Common questions

What is the HydraDNS MCP server?

HydraDNS is an MCP server listed in the public MCP registry as io.github.hydradns/hydra-mcp. Manage a self-hosted DNS firewall: block domains, create policies, read query logs and metrics. This page covers its container image (ghcr.io/hydradns/hydra-cli:0.1.0).

Is the HydraDNS MCP server safe to use?

HydraDNS scores 6 out of 100 on VerifyMCP. 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 HydraDNS MCP server still maintained?

HydraDNS is still listed as active in the MCP registry. We last reached this channel on 19 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.