# hetzner-dns-mcp

Manage DNS zones and records (zonefiles, RRSets, TTL, protection) via the Hetzner Cloud API

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.4.0
- **Author:** io.github.ni-c
- **License:** Unknown
- **npm:** hetzner-dns-mcp
- **Source:** https://github.com/ni-c/hetzner-dns-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 10 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-18T13:55:09.264Z
- **Version scanned:** 0.3.1
- **CVEs:** none found by OSV at scan time

## Tools

22 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `list_zone_actions`
- `get_zone_action`
- `list_rrsets`
- `get_rrset`
- `create_rrset`
- `update_rrset`
- `delete_rrset`
- `set_records`
- `add_records`
- `remove_records`
- `change_rrset_ttl`
- `change_rrset_protection`
- `list_zones`
- `get_zone`
- `export_zonefile`
- `create_zone`
- `update_zone`
- `delete_zone`
- `import_zonefile`
- `change_zone_ttl`
- `change_zone_protection`
- `change_primary_nameservers`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"hetzner-dns\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"hetzner-dns-mcp\"\n      ],\n      \"env\": {\n        \"HETZNER_API_TOKEN\": \"<YOUR_HETZNER_API_TOKEN>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `HETZNER_API_TOKEN` — Hetzner API Token (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — deletes data; holds an api key.
- Floor 54, ceiling 54 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/hetzner-dns-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/hetzner-dns-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/hetzner-dns-mcp
- HTML page: https://forgeregistry.com/registry/hetzner-dns-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.