Firegex MCP Server
firegex-mcp
PyPI
v0.1.1
Published by umbra2728 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for Firegex — CTF regex/proxy firewall
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
Tools 49
Each tool and what it can reach — statically extracted from the published source.
add_nfproxy_serviceno sensitive capabilityadd_nfregex_serviceno sensitive capabilityadd_phj_serviceno sensitive capabilityadd_regexno sensitive capabilitychange_passwordno sensitive capabilitychange_phj_destinationno sensitive capabilitydelete_nfproxy_serviceno sensitive capabilitydelete_nfregex_serviceno sensitive capabilitydelete_phj_serviceno sensitive capabilitydelete_regexno sensitive capability
Show 39 more tools ↓
disable_firewallno sensitive capabilitydisable_pyfilterno sensitive capabilitydisable_regexno sensitive capabilityenable_firewallno sensitive capabilityenable_pyfilterno sensitive capabilityenable_regexno sensitive capabilityget_firegex_statusno sensitive capabilityget_firewall_settingsno sensitive capabilityget_nfproxy_serviceno sensitive capabilityget_nfregex_metricsno sensitive capabilityget_nfregex_serviceno sensitive capabilityget_phj_serviceno sensitive capabilityget_pyfilter_codeno sensitive capabilityget_regexno sensitive capabilitylist_firewall_rulesno sensitive capabilitylist_interfacesno sensitive capabilitylist_nfproxy_servicesno sensitive capabilitylist_nfregex_servicesno sensitive capabilitylist_phj_servicesno sensitive capabilitylist_pyfiltersno sensitive capabilitylist_regexesno sensitive capabilitylogin_probeno sensitive capabilityrename_nfproxy_serviceno sensitive capabilityrename_nfregex_serviceno sensitive capabilityrename_phj_serviceno sensitive capabilityreplace_firewall_rulesno sensitive capabilityreset_firegexno sensitive capabilityset_firewall_settingsno sensitive capabilityset_passwordno sensitive capabilityset_pyfilter_codeno sensitive capabilityset_pyfilter_code_from_fileno sensitive capabilitystart_nfproxy_serviceno sensitive capabilitystart_nfregex_serviceno sensitive capabilitystart_phj_serviceno sensitive capabilitystop_nfproxy_serviceno sensitive capabilitystop_nfregex_serviceno sensitive capabilitystop_phj_serviceno sensitive capabilityupdate_nfproxy_service_settingsno sensitive capabilityupdate_nfregex_service_settingsno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (49 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.1 latest |
A 99/100 | 0 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan firegex-mcp --online --registry pypiMore in Security & Testing
The Stripe Agent Toolkit enables popular agent frameworks including LangChain and Vercel's AI SDK to integrate with Stripe APIs through function calling.
MCP (Model Context Protocol) server for AgentGate. Enables Claude and other MCP-compatible AI assistants to request approvals.
Scan any website for AI agent readiness, payment protocols, and discovery endpoints
MCP server for aigently security guardrails — reads static catalog-data JSON, zero API dependency
Governed threat modeling, code threat verification, traceability & compliance, as MCP tools.
Governed threat modeling, code threat verification, traceability & compliance, as MCP tools.