io.github.hydradns/hydra-mcp
HydraDNS
Is the HydraDNS MCP server down? Yes. It has given no valid answer since 2026-11-01: not found.
Manage a self-hosted DNS firewall: block domains, create policies, read query logs and metrics.
not found down since 2026-11-01 · probed 2026-11-14 · unchanged since 2026-11-08
Error response from daemon: failed to resolve reference "ghcr.io/hydradns/hydra-cli:0.1.0": ghcr.io/hydradns/hydra-cli:0.1.0: not found
- Run it
- docker run -i --rm ghcr.io/hydradns/hydra-cli:0.1.0 (stdio, probed in a container with the network off)
- Host
- ghcr.io
- Repository
- https://github.com/hydradns/hydradns
- Website
- https://github.com/hydradns/hydradns
- Registry
- active, updated 2026-09-21 · registry entry
Compare this server with others.
More servers
Other registry entries on ghcr.io, the ones next to this name; all of them.
- Hostim io.github.hostimdev/hostim · needs args
- Nordnet Portfolio io.github.hpasic/nordnet-mcp · crashed on start
- io.github.hughhan1/mysql · not probed
- droidmap io.github.hussainshirazi/droidmap · crashed on start
- ultra-e2e-test tasks io.github.hynix666/ultra-e2e-test · not found
- Polyglot Database MCP io.github.hyperpolymath/poly-db-mcp · not found
- Polyglot SSG MCP io.github.hyperpolymath/poly-ssg-mcp · not found
- io.github.ibeal/tidal-mcp · needs env
Servers that mention hydra.
- Pandough app.pandough/mcp · alive
- Hydrata - ANUGA Flood Simulation com.hydrata/hydrata-mcp-server · needs auth
- Hydracept com.hydracept/hydracept · needs auth
- Hydrafetch com.hydrafetch/web · alive
- com.hydrantly/site · alive
- Hydrant dev.hydrant/hydrant · needs auth
- INCOME 2 io.github.Patrickbo19/income2 · not found
- io.github.codymcc4/fuelcenter · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-11-01, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.