Vultr Blade MCP Server

vultr-blade-mcp npm v0.5.1 Source verified

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

Trust grade
A
100/100
Last scanned 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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
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 50

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

  • vultr_account_infono sensitive capability
  • vultr_billing_historyno sensitive capability
  • vultr_bm_bandwidthno sensitive capability
  • vultr_bm_createno sensitive capability
  • vultr_bm_deleteno sensitive capability
  • vultr_bm_getno sensitive capability
  • vultr_bm_listno sensitive capability
  • vultr_bm_list_plansno sensitive capability
  • vultr_bm_rebootno sensitive capability
  • vultr_bm_startno sensitive capability
Show 40 more tools ↓
  • vultr_bm_stopno sensitive capability
  • vultr_dns_create_recordno sensitive capability
  • vultr_dns_delete_recordno sensitive capability
  • vultr_dns_list_domainsno sensitive capability
  • vultr_dns_list_recordsno sensitive capability
  • vultr_dns_update_recordno sensitive capability
  • vultr_fw_create_groupno sensitive capability
  • vultr_fw_create_ruleno sensitive capability
  • vultr_fw_delete_groupno sensitive capability
  • vultr_fw_get_groupno sensitive capability
  • vultr_fw_list_groupsno sensitive capability
  • vultr_fw_list_rulesno sensitive capability
  • vultr_inference_createno sensitive capability
  • vultr_inference_deleteno sensitive capability
  • vultr_inference_getno sensitive capability
  • vultr_inference_listno sensitive capability
  • vultr_inference_usageno sensitive capability
  • vultr_script_createno sensitive capability
  • vultr_script_deleteno sensitive capability
  • vultr_script_getno sensitive capability
  • vultr_script_listno sensitive capability
  • vultr_snap_createno sensitive capability
  • vultr_snap_deleteno sensitive capability
  • vultr_snap_getno sensitive capability
  • vultr_snap_listno sensitive capability
  • vultr_vm_bandwidthno sensitive capability
  • vultr_vm_createno sensitive capability
  • vultr_vm_deleteno sensitive capability
  • vultr_vm_getno sensitive capability
  • vultr_vm_listno sensitive capability
  • vultr_vm_list_imagesno sensitive capability
  • vultr_vm_list_plansno sensitive capability
  • vultr_vm_list_regionsno sensitive capability
  • vultr_vm_rebootno sensitive capability
  • vultr_vm_set_reverse_dnsno sensitive capability
  • vultr_vm_ssh_keysno sensitive capability
  • vultr_vm_startno sensitive capability
  • vultr_vm_statusno sensitive capability
  • vultr_vm_stopno sensitive capability
  • vultr_vm_updateno 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.5.1 latest A 100/100 0 1.9.0 2026-07-24

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

Use the free API → How scoring works

More in Developer Tools