PentestAgentMCP

Created By
ibrahimsaleema year ago
Repository for creating an automatic pentesting agent using MCP servers.
Overview

what is PentestAgentMCP?

PentestAgentMCP is a repository designed for creating an automatic penetration testing agent utilizing MCP servers.

how to use PentestAgentMCP?

To use PentestAgentMCP, clone the repository from GitHub and follow the setup instructions provided in the documentation to configure the agent for your specific pentesting needs.

key features of PentestAgentMCP?

  • Automated penetration testing capabilities
  • Integration with MCP servers for enhanced testing
  • Customizable configurations for various testing scenarios

use cases of PentestAgentMCP?

  1. Conducting automated security assessments on web applications.
  2. Testing network security configurations using automated scripts.
  3. Streamlining the penetration testing process for security professionals.

FAQ from PentestAgentMCP?

  • What is the purpose of PentestAgentMCP?

PentestAgentMCP aims to automate the penetration testing process, making it easier for security professionals to identify vulnerabilities.

  • Is PentestAgentMCP free to use?

Yes! PentestAgentMCP is open-source and available for free on GitHub.

  • Can I customize the testing parameters?

Yes! The repository allows for extensive customization to fit various testing requirements.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ibrahimsaleem
Star
0
Language
-
License
-
Category
security

Recommend Servers

View All
Gpt Scrambler

2 days ago
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