Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Follow Burp and proxy-tool compatibility because security-tool actions change
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
AI-assisted web security testing in Burp Suite
What we know
Official Burp Suite extension that connects Burp to MCP clients over SSE or a packaged stdio proxy.
Maintenance / activity evidence
- Observed (UTC)Preserve valid JSON when truncating history items ( 115)
Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.
Verification gaps / watch-outs
- Installation and comprehensive security have not been independently audited.
- Can interact with Burp project/session according to extension capabilities. Writes: Security-testing actions may alter requests/targets depending on Burp configuration.
- Not fully documented.
- Sensitive access: Captured traffic, Tokens, Vulnerability data
- A security-testing bridge can expose sensitive intercepted traffic and high-impact testing actions.
Full authority, access and evidence limits are available in Review context and Access & risk.
Popularity
1,216 repository stars
Stars observed Oct 6, 2026.
No canonical package metric applied.
No canonical package metric applied.
No canonical package metric applied.
All limitations / Review context
Which Burp operations and approval boundaries remain documented for MCP?
The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.
- A security-testing bridge can expose sensitive intercepted traffic and high-impact testing actions.
- Can interact with Burp project/session according to extension capabilities.
- Not fully documented.
- Captured web traffic/findings can be exposed to the connected client.
- Reviewed write actions: Security-testing actions may alter requests/targets depending on Burp configuration
- Sensitive access: Captured traffic, Tokens, Vulnerability data
- Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
- A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
- No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
- The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
- Exact authentication
- Full tool/permission matrix
- Pricing
- Requires Burp Suite.
- Exact MCP permission/auth surface is not fully enumerated in README.
Original activity observations
- 2026-08-12T09:44:06Z: Preserve valid JSON when truncating history items ( 115)
Technical identity
github.com/portswigger/mcp-server- Exact implementation source
- https://github.com/portswigger/mcp-server ↗
- Reviewed resource type
- Testing / Debugging
- Repository identity
- PortSwigger/mcp-server
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- GitHub repository ↗
portswigger/mcp-server
Recorded repository material and project history.
Includes references whose attribution is not established.
Setup · Watchlist
Testing / Debugging setup
Publisher instructions.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Install / connect
Publisher instructionsInstall Burp MCP extension in Burp Suite; verify Java and jar for building extension, or use publisher release. Do not confuse Burp extension with a standalone npm server.
publisher setup or prerequisite · Publisher instructions
java --versionpublisher setup or prerequisite · Publisher instructions
jar --versionConfigure / authenticate
MCP100 setup guideBurp Suite > Extensions: install PortSwigger MCP extension and enable its MCP tab listener. For Claude Desktop use the extension built-in client/proxy installer; for compatible clients connect to the extension SSE endpoint, respecting the configured local port. Restart client after registration.
Previously reviewed prerequisites / client guidance: Leave config-editing tools disabled unless specifically needed.
Check connection
Suggested checkBurp MCP tab listener enabled, server entry present in client, and tools/list succeeds from the client. JAR version checks are build prerequisites, not connection proof.
Remove / uninstall / revoke
Suggested checkIn Burp Suite open Extensions > Installed and unload/remove the MCP Server extension. Remove the Burp MCP entry that its built-in Claude Desktop installer registered, then restart Claude Desktop. If the Java stdio proxy was extracted, delete that proxy only after disconnecting it.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.
What it does
Official Burp Suite extension that connects Burp to MCP clients over SSE or a packaged stdio proxy.
- Capability
- Security & Testing
- Resource type
- Testing / Debugging
- Industry
- Cybersecurity
- Best fit
- AI-assisted web security testing in Burp Suite
Representative uses
- Install/configure the Burp extension
- Connect AI clients
- Use Burp project/session data through MCP
Limitations
- Requires Burp Suite.
- Exact MCP permission/auth surface is not fully enumerated in README.
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- Not fully documented.
- Permissions
- Can interact with Burp project/session according to extension capabilities.
- Data handling
- Captured web traffic/findings can be exposed to the connected client.
- Cost
- unknown
- Risk and cautions
- A security-testing bridge can expose sensitive intercepted traffic and high-impact testing actions.
Access scope and cautions
- Write actions
- Security-testing actions may alter requests/targets depending on Burp configuration
- Sensitive access
- Captured traffic Tokens Vulnerability data
- Risk level
- high
FAQ
Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.
Which implementation does this page cover?
What setup and authentication are documented?
Can it modify data or perform write operations?
What data-handling boundary should I consider?
What limitations and risks should I check before use?
Is this an official MCP?
PortSwigger is listed as First-party MCP in MCP100’s current evidence.