Overview

Run profile-based scans on your own machines, with REST and optional MCP.

Burp Bounty Server runs profile-based web scanning outside Burp Suite. Install it on a workstation, server or VPS and control it through the REST API, Burp Bounty Pro or an MCP-capable agent.

How it fits together

Interfaces

Interface	Availability	Profile input
REST	Always enabled on the main HTTP listener	Uploaded .bb profiles and exchanges.
Pro's Server Scanner	REST client built into Pro	Pro uploads the enabled selection.
MCP	Add --mcp; endpoint /mcp on the same listener	Catalogue names/tags or supplied profile JSON.
Metrics	Separate monitoring listener, loopback port 8082 by default	No scan submission.

The service does not provide a browser-based scan dashboard. Its MCP is Streamable HTTP, not a legacy SSE-only endpoint or a STDIO process. Streamable HTTP can use SSE responses internally; select HTTP in a client that offers stdio/http/sse.

Independent workers

Multiple installations have separate catalogues, scan IDs, budgets and retained history. Pro distributes a submitted batch; an agent can explicitly divide work across its MCP connections. There is no automatic server-to-server scheduler, shared history or live scan migration.

What it retains

When requested, Server keeps compact scan metadata, finding summaries and bounded finding evidence. It does not persist a replayable queue of every probe. See results and retention.

For existing deployments, jump to Pro integration or the REST reference.

Keep exploring

Start the server

Choose a binary, configure licensing and verify access.

Connect an agent

Configure the HTTP endpoint and discover profiles.