MCP Server Pentest

What is MCP Server Pentest?

MCP Server Pentest is a server that integrates browser automation with security testing, enabling automated detection of XSS and SQL injection vulnerabilities in URLs. It also provides full browser control for navigation, screenshots, click interactions, and JavaScript execution, targeting developers and security testers who need to automate web security checks.

How to use MCP Server Pentest?

Install by running npx playwright install firefox, yarn install, and npm run build. Then add the provided JSON configuration block to your Claude config file, pointing to the built dist/index.js. Use the exposed tools (e.g., broser_url_reflected_xss, browser_url_sql_injection) by passing a URL and parameter name as arguments.

Key features of MCP Server Pentest

• Automatic XSS vulnerability detection in URLs
• Automatic SQL injection vulnerability detection in URLs
• Full-page or element-specific screenshot capture
• Browser navigation, clicking, form filling, and text selection
• Console log monitoring and JavaScript execution in browser context

Use cases of MCP Server Pentest

• Automatically test a web application’s URL parameters for reflected XSS
• Scan form inputs or query strings for SQL injection flaws
• Take screenshots of vulnerable pages for reporting
• Fill and submit forms to test login or search endpoints
• Execute custom JavaScript to extract runtime page data

FAQ from MCP Server Pentest

What runtime dependencies are required?

The server requires Node.js, the Playwright package, and a Firefox browser (installed via npx playwright install firefox). It runs as a command-line MCP server.

Which browsers are supported?

Firefox is explicitly installed and used; the README does not mention Chrome or other browsers.

Can it interact with dynamic content?

Yes – tools for clicking, hovering, filling inputs, and selecting dropdown options are available, along with JavaScript evaluation in the browser context.

Where are screenshots saved?

The README does not specify a default save location; screenshots are likely stored in the working directory or must be explicitly named via the name parameter in browser_screenshot.