# 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.

- Trust score: 6/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-19

## Components

- oci · `ghcr.io/hydradns/hydra-cli:0.1.0`: 6/100 (this document), [markdown](https://verifymcp.io/servers/hydradns-hydra-mcp/ghcr-io-hydradns-hydra-cli-0-1-0.md), [page](https://verifymcp.io/servers/hydradns-hydra-mcp/ghcr-io-hydradns-hydra-cli-0-1-0)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/hydradns/hydra-cli:0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-19.

- **Supply Chain Security**: 0/100
  - 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.
  - Known CVEs could not be checked: we could not find this package in its registry.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we could not find this package in its registry.
- **Provenance & Transparency**: 29/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: the declared version isn't published, so its provenance can't be verified.
  - License check failed: no license is declared.
  - Maintenance history not yet determined.
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.

**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.

## 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.

### Claude

```bash
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.

### Cursor

```json
{
  "mcpServers": {
    "hydradns-hydra-mcp": {
      "command": "docker",
      "args": [
        "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.

### VS Code

```json
{
  "servers": {
    "hydradns-hydra-mcp": {
      "command": "docker",
      "args": [
        "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.

### Codex

```bash
codex 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.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hydradns-hydra-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "HYDRA_API_URL",
        "-e",
        "HYDRA_TOKEN",
        "-e",
        "MCP_ROLE",
        "ghcr.io/hydradns/hydra-cli:0.1.0"
      ],
      "enabled": true
    }
  }
}
```

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.

### Hermes

```yaml
mcp_servers:
  hydradns-hydra-mcp:
    command: "docker"
    args: ["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.

### Netclaw

```json
{
  "McpServers": {
    "hydradns-hydra-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "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.

### Other

```json
{
  "mcpServers": {
    "hydradns-hydra-mcp": {
      "command": "docker",
      "args": [
        "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-02 (score 6, −32)

- [security regression] Stability: 0.33 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-01 (score 38, +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.

### 2026-09-29 (score 37, −3)

- [security] Provenance: Provenance check failed: the declared version isn't published, so its provenance can't be verified.
- [functional regression] Maintenance: pass → unverified
- [functional regression] License: pass → fail
- [functional] Licence: GPL-3.0

### 2026-09-28 (score 40, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 40, +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.

### 2026-09-25 (score 39, +2)

- [functional improvement] Stability: unverified → 0.13
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-21 (score 37)

First indexed and scored.

## MCP tools (0)

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.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/hydradns-hydra-mcp/ghcr-io-hydradns-hydra-cli-0-1-0#diagnostics

## Score history

- 2026-10-19: 6
- 2026-10-18: 6
- 2026-10-17: 6
- 2026-10-16: 6
- 2026-10-15: 6
- 2026-10-14: 6
- 2026-10-13: 6
- 2026-10-12: 6
- 2026-10-10: 6
- 2026-10-07: 6
- 2026-10-05: 6
- 2026-10-04: 6
- 2026-10-03: 6
- 2026-10-02: 6
- 2026-10-01: 38
- 2026-09-30: 37
- 2026-09-29: 37
- 2026-09-28: 40
- 2026-09-27: 40
- 2026-09-26: 39
- 2026-09-25: 39
- 2026-09-24: 37
- 2026-09-23: 37
- 2026-09-22: 37
- 2026-09-21: 37

## 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.

## Links

- GitHub Container Registry: https://ghcr.io/hydradns/hydra-cli
- Repository: https://github.com/hydradns/hydradns
- Changelog RSS feed: https://verifymcp.io/servers/hydradns-hydra-mcp/ghcr-io-hydradns-hydra-cli-0-1-0.xml
- Changelog JSON feed: https://verifymcp.io/servers/hydradns-hydra-mcp/ghcr-io-hydradns-hydra-cli-0-1-0.json
- HTML version of this page: https://verifymcp.io/servers/hydradns-hydra-mcp/ghcr-io-hydradns-hydra-cli-0-1-0