Red-team-mcp

Created By
skjortan23a year ago
Overview

what is Red-team-mcp?

Red-team-mcp is a Model Context Protocol (MCP) server designed for AI agents to utilize during red teaming exercises, providing essential resources and tools for security testing.

how to use Red-team-mcp?

To use Red-team-mcp, set up the server with the required dependencies, including MongoDB and Metasploit, and then utilize the provided tools for scanning and vulnerability assessment.

key features of Red-team-mcp?

  • Integration with various scanning tools (masscan, nuclei, Metasploit)
  • Real-time exploit searching and execution capabilities
  • Modular architecture for easy extension and integration of new tools
  • Comprehensive logging and monitoring features

use cases of Red-team-mcp?

  1. Conducting security assessments and penetration testing using AI agents.
  2. Automating vulnerability scanning and exploit execution in red teaming scenarios.
  3. Facilitating the discovery of open ports and services on target networks.

FAQ from Red-team-mcp?

  • What tools are required to run Red-team-mcp?

You need MongoDB, Metasploit Framework, and Python dependencies to set up the server.

  • Can I extend the server with new tools?

Yes! The server is designed to be modular, allowing for easy integration of additional tools and resources.

  • Is there a user guide available?

Yes, detailed setup and usage instructions are provided in the project documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
skjortan23
Star
2
Language
Python
License
-
Category
security

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago