Server data from the Official MCP Registry
Server security audit (413 checks), hardening, and fleet management across 4 cloud providers.
Server security audit (413 checks), hardening, and fleet management across 4 cloud providers.
Set these up before or after installing:
Environment variable: HETZNER_TOKEN
Environment variable: DIGITALOCEAN_TOKEN
Environment variable: VULTR_TOKEN
Environment variable: LINODE_TOKEN
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-kastelldev-kastell": {
"env": {
"VULTR_TOKEN": "your-vultr-token-here",
"LINODE_TOKEN": "your-linode-token-here",
"HETZNER_TOKEN": "your-hetzner-token-here",
"DIGITALOCEAN_TOKEN": "your-digitalocean-token-here"
},
"args": [
"-y",
"kastell"
],
"command": "npx"
}
}
}Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.
Scanned 4 files · 1 finding
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Be the first to review this server!