Vultr MCP Server

mcp-vultr PyPI v2.4.1

Published by an unidentified publisher — 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.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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
Moderate
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 = 96/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 − 4 = 96. 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
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−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 1

medium Hardcoded egress to an external endpoint (src/mcp_vultr/serverless_inference_analyzer.py)MTC-SRC-003

In the server's implementation (`src/mcp_vultr/serverless_inference_analyzer.py:492`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: }} ] }} response = requests.post( 'https://api.vultr.com/v2/inference/chat/completions', headers=headers,

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/mcp_vultr/serverless_inference_analyzer.py

Tools 200

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

  • analyze_cdn_performanceno sensitive capability
  • analyze_database_migration_statusno sensitive capability
  • analyze_database_performanceno sensitive capability
  • analyze_domainno sensitive capability
  • analyze_kubernetes_cluster_costsno sensitive capability
  • analyze_spending_trendsno sensitive capability
  • attachno sensitive capability
  • configure_basic_web_lbno sensitive capability
  • createno sensitive capability
  • create_bare_metal_serverno sensitive capability
Show 190 more tools ↓
  • create_cdn_ssl_certificateno sensitive capability
  • create_cdn_zoneno sensitive capability
  • create_connection_poolno sensitive capability
  • create_domainno sensitive capability
  • create_forwarding_ruleno sensitive capability
  • create_groupno sensitive capability
  • create_ipv4no sensitive capability
  • create_isono sensitive capability
  • create_kafka_topicno sensitive capability
  • create_kubernetes_clusterno sensitive capability
  • create_kubernetes_node_poolno sensitive capability
  • create_logical_databaseno sensitive capability
  • create_read_replicano sensitive capability
  • create_recordno sensitive capability
  • create_ruleno sensitive capability
  • create_userno sensitive capability
  • deleteno sensitive capability
  • delete_bare_metal_serverno sensitive capability
  • delete_cdn_ssl_certificateno sensitive capability
  • delete_cdn_zoneno sensitive capability
  • delete_connection_poolno sensitive capability
  • delete_domainno sensitive capability
  • delete_forwarding_ruleno sensitive capability
  • delete_groupno sensitive capability
  • delete_ipv4no sensitive capability
  • delete_isono sensitive capability
  • delete_kafka_topicno sensitive capability
  • delete_kubernetes_clusterno sensitive capability
  • delete_kubernetes_cluster_with_resourcesno sensitive capability
  • delete_kubernetes_nodeno sensitive capability
  • delete_kubernetes_node_poolno sensitive capability
  • delete_logical_databaseno sensitive capability
  • delete_recordno sensitive capability
  • delete_ruleno sensitive capability
  • delete_sslno sensitive capability
  • delete_userno sensitive capability
  • detachno sensitive capability
  • disable_auto_sslno sensitive capability
  • export_zone_fileno sensitive capability
  • find_by_regionno sensitive capability
  • fork_databaseno sensitive capability
  • generate_docker_credentialsno sensitive capability
  • generate_kubernetes_credentialsno sensitive capability
  • getno sensitive capability
  • get_account_infono sensitive capability
  • get_applicationno sensitive capability
  • get_application_deployment_guideno sensitive capability
  • get_applications_by_vendorno sensitive capability
  • get_bandwidthno sensitive capability
  • get_bare_metal_bandwidthno sensitive capability
  • get_bare_metal_neighborsno sensitive capability
  • get_bare_metal_planno sensitive capability
  • get_bare_metal_serverno sensitive capability
  • get_bare_metal_server_summaryno sensitive capability
  • get_bare_metal_user_datano sensitive capability
  • get_cdn_available_regionsno sensitive capability
  • get_cdn_ssl_certificateno sensitive capability
  • get_cdn_zoneno sensitive capability
  • get_cdn_zone_logsno sensitive capability
  • get_cdn_zone_statsno sensitive capability
  • get_cdn_zone_summaryno sensitive capability
  • get_configuration_summaryno sensitive capability
  • get_connection_poolno sensitive capability
  • get_cost_breakdown_by_serviceno sensitive capability
  • get_current_balanceno sensitive capability
  • get_current_month_summaryno sensitive capability
  • get_deployment_examplesno sensitive capability
  • get_docker_login_commandno sensitive capability
  • get_domainno sensitive capability
  • get_firewall_ruleno sensitive capability
  • get_forwarding_ruleno sensitive capability
  • get_groupno sensitive capability
  • get_health_statusno sensitive capability
  • get_invoiceno sensitive capability
  • get_isono sensitive capability
  • get_iso_by_nameno sensitive capability
  • get_kafka_topicno sensitive capability
  • get_kubernetes_available_upgradesno sensitive capability
  • get_kubernetes_clusterno sensitive capability
  • get_kubernetes_cluster_configno sensitive capability
  • get_kubernetes_cluster_resourcesno sensitive capability
  • get_kubernetes_cluster_statusno sensitive capability
  • get_kubernetes_nodeno sensitive capability
  • get_kubernetes_node_poolno sensitive capability
  • get_kubernetes_versionsno sensitive capability
  • get_last_month_summaryno sensitive capability
  • get_logical_databaseno sensitive capability
  • get_maintenance_updatesno sensitive capability
  • get_marketplace_app_variablesno sensitive capability
  • get_migration_statusno sensitive capability
  • get_monthly_usage_summaryno sensitive capability
  • get_mounting_instructionsno sensitive capability
  • get_operating_systemno sensitive capability
  • get_os_by_nameno sensitive capability
  • get_payment_summaryno sensitive capability
  • get_planno sensitive capability
  • get_popular_marketplace_appsno sensitive capability
  • get_recordno sensitive capability
  • get_registry_infono sensitive capability
  • get_ruleno sensitive capability
  • get_s3_configno sensitive capability
  • get_storage_summaryno sensitive capability
  • get_usageno sensitive capability
  • get_userno sensitive capability
  • get_volume_statusno sensitive capability
  • import_zone_fileno sensitive capability
  • list_application_categoriesno sensitive capability
  • list_application_imagesno sensitive capability
  • list_attachedno sensitive capability
  • list_available_versionsno sensitive capability
  • list_backupsno sensitive capability
  • list_bare_metal_plansno sensitive capability
  • list_bare_metal_serversno sensitive capability
  • list_bare_metal_servers_by_regionno sensitive capability
  • list_bare_metal_servers_by_statusno sensitive capability
  • list_billing_historyno sensitive capability
  • list_by_regionno sensitive capability
  • list_cdn_zonesno sensitive capability
  • list_cluster_tiersno sensitive capability
  • list_clustersno sensitive capability
  • list_connection_poolsno sensitive capability
  • list_custom_isosno sensitive capability
  • list_databasesno sensitive capability
  • list_domainsno sensitive capability
  • list_firewall_rulesno sensitive capability
  • list_forwarding_rulesno sensitive capability
  • list_groupsno sensitive capability
  • list_invoice_itemsno sensitive capability
  • list_invoicesno sensitive capability
  • list_ipv4no sensitive capability
  • list_ipv6no sensitive capability
  • list_isosno sensitive capability
  • list_kafka_topicsno sensitive capability
  • list_kubernetes_clustersno sensitive capability
  • list_kubernetes_node_poolsno sensitive capability
  • list_kubernetes_nodesno sensitive capability
  • list_linux_osno sensitive capability
  • list_operating_systemsno sensitive capability
  • list_os_by_familyno sensitive capability
  • list_plansno sensitive capability
  • list_public_isosno sensitive capability
  • list_recordsno sensitive capability
  • list_rulesno sensitive capability
  • list_unattachedno sensitive capability
  • list_usersno sensitive capability
  • list_vc2_plansno sensitive capability
  • list_vhf_plansno sensitive capability
  • list_voc_plansno sensitive capability
  • list_windows_osno sensitive capability
  • promote_read_replicano sensitive capability
  • purge_cdn_zoneno sensitive capability
  • rebootno sensitive capability
  • reboot_bare_metal_serverno sensitive capability
  • recycle_kubernetes_nodeno sensitive capability
  • regenerate_keysno sensitive capability
  • reinstallno sensitive capability
  • reinstall_bare_metal_serverno sensitive capability
  • restore_from_backupno sensitive capability
  • scale_kubernetes_node_poolno sensitive capability
  • search_applicationsno sensitive capability
  • search_bare_metal_plansno sensitive capability
  • search_os_by_nameno sensitive capability
  • setup_cdn_for_websiteno sensitive capability
  • setup_kubernetes_cluster_for_workloadno sensitive capability
  • setup_mysql_databaseno sensitive capability
  • setup_postgresql_databaseno sensitive capability
  • setup_web_server_rulesno sensitive capability
  • setup_websiteno sensitive capability
  • startno sensitive capability
  • start_bare_metal_serverno sensitive capability
  • start_maintenanceno sensitive capability
  • start_migrationno sensitive capability
  • start_version_upgradeno sensitive capability
  • stopno sensitive capability
  • stop_bare_metal_serverno sensitive capability
  • stop_migrationno sensitive capability
  • updateno sensitive capability
  • update_bare_metal_serverno sensitive capability
  • update_cdn_zoneno sensitive capability
  • update_connection_poolno sensitive capability
  • update_groupno sensitive capability
  • update_kafka_topicno sensitive capability
  • update_kubernetes_clusterno sensitive capability
  • update_kubernetes_node_poolno sensitive capability
  • update_recordno sensitive capability
  • update_userno sensitive capability
  • update_user_access_controlno sensitive capability
  • upgrade_kubernetes_clusterno sensitive capability
  • validate_recordno sensitive capability
  • validate_s3_accessno 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
v2.4.1 latest A 96/100 1 1.9.0 2026-07-23

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

Use the free API → How scoring works

More in Cloud & DevOps