SkillAgentSearch skills...

RedVector

RedVector AI - AI-powered penetration testing and cybersecurity automation framework for security researchers and ethical hackers.

Install / Use

claude mcp add 0x7AK7 -- npx -y github:0x7AK7/RedVector

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

78/100

Category

Security

Supported Platforms

Claude Code
Claude Desktop

Our assessment of RedVector

RedVector scores 78/100 on our quality scale, 1016th of 1,108 Security skills we index.

Its MCP Server is 42 KB long, well organised into 43 sections with 16 code examples: long enough that it reads more like full documentation than a focused instruction file, which agents can find harder to follow.

It has 47 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
21/30
Structure
20/20
Description
15/15
Adoption
7/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 5 days ago, so RedVector is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 85/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-16. Automated pattern scan on 2026-11-15. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

RedVector compared with similar skills

All 4 of these similar skills score higher than RedVector; compare them before choosing.

SkillScoreStarsUpdatedFormat
RedVector (this skill)by 0x7AK778475d agoMCP Server
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
CowAgentby zhayujie10048.0ktodayCLAUDE.md

Frequently asked questions

How do I install RedVector?
Run claude mcp add 0x7AK7 -- npx -y github:0x7AK7/RedVector. The install tabs above show the steps for each supported agent.
Which AI agents does RedVector work with?
It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
Is RedVector safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 85/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is RedVector still maintained?
The repository was last updated 5 days ago, so RedVector is actively maintained.
<div align="center"> <img src="assets/Redvector-logo4.png" alt="RedVector Logo" width="360"/>

RedVector AI v8.0

Official Website

https://0x7ak7.github.io/RedVector/

AI-Assisted Cybersecurity Automation, Penetration Testing and Red Team Orchestration

Python License MCP REST API Security

Developed and maintained by Adam Karim

RedVector connects MCP-compatible AI clients with a large collection of real cybersecurity tools through a Python MCP layer and a Flask execution backend.

Overview • Architecture • Installation • Security Tools • AI Systems • Workflow • MCP Tools • License

</div>

Overview

RedVector AI is an AI-assisted cybersecurity automation platform for authorized penetration testing, red-team exercises, vulnerability research, CTFs, labs, defensive validation, digital forensics, reverse engineering, cloud and container assessment, Active Directory testing, web and API security, and security-tool orchestration.

The supplied source tree registers 328 MCP tools in redvector_mcp.py and 331 Flask routes in redvector_server.py. The MCP layer exposes structured capabilities to compatible AI clients. The Flask backend performs validation, process execution, orchestration, result collection, caching, recovery, telemetry, reporting, and access to the underlying security tools installed on the host.

RedVector does not magically bundle every third-party executable. A wrapper may exist even when the corresponding tool is not installed. Kali Linux provides the broadest out-of-the-box coverage, while Ubuntu, Debian and other supported environments can also be used with the required tools installed separately.

Authorized use only. Use RedVector only on systems you own or have explicit permission to assess.


Architecture

graph TD
    A[AI Client / MCP-Compatible Agent] -->|MCP stdio| B[redvector_mcp.py]
    B -->|HTTP / REST| C[redvector_server.py]
    C --> D[Intelligent Decision and Workflow Layer]
    C --> E[Process, Cache, Recovery and Telemetry]
    C --> F[Security Tool Integrations]
    F --> G[Recon and Network]
    F --> H[Web, API and Authentication]
    F --> I[Active Directory and Windows]
    F --> J[Cloud, Container and IaC]
    F --> K[Binary, Forensics and CTF]
    D --> L[Structured Results and Reports]
    E --> L
    G --> L
    H --> L
    I --> L
    J --> L
    K --> L

Main runtime files

| File | Role | |---|---| | redvector_server.py | Flask backend, orchestration, security-tool execution, autonomous workflows, process management and reporting | | redvector_mcp.py | FastMCP interface exposing RedVector capabilities to AI clients | | redvector_tool_manager.py | Runtime tool registry and manager backing RedVector's MCP tool surface | | redvector-mcp.json | Example MCP configuration | | start_redvector.sh | Linux launcher, verifies backend ownership, starts backend on demand and runs MCP client | | redvector_banner.py | Shared original terminal banner and startup panel; also performs the Linux socket/process ownership backend identity check via --backend-check (migrated from the removed redvector_backend_check.py); never starts the backend | | redvector_ai_desktop_manager.sh | Primary Claude Desktop installer and MCP manager (install, configure, check, start and update Claude Desktop with RedVector MCP) | | start_redvector.ps1 | Windows PowerShell launcher | | requirements.txt | Python dependencies |


How RedVector Works

  1. Start the RedVector backend. The Flask service normally binds to 127.0.0.1:8888.
  2. Connect an MCP-compatible AI client. The client launches or connects to redvector_mcp.py.
  3. Submit an authorized task. The AI selects a RedVector MCP capability based on the operator's request.
  4. RedVector validates parameters and scope. Requests are normalized before execution.
  5. The backend invokes the selected integration. The corresponding security tool runs on the RedVector host.
  6. Process and recovery systems monitor execution. Long-running jobs can be cached, monitored, retried, paused, resumed, or terminated where supported.
  7. Results are normalized. Tool output is returned through the Flask API to the MCP layer.
  8. The AI interprets the result. The client can explain findings, select a follow-up workflow, generate a report, or call another RedVector capability.

Typical assessment workflow

Authorized target
      |
      v
Reconnaissance and OSINT
      |
      v
Service and technology identification
      |
      v
Vulnerability discovery and correlation
      |
      v
Validation / exploit research
      |
      v
Controlled exploitation where explicitly authorized
      |
      v
Post-exploitation / privilege escalation / lateral movement where in scope
      |
      v
Evidence, reporting and remediation guidance

RedVector also contains specialized workflow managers and autonomous engines for CTF, bug bounty, Active Directory, web vulnerability chaining, cloud assessment, CCTV assessment, exploitation research, privilege escalation, persistence, lateral movement, data exfiltration simulation, fuzzing and related red-team workflows.


Installation

Kali Linux / Linux

Clone RedVector and install its Python dependencies:

git clone https://github.com/0x7AK7/RedVector.git
cd RedVector
python3 -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
pip install -r requirements.txt

Choose how to run RedVector:

  • Claude Desktop integration (recommended for desktop users): Follow Claude Desktop automatic setup below. Do not start start_redvector.sh separately when Claude Desktop is configured to launch it.
  • Standalone or another MCP client: Run bash start_redvector.sh in a dedicated terminal. This starts the backend if necessary and launches the MCP client using stdio. For a backend-only session, see below.

Or start the backend directly:

python redvector_server.py

AI Desktop Manager (Claude Desktop)

redvector_ai_desktop_manager.sh is a menu-driven manager that installs and manages Claude Desktop with its RedVector MCP integration. Run it after cloning and installing the Python dependencies above:

chmod +x redvector_ai_desktop_manager.sh
./redvector_ai_desktop_manager.sh
REDVECTOR  —  AI DESKTOP MANAGER

  [1] Claude Desktop    Install Claude and register the RedVector MCP server
  [0] Exit
  • Claude Desktop — installs from the verified official APT repository (signing-key fingerprint checked) and registers RedVector as an MCP server by launching start_redvector.sh. Existing MCP servers and any existing RedVector environment variables are preserved, a timestamped backup is written, and the configuration is updated atomically.

Run the manager as your normal desktop user (it uses sudo only for package steps). Use --status for a non-interactive summary and --help for usage. This manager is an optional convenience; the manual Claude Desktop setup below remains fully supported.

Claude Desktop automatic setup (Kali Linux)

Claude Desktop on Linux is currently a beta release. Kali Linux is Debian-based, but it is not among Anthropic's officially tested distributions. An x86_64 or arm64 Debian-based desktop is required. If you use Kali through WSL2, Anthropic recommends installing Claude Desktop on Windows and running sessions in WSL rather than installing the Linux desktop app inside WSL.

One-time setup: use the AI Desktop Manager described above (./redvector_ai_desktop_manager.sh). Choose Install Claude Desktop, then Configure RedVector MCP. The manager creates or updates ~/.config/Claude/claude_desktop_config.json, backs up an existing configuration, and preserves other MCP server entries. The generated redvector-ai entry launches start_redvector.sh using an absolute path. Use your existing API token configuration when applicable; avoid publishing secrets in Git.

Everyday use, after fully quitting and restarting Claude Desktop once to load the configuration:

claude-desktop

Claude Desktop is expected to launch RedVector's start_redvector.sh automatically through MCP. The launcher resolves its own installation directory (including symbolic links), uses that project's .venv Python when available, and verifies the listening process through Linux /proc before reusing a backend. It checks http://127.0.0.1:8888/health, starts the RedVector backend when the port is free, and runs redvector_mcp.py via stdio. A foreign process or unverifiable owner causes a clear error; no process is stopped automatically. You normally do not need to execute start_redvector.sh manually. The backend may remain running after Claude Desktop closes because the launcher detaches it.

The MCP client obtains tool availability from /health/details, including the essential count (for example, 8/8). Missing or invalid availability fields are reported as Unknown. Launcher and MCP diagnostics go to stderr; backend output goes to server.log, keeping MCP stdout reserved for the protocol. If ownership cannot be read (for example, restricted /proc access or a different user), run the backend under the same user with visible process metadata or resolve the port conflict manually.

When run manually with bash start_redvector.sh from an interactive terminal, the launcher also displays the original red logo and startup panel on stderr, including when it reuses this installation's running backend. The server and launcher share the same renderer; displaying the banner does not start another server. The MCP tool count is read from the current registrations. Claude Desktop's piped MCP launch suppresses the banner and keeps stdout exclusively for the protocol.

Verify the connection: Open Claude Desktop → Settings → Developer → Local MCP servers and check that redvector-ai is running. In a Claude chat, request a read-only server_health check. Do not assume a reported scan was executed unless the corresponding MCP tool call and output are visible.

If redvector-ai shows Failed:

curl -fsS http://127.0.0.1:8888/health
cat ~/.config/Claude/claude_desktop_config.json
ls -lah ~/.config/Claude/logs/

Inspect the redvector-ai log through View logs in Claude Desktop. Ensure the configured project path exists and start_redvector.sh is present. Avoid sharing API tokens when pasting configuration or logs publicly.

This setup is for Claude Desktop. Claude Code launched independently with the claude terminal command may require separate MCP registration.

Windows PowerShell

git clone https://github.com/0x7AK7/RedVector.git
cd RedVector
python -m venv .venv
.\.venv\Scripts\Activate.ps1
python -m pip install --upgrade pip
pip install -r requirements.txt
.\start_redvector.ps1

Verify the backend

curl http://127.0.0.1:8888/health

Configuration

Common environment variables used by the project include:

| Variable | Purpose | |---|---| | REDVECTOR_HOST / HOST | Backend bind address, depending on launcher/runtime path | | REDVECTOR_PORT / PORT | Backend port | | REDVECTOR_API_TOKEN | Bearer token used to protect API access | | `REDVECTO

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars47
CategorySecurity
Updated5d ago
Forks14

Languages

Python

Trust signals

85/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 info