Kvmfleet MCP Server

@kvmfleet/mcp npm v0.3.1

Published by @kvmfleet — 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.

MCP server for KVM Fleet — let an AI assistant read your fleet, audit log, and compliance state and (opt-in) act on it. Includes curated governance prompts. All calls go through the platform REST API, so RBAC, policy, JIT access, and audit apply.

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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 = 99/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 − 1 = 99. 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
−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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 37

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

  • access-reviewno sensitive capability
  • acknowledge_alertno sensitive capability
  • approve_accessno sensitive capability
  • audit-integrity-checkno sensitive capability
  • compliance-evidenceno sensitive capability
  • create_report_shareno sensitive capability
  • daysno sensitive capability
  • deny_accessno sensitive capability
  • end_console_sessionno sensitive capability
  • frameworkno sensitive capability
Show 27 more tools ↓
  • get_audit_chain_headno sensitive capability
  • get_compliance_configno sensitive capability
  • get_compliance_scoreno sensitive capability
  • get_device_healthno sensitive capability
  • get_device_metricsno sensitive capability
  • get_inclusion_proofno sensitive capability
  • get_power_stateno sensitive capability
  • list_access_grantsno sensitive capability
  • list_alertsno sensitive capability
  • list_audit_witnessesno sensitive capability
  • list_devicesno sensitive capability
  • list_isosno sensitive capability
  • list_open_console_sessionsno sensitive capability
  • list_policiesno sensitive capability
  • list_policy_evaluationsno sensitive capability
  • list_report_sharesno sensitive capability
  • list_teamno sensitive capability
  • mount_isono sensitive capability
  • policy-postureno sensitive capability
  • power_actionno sensitive capability
  • query_audit_logno sensitive capability
  • render_compliance_reportno sensitive capability
  • request_accessno sensitive capability
  • resolve_alertno sensitive capability
  • revoke_accessno sensitive capability
  • unmount_isono sensitive capability
  • verify_audit_integrityno 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.3.1 latest A 99/100 0 1.13.0 2026-09-07

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

Use the free API → How scoring works

More in Security & Testing