A side-by-side look at the Unchore Defend and OPNSenseMCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Unchore Defend for security work; choose OPNSenseMCP for security as a local process. You can also run both side by side in one mcpServers block.
OPENROUTER_API_KEY, UNCHORE_TOKEN.OPNSENSE_HOST, OPNSENSE_API_KEY, OPNSENSE_API_SECRET, OPNSENSE_VERIFY_SSL.firewall_list_rules, firewall_create_rule, firewall_update_rule.Rows where the two servers differ are marked.
| Spec | U Unchore Defend | |
|---|---|---|
| Category | Security | Security |
| Quality signal | 36/100 · Fair | 64/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | OPENROUTER_API_KEYUNCHORE_TOKEN | OPNSENSE_HOSTOPNSENSE_API_KEYOPNSENSE_API_SECRETOPNSENSE_VERIFY_SSL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 90 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | 18 |
| Full listing | View Unchore Defend | View OPNSenseMCP |
No tool names declared yet. Check the project README from the listing page.
firewall_list_rulesList all firewall rulesfirewall_create_ruleCreate a new rulefirewall_update_ruleUpdate existing rulefirewall_delete_ruleDelete a rulefirewall_apply_changesApply pending changesnat_list_outboundList outbound NAT rulesnat_set_modeSet NAT modenat_create_outbound_ruleCreate NAT rulenat_fix_dmzFix DMZ NAT issuesnat_analyze_configAnalyze NAT configurationarp_listList ARP table entriesrouting_diagnosticsDiagnose routing issuesPaste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
No confirmed install command for Unchore Defend yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"vespo92-opnsensemcp": {
"command": "npx",
"args": [
"-y",
"opnsense-mcp-server"
],
"env": {
"OPNSENSE_HOST": "YOUR_OPNSENSE_HOST_HERE",
"OPNSENSE_API_KEY": "YOUR_OPNSENSE_API_KEY_HERE",
"OPNSENSE_API_SECRET": "YOUR_OPNSENSE_API_SECRET_HERE",
"OPNSENSE_VERIFY_SSL": "YOUR_OPNSENSE_VERIFY_SSL_HERE"
}
}
}
}