Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.antonio-mello-ai/mcp-pfsense

PYPI · MCP-PFSENSE · SCANNED SEP 20

Manage pfSense firewalls through AI assistants — rules, DHCP, DNS, and more

Available components

−15 this week 61 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency32
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 923 tokens (~48/item across 19 items; 19 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_firewall_rule" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.antonio-mello-ai/mcp-pfsense server?

io.github.antonio-mello-ai/mcp-pfsense runs locally as a PyPI package, launched with uvx mcp-pfsense. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-pfsense

# add to Claude Code
claude mcp add antonio-mello-ai-mcp-pfsense -- uvx mcp-pfsense
// .cursor/mcp.json
{
  "mcpServers": {
    "antonio-mello-ai-mcp-pfsense": {
      "command": "uvx",
      "args": [
        "mcp-pfsense"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "antonio-mello-ai-mcp-pfsense": {
      "command": "uvx",
      "args": [
        "mcp-pfsense"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add antonio-mello-ai-mcp-pfsense -- uvx mcp-pfsense
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "antonio-mello-ai-mcp-pfsense": {
      "type": "local",
      "command": [
        "uvx",
        "mcp-pfsense"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add antonio-mello-ai-mcp-pfsense --command uvx --arg mcp-pfsense
# ~/.hermes/config.yaml
mcp_servers:
  antonio-mello-ai-mcp-pfsense:
    command: "uvx"
    args: ["mcp-pfsense"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "antonio-mello-ai-mcp-pfsense": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-pfsense"
      ]
    }
  }
}
# add to Vellum
assistant mcp add antonio-mello-ai-mcp-pfsense -t stdio -c uvx -a mcp-pfsense
// mcp.json
{
  "mcpServers": {
    "antonio-mello-ai-mcp-pfsense": {
      "command": "uvx",
      "args": [
        "mcp-pfsense"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 0
    • Package version: 0.1.1 → 0.2.0 functional
  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 −14
    • Malware scan: pass → unverified security
  • 12 Sept 26 +16
    • Malware scan: unverified → pass security
  • 11 Sept 26 −15
    • Malware scan: pass → unverified security
  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed pypi/mcp-pfsense@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 19 exposed · ~911 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_dhcp_static_mapping ~85

Create a DHCP static mapping (IP reservation) for a MAC address. Staged until apply_changes('dhcp') is called or apply=true is passed.

NameTypeReqDescription
applyboolean
descrstring
hostnamestring
interfacestringyes
ipaddrstringyes
macstringyes

Structured output declared, but exposes no named fields.

No examples provided.

add_dns_host_override ~73

Create a DNS host override entry in Unbound DNS Resolver. Staged until apply_changes('dns') is called or apply=true is passed.

NameTypeReqDescription
applyboolean
descrstring
domainstringyes
hoststringyes
ipstringyes

Structured output declared, but exposes no named fields.

No examples provided.

add_firewall_rule ~113

Add a firewall rule. Type is 'pass', 'block', or 'reject'. The rule is staged (not active) until apply_changes('firewall') is called or apply=true is passed here.

NameTypeReqDescription
applyboolean
descrstring
destinationstring
dstport
interfacestringyes
ipprotocolstring
protocol
sourcestring
typestringyes

Structured output declared, but exposes no named fields.

No examples provided.

apply_changes ~74

Apply ALL staged changes of a subsystem ('firewall', 'dhcp' or 'dns'). Requires confirm=true. This reloads the subsystem, activating every pending change — including any a human staged in the pfSense WebGUI and has not reviewed yet.

NameTypeReqDescription
confirmboolean
subsystemstringyes

Structured output declared, but exposes no named fields.

No examples provided.

delete_dhcp_static_mapping ~105

Delete a DHCP static mapping. Requires confirm=true. `interface` is the mapping's DHCP server — the `parent_id` value returned by list_dhcp_static_mappings; `mapping_id` is its `id` there. Staged until apply_changes('dhcp') is called or apply=true is passed.

NameTypeReqDescription
applyboolean
confirmboolean
interfacestringyes
mapping_idintegeryes

Structured output declared, but exposes no named fields.

No examples provided.

delete_dns_host_override ~60

Delete a DNS host override by ID. Requires confirm=true. Staged until apply_changes('dns') is called or apply=true is passed.

NameTypeReqDescription
applyboolean
confirmboolean
override_idintegeryes

Structured output declared, but exposes no named fields.

No examples provided.

delete_firewall_rule ~71

Delete a firewall rule by its ID (the `id` from list_firewall_rules). Requires confirm=true. Staged until apply_changes('firewall') is called or apply=true is passed.

NameTypeReqDescription
applyboolean
confirmboolean
rule_idintegeryes

Structured output declared, but exposes no named fields.

No examples provided.

get_arp_table ~24

Get ARP table showing connected devices (IP, MAC, interface).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

get_gateway_status ~22

Get gateway status including latency, packet loss, and online state.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

get_interfaces ~17

List all network interfaces with status and configuration.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

get_pending_changes ~39

Check whether a subsystem ('firewall', 'dhcp' or 'dns') has staged, unapplied changes.

NameTypeReqDescription
subsystemstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_system_status ~26

Get pfSense system status including version, CPU, memory, uptime, and temperature.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_dhcp_leases ~26

List active DHCP leases showing IP, MAC, hostname, and lease times.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

list_dhcp_static_mappings ~59

List DHCP static mappings (IP reservations), optionally filtered by interface. Each mapping carries `parent_id` (its DHCP server / interface) — pass that as `interface` to delete_dhcp_static_mapping.

NameTypeReqDescription
interface
NameTypeReqDescription
resultarrayyes

No examples provided.

list_dns_host_overrides ~21

List DNS Resolver host overrides (local DNS entries).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

list_firewall_aliases ~24

List firewall aliases (IP groups, port groups, URL lists).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

list_firewall_rules ~24

List firewall rules, optionally filtered by interface.

NameTypeReqDescription
interface
NameTypeReqDescription
resultarrayyes

No examples provided.

list_services ~16

List all services and their running status.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

restart_service ~32

Restart a service by name. Requires confirm=true.

NameTypeReqDescription
confirmboolean
namestringyes

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the io.github.antonio-mello-ai/mcp-pfsense server?

io.github.antonio-mello-ai/mcp-pfsense is listed in the public MCP registry as io.github.antonio-mello-ai/mcp-pfsense. Manage pfSense firewalls through AI assistants, rules, DHCP, DNS, and more. This page covers its PyPI package (mcp-pfsense).

Is the io.github.antonio-mello-ai/mcp-pfsense server safe to use?

io.github.antonio-mello-ai/mcp-pfsense scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.antonio-mello-ai/mcp-pfsense server expose?

io.github.antonio-mello-ai/mcp-pfsense exposes 19 tools: get_system_status, get_interfaces, list_firewall_rules, add_firewall_rule, delete_firewall_rule, and 14 more. Their descriptions and schemas cost roughly 911 tokens of context every time the server is loaded.

Is the io.github.antonio-mello-ai/mcp-pfsense server still maintained?

io.github.antonio-mello-ai/mcp-pfsense is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.