A
licenseA
qualityB
maintenanceMCP server for offensive-security tooling, enabling AI agents to run reconnaissance, CVE intelligence, JavaScript analysis, HTTP probing, and port scanning against authorized targets.
10
MIT
frx-director-mcp
Related Servers
Alternatives to frx-director-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceLocal MCP server that enables delegating low-risk tasks like summarization or code patches to a low-cost model, with the main agent reviewing results.2-
- FlicenseBqualityBmaintenanceMCP server that enables AI agents to drive your real, logged-in browser via accessibility snapshots, with hardened credential brokering and local workflow memory.5341 npm-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to expose and control local and self-hosted tools via MCP, with isolated workers, long-running task management, persisted state, and modular integrations for reverse engineering and development workflows.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables delegation of small coding implementations to a cheaper language model with propose_patch and apply_patch tools, while the primary agent retains architecture, review, and approval.MIT
- FlicenseNot gradedqualityDmaintenanceA local, privacy-first MCP server that orchestrates Ghidra, Binary Ninja, x64dbg, and system tools to provide AI assistants with powerful binary analysis capabilities.-
TDQS
B3.4/5.0
Scored across 23 tools
Disambiguation4/5
The agent_* family has mild overlap: agent_read, agent_read_brief, and agent_state all read worker state, and agent_wait_for_stop vs agent_poll both wait for settle. However, descriptions clearly differentiate them (full vs brief vs cheap snapshot; long blocking vs short CLI polling), so misselection risk is low. Env tools (create/open/close/rename/delete/list/current/import_json/import_capture) each target a distinct action.
Naming Consistency4/5
All names use snake_case with clear verb_noun patterns. There are three prefix families (frx_env_*, frx_*, agent_*) reflecting different subsystems, with frx_status and frx_page_automation_scan being minor deviations from frx_env_*. Within each group the convention is consistent and readable.
Tool Count4/5
23 tools is on the heavy side (the 16-25 band), but the server genuinely spans two subsystems: browser environment lifecycle management and director/worker agent orchestration. Each area justifies roughly ten tools, so the count is defensible rather than padded.
Completeness4/5
Env lifecycle is well covered (create/open/close/rename/delete/list/current plus two import paths), and the worker orchestration surface (start/send/stop/poll/wait/read/state/runlog/set_mode/tools/call_tool) supports the full director loop. Minor gaps: no env settings update beyond rename/import, and no browser launch control (deliberately external).
Maintenance
ActivityMaintained
ResponsivenessSlow