io.github.ni-c/hetzner-dns-mcp

Hetzner DNS

Is the Hetzner DNS MCP server down? Yes. It has given no valid answer since 2026-10-16: crashed on start.

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

crashed on start down since 2026-10-16 · probed 2026-11-15 · unchanged since 2026-10-30

MCP error -32000: Connection closed
hetzner-dns-mcp: HETZNER_API_BASE_URL is not a valid URL (19 characters)

Run it: npx -y hetzner-dns-mcp@0.6.0 (stdio, probed in a container with the network off)
Host: npmjs.com
Repository: https://github.com/ni-c/hetzner-dns-mcp
Website: https://hetzner-dns-mcp.ni-c.de
Registry: active, updated 2026-09-07 · registry entry

More servers

Other registry entries on npmjs.com, the ones next to this name; all of them.

CardDAV address books io.github.ni-c/carddav-mcp · needs env
FreshRSS io.github.ni-c/freshrss-mcp · crashed on start
Google Search Console io.github.ni-c/google-search-console-mcp · crashed on start
Healthchecks io.github.ni-c/healthchecks-mcp · needs env
IMAP mailbox io.github.ni-c/imap-mcp · crashed on start
Linkwarden io.github.ni-c/linkwarden-mcp · needs env
mcp-hub io.github.ni-c/mcp-hub · alive
Mealie MCP Server io.github.ni-c/mealie-mcp · crashed on start

Servers that mention hetzner.

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

No valid answer since 2026-10-16, in every probe since then.
The process exited on start before it answered initialize. The error output is above.