Skills/Glama/contabo-mcp

contabo-mcp@1.1.0

VERIFIED· startup only

Publisher claims: "Enables AI agents to manage the entire Contabo API, including VPS/VDS instances, snapshots, images, object storage, private networks, firewalls, DNS, domains, secrets, users, and tags, through one tool per API operation." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher kirad20 · publishing for 3 daysInstalls 0Last detonated 3d ago
$npx skills add contabo-mcp
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
CONTABO_API_PASSWORDCONTABO_AUTH_URLCONTABO_CLIENT_SECRETConfiguration, not credentials: CONTABO_API_URL, CONTABO_API_USER, CONTABO_CLIENT_ID, CONTABO_COMPACT, CONTABO_EXCLUDE_AUDITS, CONTABO_EXCLUDE_TOOLS, CONTABO_GROUPS, CONTABO_MAX_RESPONSE_CHARS, CONTABO_MAX_RETRIES, CONTABO_READ_ONLY, CONTABO_TIMEOUT_MS
Where it talks to
contabo.com (its own)
What the honeypot saw
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it with a scoped credential, under the guard. It asks for CONTABO_API_PASSWORD, CONTABO_AUTH_URL, CONTABO_CLIENT_SECRET and talks to contabo.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets CONTABO_API_PASSWORD=contabo.com,CONTABO_AUTH_URL=contabo.com,CONTABO_CLIENT_SECRET=contabo.com -- <the server's command>

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-12 and scored it 91/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 24 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
4.0sprocessdependency install exit 0
24sclaimedstartup only: exited (0) before answering · syscall: 'open', path: '/tmp/ks-detonate-si8sDl/task/home/work/acme-api/.claude/skills/contabo-mcp/src/openapi.json' } Node.js v22.23.4
24sprocessscript backend runs setup only
24sprocessno install scripts to re-run

Static findings

MEDIUM
Access to sensitive file pathstest/smoke.mjs:10 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesconst p = spawn(process.execPath, [entry], { env: { PATH: process.env.PATH, ...env } });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

No other findings across 2,487 lines in 29 files.

Cost to the agent

Instructions loaded
≈34 tok
1 file · 29 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.