Hetzner Platform (mjmirza) MCP Server

hetzner-mcp npm v0.4.0 Source verified

Published by mjmirza — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for the full Hetzner platform: Cloud servers, networks, volumes, firewalls, load balancers, IPs, DNS, Storage Box, and Robot dedicated servers.

View on npm ↗ Repository ↗ Raw report (JSON) ↗

Trust grade

100/100

Last scanned 2026-08-31 get badge →

Trust

A · 100/100

Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.

Capability

Minimal

Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.

Coverage

Source

How much the scan could actually inspect. Shallow coverage is stated, never hidden.

A Why this grade threat 100 − adoption risk = 100/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 0 = 100. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

✓ No adoption-risk deductions — minimal blast radius, verified enough, and fully inspected.

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 25

Each tool and what it can reach — statically extracted from the published source.

cloud_assign_floating_ipno sensitive capability
cloud_assign_primary_ipno sensitive capability
cloud_attach_volumeno sensitive capability
cloud_create_firewallno sensitive capability
cloud_create_floating_ipno sensitive capability
cloud_create_load_balancerno sensitive capability
cloud_create_networkno sensitive capability
cloud_create_placement_groupno sensitive capability
cloud_create_primary_ipno sensitive capability
cloud_create_serverno sensitive capability

Show 15 more tools ↓

cloud_create_ssh_keyno sensitive capability
cloud_create_volumeno sensitive capability
cloud_delete_firewallno sensitive capability
cloud_delete_floating_ipno sensitive capability
cloud_delete_load_balancerno sensitive capability
cloud_delete_networkno sensitive capability
cloud_delete_placement_groupno sensitive capability
cloud_delete_primary_ipno sensitive capability
cloud_delete_serverno sensitive capability
cloud_delete_ssh_keyno sensitive capability
cloud_delete_volumeno sensitive capability
cloud_detach_volumeno sensitive capability
cloud_unassign_floating_ipno sensitive capability
cloud_unassign_primary_ipno sensitive capability
contribute_or_reportno sensitive capability

What this scan could not see

Tools were statically extracted from the published source (25 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

Version	Score	Findings	Engine	Scanned
`v0.4.0` latest	A 100/100	0	1.13.0	2026-08-31
`v0.3.0`	A 100/100	0	1.13.0	2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

Markdown (GitHub README)

[![MCP Trust Score](https://mcptrustchecker.com/registry/hetzner-mcp/badge.svg)](https://mcptrustchecker.com/registry/hetzner-mcp)

HTML

<a href="https://mcptrustchecker.com/registry/hetzner-mcp"><img src="https://mcptrustchecker.com/registry/hetzner-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>

Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/hetzner-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan hetzner-mcp --online

Use the free API → How scoring works

Other implementations of Hetzner Platform 4

Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →

Hetzner (lazyants) Source verified npm

@lazyants/hetzner-mcp-server

MCP server for the Hetzner Cloud API — manage servers, networks, volumes, and more

Cloud & DevOps Score 100/100 1 finding 301/wk Cap. Minimal

Hetzner (nityeshaga) npm

hetzner-mcp-server

MCP server for managing Hetzner Cloud infrastructure from Claude Code

Cloud & DevOps Score 99/100 0 findings 22/wk Cap. Minimal

Hetzner (bcanozgur) PyPI

mcp-hetzner

A Model Context Protocol (MCP) server for the Hetzner Cloud API — manage servers, volumes, firewalls, and SSH keys from Claude Code, Codex, Cursor, and any MCP client.

Cloud & DevOps Score 99/100 0 findings Cap. Minimal

Hetzner (jurislm) npm

@jurislm/hetzner-mcp

MCP server for managing Hetzner Cloud infrastructure

Cloud & DevOps Score 93/100 1 finding 19/wk Cap. High