MCP Server Pentest

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MCP Server Pentest?

MCP Server Pentest is a security testing tool designed to automatically detect vulnerabilities such as XSS and SQL injection in web applications.

how to use MCP Server Pentest?

To use MCP Server Pentest, install the necessary dependencies using the provided commands, configure the tool, and then run tests against your target URLs to identify vulnerabilities.

key features of MCP Server Pentest?

  • Automatic detection of XSS and SQL injection vulnerabilities
  • Ability to take screenshots of web pages or specific elements
  • Comprehensive network interaction capabilities including navigation and form filling
  • Monitoring of console logs and execution of JavaScript in the browser context

use cases of MCP Server Pentest?

  1. Conducting security assessments on web applications to identify vulnerabilities.
  2. Automating the testing process for web application security.
  3. Generating reports on security findings for developers and stakeholders.

FAQ from MCP Server Pentest?

  • What types of vulnerabilities can MCP Server Pentest detect?

MCP Server Pentest can detect XSS and SQL injection vulnerabilities among others.

  • Is MCP Server Pentest easy to set up?

Yes! The installation process is straightforward and includes configuration steps.

  • Can I use MCP Server Pentest for any web application?

Yes! MCP Server Pentest can be used on any web application that you have permission to test.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
MIT 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