67
/ 100
1 month ago
glama

opnsense-mcp

Enables interaction with OPNsense firewalls through MCP tools for managing firewall rules, interfaces, DHCP leases, and system monitoring.

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 2 credentials: OPNSENSE_API_KEY, OPNSENSE_API_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configOPNSENSE_HOSTThe base URL of your OPNsense firewall (e.g., https://192.168.1.1).
🔐 secretOPNSENSE_API_KEYYour OPNsense API key.
🔐 secretOPNSENSE_API_SECRETYour OPNsense API secret.
configOPNSENSE_VERIFY_SSL(optional): Set to true to verify SSL certificates (defaults to false for self-signed certificates).
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/aesaganda-opnsense-mcp-1hl983)](https://m8ven.ai/mcp/aesaganda-opnsense-mcp-1hl983)
commit: 9427a3aa74a440d6aa6028b94214f9bccef78f34
code hash: 7b865bfde46c07d10429962885326803e1df27994fbafa85aac9feceffac99e8
verified: 6/30/2026, 9:52:16 AM
view raw JSON →