Hcloud MCP Server

hcloud-mcp npm v0.1.1

Published by xodus-co — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Standalone MCP server for Hetzner Cloud API — use with Cursor, Claude Desktop, CLI, or any MCP client

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/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 − 1 = 99. 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:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 76

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

  • add_load_balancer_serviceno sensitive capability
  • add_load_balancer_targetno sensitive capability
  • add_network_subnetno sensitive capability
  • apply_firewall_to_resourcesno sensitive capability
  • assign_floating_ipno sensitive capability
  • assign_primary_ipno sensitive capability
  • attach_isono sensitive capability
  • attach_server_to_networkno sensitive capability
  • attach_volumeno sensitive capability
  • change_server_typeno sensitive capability
Show 66 more tools ↓
  • create_firewallno sensitive capability
  • create_floating_ipno sensitive capability
  • create_load_balancerno sensitive capability
  • create_networkno sensitive capability
  • create_placement_groupno sensitive capability
  • create_primary_ipno sensitive capability
  • create_serverno sensitive capability
  • create_ssh_keyno sensitive capability
  • create_volumeno sensitive capability
  • delete_firewallno sensitive capability
  • delete_floating_ipno sensitive capability
  • delete_load_balancerno sensitive capability
  • delete_load_balancer_serviceno sensitive capability
  • delete_networkno sensitive capability
  • delete_network_subnetno sensitive capability
  • delete_placement_groupno sensitive capability
  • delete_primary_ipno sensitive capability
  • delete_serverno sensitive capability
  • delete_ssh_keyno sensitive capability
  • delete_volumeno sensitive capability
  • detach_isono sensitive capability
  • detach_server_from_networkno sensitive capability
  • detach_volumeno sensitive capability
  • get_actionno sensitive capability
  • get_firewallno sensitive capability
  • get_load_balancerno sensitive capability
  • get_networkno sensitive capability
  • get_pricingno sensitive capability
  • get_primary_ipno sensitive capability
  • get_serverno sensitive capability
  • get_volumeno sensitive capability
  • list_actionsno sensitive capability
  • list_datacentersno sensitive capability
  • list_firewallsno sensitive capability
  • list_floating_ipsno sensitive capability
  • list_imagesno sensitive capability
  • list_load_balancer_typesno sensitive capability
  • list_load_balancersno sensitive capability
  • list_locationsno sensitive capability
  • list_networksno sensitive capability
  • list_placement_groupsno sensitive capability
  • list_primary_ipsno sensitive capability
  • list_server_typesno sensitive capability
  • list_serversno sensitive capability
  • list_ssh_keysno sensitive capability
  • list_volumesno sensitive capability
  • power_off_serverno sensitive capability
  • power_on_serverno sensitive capability
  • reboot_serverno sensitive capability
  • remove_firewall_from_resourcesno sensitive capability
  • remove_load_balancer_targetno sensitive capability
  • reset_serverno sensitive capability
  • set_firewall_rulesno sensitive capability
  • shutdown_serverno sensitive capability
  • unassign_floating_ipno sensitive capability
  • unassign_primary_ipno sensitive capability
  • update_firewallno sensitive capability
  • update_floating_ipno sensitive capability
  • update_load_balancerno sensitive capability
  • update_load_balancer_serviceno sensitive capability
  • update_networkno sensitive capability
  • update_placement_groupno sensitive capability
  • update_primary_ipno sensitive capability
  • update_serverno sensitive capability
  • update_ssh_keyno sensitive capability
  • update_volumeno sensitive capability

What this scan could not see

Versions 1

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.

VersionScoreFindingsEngineScanned
v0.1.1 latest A 99/100 0 1.13.0 2026-09-07

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.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/hcloud-mcp/badge.svg)](https://mcptrustchecker.com/registry/hcloud-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/hcloud-mcp"><img src="https://mcptrustchecker.com/registry/hcloud-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/hcloud-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 hcloud-mcp --online

Use the free API → How scoring works

More in Cloud & DevOps