Model Context Provider (MCP) for Penetration Testing

Created By
allsmoga year ago
An MCP server for pentesting. Contributors wanted!
Overview

What is Model Context Provider (MCP) for Penetration Testing?

MCP is an AI-driven middleware designed to assist penetration testers by integrating various pentesting tools and guiding users through the testing process.

How to use MCP?

To use MCP, clone the repository, build the Docker containers, and start the services. You can create engagements and run tasks via API calls.

Key features of MCP?

  • Methodology enforcement for structured testing phases.
  • Real-time context aggregation from multiple tools.
  • LLM-powered insights for interpreting findings.
  • Seamless integration with major pentesting tools.
  • Secure data handling and reporting capabilities.

Use cases of MCP?

  1. Streamlining penetration testing engagements.
  2. Enhancing collaboration among security teams.
  3. Providing AI-driven insights during testing phases.

FAQ from MCP?

  • Is MCP suitable for all types of penetration testing?

Yes, MCP is designed for various penetration testing scenarios, provided they are conducted legally and ethically.

  • How can I contribute to MCP?

Contributions are welcome! Check the CONTRIBUTING.md file for details on how to get involved.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
allsmog
Star
0
Language
Python
License
MIT license

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