Librenms (mhajder) MCP Server

librenms-mcp PyPI v1.10.3

Published by mhajder — 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 LibreNMS management

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 100

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

  • alert_acknowledgeno sensitive capability
  • alert_get_by_idno sensitive capability
  • alert_rule_addno sensitive capability
  • alert_rule_deleteno sensitive capability
  • alert_rule_editno sensitive capability
  • alert_rule_getno sensitive capability
  • alert_rules_listno sensitive capability
  • alert_template_createno sensitive capability
  • alert_template_deleteno sensitive capability
  • alert_template_editno sensitive capability
Show 90 more tools ↓
  • alert_template_getno sensitive capability
  • alert_templates_listno sensitive capability
  • alert_unmuteno sensitive capability
  • alerts_getno sensitive capability
  • arp_searchno sensitive capability
  • bgp_session_editno sensitive capability
  • bgp_session_getno sensitive capability
  • bgp_sessionsno sensitive capability
  • bill_create_or_updateno sensitive capability
  • bill_deleteno sensitive capability
  • bill_getno sensitive capability
  • bill_graphno sensitive capability
  • bill_graph_datano sensitive capability
  • bill_historyno sensitive capability
  • bill_history_graphno sensitive capability
  • bill_history_graph_datano sensitive capability
  • bills_listno sensitive capability
  • device_addno sensitive capability
  • device_availabilityno sensitive capability
  • device_deleteno sensitive capability
  • device_discoverno sensitive capability
  • device_eventlog_addno sensitive capability
  • device_getno sensitive capability
  • device_linksno sensitive capability
  • device_maintenance_statusno sensitive capability
  • device_outagesno sensitive capability
  • device_portsno sensitive capability
  • device_ports_getno sensitive capability
  • device_renameno sensitive capability
  • device_set_maintenanceno sensitive capability
  • device_updateno sensitive capability
  • device_vlansno sensitive capability
  • devicegroup_addno sensitive capability
  • devicegroup_add_devicesno sensitive capability
  • devicegroup_deleteno sensitive capability
  • devicegroup_devicesno sensitive capability
  • devicegroup_remove_devicesno sensitive capability
  • devicegroup_set_maintenanceno sensitive capability
  • devicegroup_updateno sensitive capability
  • devicegroups_listno sensitive capability
  • devices_listno sensitive capability
  • fdb_lookupno sensitive capability
  • health_by_typeno sensitive capability
  • health_listno sensitive capability
  • health_sensor_getno sensitive capability
  • inventory_deviceno sensitive capability
  • inventory_device_flatno sensitive capability
  • location_addno sensitive capability
  • location_deleteno sensitive capability
  • location_editno sensitive capability
  • location_getno sensitive capability
  • location_set_maintenanceno sensitive capability
  • locations_listno sensitive capability
  • logs_alertlogno sensitive capability
  • logs_authlogno sensitive capability
  • logs_eventlogno sensitive capability
  • logs_syslogno sensitive capability
  • logs_syslogsinkno sensitive capability
  • ospf_listno sensitive capability
  • ospf_portsno sensitive capability
  • oxidized_config_getno sensitive capability
  • oxidized_config_searchno sensitive capability
  • oxidized_listno sensitive capability
  • pingno sensitive capability
  • poller_group_getno sensitive capability
  • port_description_getno sensitive capability
  • port_description_updateno sensitive capability
  • port_getno sensitive capability
  • port_group_addno sensitive capability
  • port_group_assignno sensitive capability
  • port_group_list_portsno sensitive capability
  • port_group_removeno sensitive capability
  • port_groups_listno sensitive capability
  • port_ip_infono sensitive capability
  • port_transceiverno sensitive capability
  • ports_listno sensitive capability
  • ports_searchno sensitive capability
  • ports_search_fieldno sensitive capability
  • ports_search_macno sensitive capability
  • routing_ip_addressesno sensitive capability
  • sensors_listno sensitive capability
  • service_addno sensitive capability
  • service_deleteno sensitive capability
  • service_editno sensitive capability
  • services_for_deviceno sensitive capability
  • services_listno sensitive capability
  • switching_linksno sensitive capability
  • switching_vlansno sensitive capability
  • system_infono sensitive capability
  • vrf_listno 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
v1.10.3 latest A 99/100 0 1.12.1 2026-07-27

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

Use the free API → How scoring works

Other implementations of Librenms 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in API Development