Tazendor Opnsense MCP Server

tazendor-opnsense-mcp PyPI v0.2.4

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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 = 95/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 − 5 = 95. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 43

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

  • system_config_backupingests untrusted input
  • dhcp_lease_listno sensitive capability
  • dhcp_settings_getno sensitive capability
  • dhcp_static_listno sensitive capability
  • dns_applyno sensitive capability
  • dns_host_override_addno sensitive capability
  • dns_host_override_deleteno sensitive capability
  • dns_host_override_listno sensitive capability
  • dns_host_override_updateno sensitive capability
  • dns_settings_getno sensitive capability
Show 33 more tools ↓
  • firewall_alias_addno sensitive capability
  • firewall_alias_applyno sensitive capability
  • firewall_alias_deleteno sensitive capability
  • firewall_alias_get_uuidno sensitive capability
  • firewall_alias_listno sensitive capability
  • firewall_alias_updateno sensitive capability
  • firewall_nat_addno sensitive capability
  • firewall_nat_applyno sensitive capability
  • firewall_nat_deleteno sensitive capability
  • firewall_nat_listno sensitive capability
  • firewall_nat_updateno sensitive capability
  • firewall_rule_addno sensitive capability
  • firewall_rule_applyno sensitive capability
  • firewall_rule_deleteno sensitive capability
  • firewall_rule_getno sensitive capability
  • firewall_rule_listno sensitive capability
  • firewall_rule_updateno sensitive capability
  • ids_ruleset_listno sensitive capability
  • interface_arp_tableno sensitive capability
  • interface_configno sensitive capability
  • interface_listno sensitive capability
  • interface_ndp_tableno sensitive capability
  • route_addno sensitive capability
  • route_applyno sensitive capability
  • route_deleteno sensitive capability
  • route_listno sensitive capability
  • route_updateno sensitive capability
  • service_restartno sensitive capability
  • service_startno sensitive capability
  • service_statusno sensitive capability
  • service_stopno sensitive capability
  • system_firmware_statusno sensitive capability
  • system_statusno 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.2.4 latest A 95/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 · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/tazendor-opnsense-mcp/badge.svg)](https://mcptrustchecker.com/registry/tazendor-opnsense-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/tazendor-opnsense-mcp"><img src="https://mcptrustchecker.com/registry/tazendor-opnsense-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/tazendor-opnsense-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 tazendor-opnsense-mcp --online --registry pypi

Use the free API → How scoring works

More in Developer Tools