Victron Vrm MCP Server

victron-vrm-mcp npm v0.5.0

Published by lubosstrejcek — 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 Victron Energy VRM cloud API — remote, HTTPS, Connector-compatible

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 4

medium Tool "vrm_unlink_user" can modify the filesystemMTC-CAP-002

Tool "vrm_unlink_user" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool vrm_unlink_user

medium Tool "vrm_unlink_installation" can modify the filesystemMTC-CAP-002

Tool "vrm_unlink_installation" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool vrm_unlink_installation

low Mutating tool "vrm_unlink_user" declares no destructiveHintMTC-CAP-005

Tool "vrm_unlink_user" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool vrm_unlink_user

low Mutating tool "vrm_unlink_installation" declares no destructiveHintMTC-CAP-005

Tool "vrm_unlink_installation" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool vrm_unlink_installation

Tools 53

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

  • vrm_admin_search_downloadingests untrusted input
  • vrm_get_gps_downloadingests untrusted input
  • vrm_installation_overview_downloadingests untrusted input
  • vrm_unlink_installationwrites files
  • vrm_unlink_userwrites files
  • vrm_widgetingests untrusted input
  • vrm_widget_generator_stateingests untrusted input
  • vrm_widget_graphingests untrusted input
  • vrm_add_alarmno sensitive capability
  • vrm_add_siteno sensitive capability
Show 43 more tools ↓
  • vrm_add_systemno sensitive capability
  • vrm_admin_data_attributes_countno sensitive capability
  • vrm_admin_list_devicesno sensitive capability
  • vrm_auth_loginno sensitive capability
  • vrm_auth_login_as_demono sensitive capability
  • vrm_auth_logoutno sensitive capability
  • vrm_capabilitiesno sensitive capability
  • vrm_clear_alarmno sensitive capability
  • vrm_create_access_tokenno sensitive capability
  • vrm_create_custom_widgetno sensitive capability
  • vrm_delete_access_tokenno sensitive capability
  • vrm_delete_alarmno sensitive capability
  • vrm_delete_custom_widgetno sensitive capability
  • vrm_edit_alarmno sensitive capability
  • vrm_find_by_data_attributesno sensitive capability
  • vrm_get_alarmsno sensitive capability
  • vrm_get_custom_widgetsno sensitive capability
  • vrm_get_diagnosticsno sensitive capability
  • vrm_get_dynamic_ess_settingsno sensitive capability
  • vrm_get_forecasts_last_resetno sensitive capability
  • vrm_get_overallstatsno sensitive capability
  • vrm_get_site_idno sensitive capability
  • vrm_get_site_usersno sensitive capability
  • vrm_get_statsno sensitive capability
  • vrm_get_system_overviewno sensitive capability
  • vrm_get_tagsno sensitive capability
  • vrm_invite_userno sensitive capability
  • vrm_link_user_groupsno sensitive capability
  • vrm_list_data_attributesno sensitive capability
  • vrm_list_firmwaresno sensitive capability
  • vrm_list_installationsno sensitive capability
  • vrm_list_invitesno sensitive capability
  • vrm_patch_custom_widgetno sensitive capability
  • vrm_reset_forecastsno sensitive capability
  • vrm_search_sitesno sensitive capability
  • vrm_set_dynamic_ess_settingsno sensitive capability
  • vrm_set_favoriteno sensitive capability
  • vrm_set_invite_rightsno sensitive capability
  • vrm_set_site_settingsno sensitive capability
  • vrm_set_user_group_access_levelno sensitive capability
  • vrm_set_user_rightsno sensitive capability
  • vrm_tags_addno sensitive capability
  • vrm_tags_removeno sensitive capability

What this scan could not see

Versions 2

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.0 latest A 96/100 4 1.13.0 2026-09-07
v0.3.0 A 96/100 4 1.12.1 2026-08-14

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/victron-vrm-mcp/badge.svg)](https://mcptrustchecker.com/registry/victron-vrm-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/victron-vrm-mcp"><img src="https://mcptrustchecker.com/registry/victron-vrm-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/victron-vrm-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 victron-vrm-mcp --online

Use the free API → How scoring works

More in API Development