/ 100

4 days ago

glama

pfClaude

Enables bidirectional control and monitoring of pfSense firewalls through Claude, with full API access for configuration and diagnostics, plus autonomous emergency response capabilities when network connectivity is lost.

→ ArkTechNWA/pfsense-mcp · listed on glama

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

Glama

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

// key findings

⚠️

Known vulnerabilities in dependencies: 2 high

Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.

✅

No credential exfiltration, no sensitive file access, no obfuscation

Static analysis found nothing flowing your secrets to unexpected places.

✅

Open source with a license and README

Anyone can audit the code, the license is declared, and the publisher documents what it does.

🔐

You'll be asked for 7 credentials: GUARDIAN_ADMIN_KEY, PFSENSE_API_KEY, PFSENSE_DEVICE_TOKEN, PFSENSE_PASSWORD, RELAY_ADMIN_KEY, RELAY_SECRET, SMTP_PASS

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// known CVEs in dependencies2 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.0.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.0.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →

// required environment variables

This server reads these from process.env. You'll be asked to provide them before it can run.

🔐 secretGUARDIAN_ADMIN_KEY

configGUARDIAN_RELAY_URL

configHOST

🔐 secretPFSENSE_API_KEY— "": "your-api-key"

🔐 secretPFSENSE_DEVICE_TOKEN

configPFSENSE_HOST— "": "192.168.1.1",

🔐 secretPFSENSE_PASSWORD

configPFSENSE_PORT

configPFSENSE_USERNAME

configPFSENSE_USE_RELAY_CACHE

configPFSENSE_VERIFY_SSL

configPORT

🔐 secretRELAY_ADMIN_KEY

configRELAY_DB_DIR

configRELAY_DOMAIN

🔐 secretRELAY_SECRET

configSMTP_FROM

configSMTP_HOST

🔐 secretSMTP_PASS— "password_env": "",

configSMTP_PORT

configSMTP_USER— "username_env": "",

configXDG_CACHE_HOME

// 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 3 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/arktechnwa-pfsense-mcp-efx37q)](https://m8ven.ai/mcp/arktechnwa-pfsense-mcp-efx37q)

commit: 0678d2ed70a30f3b795909bce6bca5094946fac9

code hash: b7b96accef3923e4aa5e0ee4db21cf241a0410a01a580bfde56b4f4aa85ecf1e

verified: 7/9/2026, 10:19:15 AM

view raw JSON →