Burp Suite for AI Agent
Related Servers
Alternatives to Burp Suite for AI Agent
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn MCP security toolkit that integrates Burp-style HTTP proxying, AI-driven vulnerability hunting, source code auditing, and reporting into AI coding agents, enabling authorized security testing of web applications and source code.24MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that lets AI assistants analyze Burp Suite XML exports offline, without running Burp. Provides 19 tools for mapping endpoints, finding secrets, detecting vulnerabilities, analyzing headers, exporting curl commands, and generating pentest reports.-
- AlicenseNot gradedqualityAmaintenanceExposes Burp Suite operations through a local authenticated HTTP server and an MCP stdio bridge, enabling tools like burp_proxy_history via MCP.03MIT
- AlicenseNot gradedqualityBmaintenanceEnables authorized bug bounty automation via a scope-enforced MCP bridge, supporting web, secrets, mobile, and LLM red-team scanning, with reporting and advisory.MIT
- AlicenseAqualityBmaintenanceMCP server for offensive-security tooling, enabling AI agents to run reconnaissance, CVE intelligence, JavaScript analysis, HTTP probing, and port scanning against authorized targets.10MIT
- FlicenseNot gradedqualityDmaintenanceA lightweight MCP server that wraps OWASP ZAP's REST API as Model Context Protocol tools, enabling AI agents to perform automated security scanning.-
TDQS
Scored across 11 tools
Each tool targets a distinct aspect of the Burp Suite integration: clearing, status, requests (list/detail), endpoints, tasks, issues (list/import), session snapshot, and outbound actions (send/status). Despite some related operations, the descriptions clearly differentiate them, leaving no ambiguity.
All tools follow a consistent 'burp_' prefix with snake_case names. Verbs and nouns are used predictably (e.g., burp_clear, burp_requests, burp_import_issue). There is no mixing of conventions, ensuring easy pattern recognition.
With 11 tools, the set is well-scoped for a Burp Suite bridge. It covers essential operations without being bloated or sparse. Each tool serves a clear purpose, and the count aligns with the expected complexity of security testing workflows.
The tool set covers the core workflow: connection status, request capture, endpoint discovery, task and issue management, import, session retrieval, and outbound actions. Minor gaps exist, such as the lack of detailed views for individual tasks or issues, but these do not critically hinder the primary use case.