Opnsense (lucamarien) MCP Server

opnsense-mcp-server PyPI v0.4.0

Published by lucamarien — 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
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.
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
inspection depth (source) — how much of the target the scan could see

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 81

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

  • opn_download_configingests untrusted input
  • opn_update_dnsblreads sensitive data
  • opn_add_aliasno sensitive capability
  • opn_add_ddns_accountno sensitive capability
  • opn_add_dns_overrideno sensitive capability
  • opn_add_dnsbl_allowlistno sensitive capability
  • opn_add_dnsmasq_rangeno sensitive capability
  • opn_add_firewall_categoryno sensitive capability
  • opn_add_firewall_ruleno sensitive capability
  • opn_add_icmpv6_rulesno sensitive capability
  • opn_add_nat_ruleno sensitive capability
  • opn_arp_tableno sensitive capability
  • opn_configure_mdns_repeaterno sensitive capability
  • opn_confirm_changesno sensitive capability
  • opn_crowdsec_alertsno sensitive capability
  • opn_crowdsec_statusno sensitive capability
  • opn_delete_aliasno sensitive capability
  • opn_delete_ddns_accountno sensitive capability
  • opn_delete_dns_overrideno sensitive capability
  • opn_delete_dnsmasq_rangeno sensitive capability
  • opn_delete_firewall_categoryno sensitive capability
  • opn_delete_firewall_ruleno sensitive capability
  • opn_delete_nat_ruleno sensitive capability
  • opn_dns_lookupno sensitive capability
  • opn_dns_statsno sensitive capability
  • opn_firewall_logno sensitive capability
  • opn_gateway_statusno sensitive capability
  • opn_get_config_sectionno sensitive capability
  • opn_get_dnsblno sensitive capability
  • opn_haproxy_addno sensitive capability
  • opn_haproxy_configtestno sensitive capability
  • opn_haproxy_deleteno sensitive capability
  • opn_haproxy_getno sensitive capability
  • opn_haproxy_searchno sensitive capability
  • opn_haproxy_statusno sensitive capability
  • opn_haproxy_updateno sensitive capability
  • opn_interface_statsno sensitive capability
  • opn_ipsec_statusno sensitive capability
  • opn_ipv6_statusno sensitive capability
  • opn_list_acme_certsno sensitive capability
  • opn_list_cron_jobsno sensitive capability
  • opn_list_ddns_accountsno sensitive capability
  • opn_list_dhcp_leasesno sensitive capability
  • opn_list_dns_forwardsno sensitive capability
  • opn_list_dns_overridesno sensitive capability
  • opn_list_dnsblno sensitive capability
  • opn_list_dnsmasq_leasesno sensitive capability
  • opn_list_dnsmasq_rangesno sensitive capability
  • opn_list_firewall_aliasesno sensitive capability
  • opn_list_firewall_categoriesno sensitive capability
  • opn_list_firewall_rulesno sensitive capability
  • opn_list_kea_leasesno sensitive capability
  • opn_list_nat_rulesno sensitive capability
  • opn_list_servicesno sensitive capability
  • opn_list_static_routesno sensitive capability
  • opn_mcp_infono sensitive capability
  • opn_mdns_repeater_statusno sensitive capability
  • opn_ndp_tableno sensitive capability
  • opn_openvpn_statusno sensitive capability
  • opn_pf_statesno sensitive capability
  • opn_pingno sensitive capability
  • opn_reconfigure_ddclientno sensitive capability
  • opn_reconfigure_dnsmasqno sensitive capability
  • opn_reconfigure_haproxyno sensitive capability
  • opn_reconfigure_unboundno sensitive capability
  • opn_remove_dnsbl_allowlistno sensitive capability
  • opn_scan_configno sensitive capability
  • opn_security_auditno sensitive capability
  • opn_set_dnsblno sensitive capability
  • opn_set_rule_categoriesno sensitive capability
  • opn_system_statusno sensitive capability
  • opn_toggle_aliasno sensitive capability
  • opn_toggle_firewall_ruleno sensitive capability
  • opn_tracerouteno sensitive capability
  • opn_update_aliasno sensitive capability
  • opn_update_ddns_accountno sensitive capability
  • opn_update_dns_overrideno sensitive capability
  • opn_update_dnsmasq_rangeno sensitive capability
  • opn_update_firewall_ruleno sensitive capability
  • opn_update_nat_ruleno sensitive capability
  • opn_wireguard_statusno sensitive capability

What this scan could not see

Versions

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

Use the free API → How scoring works

Other implementations of Opnsense 4

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

More in API Development