Open-source tools for people who run firewalls — self-hosted, offline-capable, no mandatory SaaS. Deterministic engines decide, models explain, and a human approves.
Deterministic decides. The model explains. A human approves.
This supervised agent session used read-only MCP connections to the labs to produce an anonymous point-in-time candidate. Deterministic validation rejects candidates containing names, addresses, or identifiers; it never receives raw identifiers or removes them. The website never connects to the private lab.
"Sovereign" is not a slogan here — it is a design constraint every mechub tool is built against.
MIT licensed. Read the code before you point it at a firewall — we would. Every repo is public from the first commit.
Where AI is used at all, it runs locally and only phrases and assists. Detection logic and device changes stay deterministic — an LLM never makes a safety-relevant decision on its own.
Everything below is early. It works in our lab against real gear; we need it to work in yours. Stats refresh live from GitHub when you're online. Hover over or tab to a card and the repos it depends on, plus the ones built on it, light up with it.
Core libraries that power the MCP server ecosystem. (3 repos)
The shared Rust foundation under mechub's per-vendor firewall mcp servers — bearer-token auth, scopes, attribution and audit, transport hardening, and change control, written once instead of once per vendor.
Async NETCONF client library for Rust — YANG code generation, vendor profiles, connection pooling, and a Terraform-like CLI for declarative network config.
A Rust replacement for Juniper PyEZ — async-first Junos device automation built on rustnetconf.
Enterprise MCP servers for vendor platforms, built on the mecmcp foundation. (8 repos)
MCP server that lets AI agents operate Juniper Junos devices — built on rustez, exercised daily against a 24-device vSRX lab.
MCP server that lets AI agents operate Palo Alto PAN-OS firewalls — bearer-token device and tool scopes, a guarded candidate-config lifecycle with independent approval, and the same security posture as rustjunosmcp.
Async mcp server for HPE Juniper Security Director Cloud — bounded read tools for discovery, and a prepare/approve/apply path for policy deployment instead of a direct deploy call.
Async mcp server for the HPE Juniper Mist cloud — bearer-token auth, org- and site-scoped tools, bounded responses, and guarded WAN-edge change control.
MCP server for Proxmox VE — one endpoint across many clusters, with destructive work held behind plan, approve and apply.
The UniFi Network member of the family — a curated, scoped, audited mcp surface over the controller API, the same shape rustjunosmcp gives Junos.
Enterprise MCP server for Fortinet FortiGate (then FortiManager) on the mecmcp foundation — scoped access, audited change control.
Enterprise MCP server for OPNsense on the mecmcp foundation — scoped access, audited change control.
Security data platforms with MCP-first architecture. (1 repo)
Sovereign Security Data Fabric — a deliberately minimal security data platform where the mcp tool surface is the product, not an afterthought. Vendor syslog normalised through Vector into ClickHouse, self-hosted end to end, with swappable model and storage backends.
Agent skills, config conversion, sanitization, and sync utilities. (4 repos)
Agent skills for firewall work — parsing, auditing, and converting configs across Cisco, Fortinet, Palo Alto, and Juniper. Works with Claude Code, Codex, and Hermes so far.
Browser-based conversion of firewall and cloud configs — PAN-OS, FortiGate, Cisco ASA/FTD, Check Point, AWS/Azure/GCP, and more — into reviewable Juniper SRX output, with an LLM-guided greenfield mode. Always a migration draft requiring review — never production-ready.
Strips private data — addresses, hostnames, secrets — out of a firewall configuration so it can be shared for help or review.
Pushes one SRX's config — policies, objects, NAT — out to a fleet of others, so a golden device can drive the rest.
Network-automation agent benchmarking and evaluation. (1 repo)
Tool-call benchmark corpus and runner for network-automation agents — drives scenarios through local models and scores emitted tool-call sequences.
Proof ahead of claims. Here is exactly what these tools are today — and what they are not yet.
Everything public here is developed and used in one real lab: a Proxmox cluster running a 24-device Juniper vSRX topology, exercised through real NETCONF sessions, real commits, and real multi-vendor configs.
No mechub tool has been proven at someone else's site. That is precisely the help we are asking for — see below.
Until a 1.0, expect breaking changes; they'll be called out in release notes, not hidden.
Deterministic code decides, models explain, a human approves. That rule does not change as the tools mature.
These are goals in active development — not promises. Scope and timing may change; when something ships, it ships on GitHub first and gets announced here.
The single most valuable thing you can do is run a tool against your own gear and tell us what happened — especially when the answer is "it broke".
Personal side projects built with the same tooling — not part of the security stack, just things we like having around.
agentofcomply is in active development and not yet public. Watch github.com/mechubsec for the release announcement.