mcp-vultr@2026.9.21.1
VERIFIED· not startedPublisher claims: "A comprehensive Model Context Protocol (MCP) server for managing Vultr DNS records" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
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
OAUTH_AUDIENCEOAUTH_CLIENT_IDOAUTH_CLIENT_SECRETOAUTH_ENABLEDOAUTH_ISSUER_URLOAUTH_JWKS_URLVULTR_API_KEY- Where it talks to
- vultr.com (its own)Also inspect.systems, docker.com, nodesource.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names inspect.systems, docker.com, nodesource.com as well as its own vendor. The guard injects OAUTH_AUDIENCE, OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET, OAUTH_ENABLED, OAUTH_ISSUER_URL, OAUTH_JWKS_URL, VULTR_API_KEY only into requests to vultr.com (and its subdomains) and refuses the rest.
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; not started: dependency install failed; the server itself was not observed) on 2026-11-10 and scored it 85/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 · 0 s · 2 scenarios · 0 deviationsStatic findings
curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo -E bash -Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.sudo lsblk | grep {device_name[5:]}Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.sudo mount {device_name} {mount_point}Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.sudo df -h {mount_point}Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."install_nfs_rhel": "sudo yum install -y nfs-utils",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.chmod a+r /etc/apt/keyrings/docker.gpgFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts."create_mount_point": f"sudo mkdir -p {mount_point}",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."ENGINE": "django.db.backends.postgresql",Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."install_nfs_alpine": "sudo apk add nfs-utils",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.sudo mkdir -p {mount_point}Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."install_nfs_ubuntu": "sudo apt update && sudo apt install -y nfs-common",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.sudo mkfs.ext4 {device_name}Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
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
No advisories in OSV for mcp-vultr@2026.9.21.1 as of 4d ago. This is the package itself, not its dependencies.