Register a server
Open MCP Servers → Add server and describe how to reach it:Name·Description(optional)Transport— how the server speaks (see Transports below)Endpoint— the command or URL for the chosen transport.- Optionally link it to an Application, Repository, or Container for cross-tier context.
Transports
Authenticated remote servers are coming. Today you can point BreachLens at a local (STDIO) server or an unauthenticated HTTP / SSE / WebSocket endpoint; per-server bearer-token auth isn’t configurable yet. If you need to test a token-protected MCP server, tell us.
Run a scan
1
Open the server
Go to MCP Servers and click the registered server.
2
Run the scan
Click Run scan. BreachLens opens the transport, completes the MCP handshake, enumerates the exposed tools, and runs the probe suite against them. If the handshake fails, you get a clear connectivity finding instead of a silent miss.
3
Review findings
Each probe can emit zero, one, or more findings, each classified by its BreachLens MCP threat class.
Some probes (prompt injection, tool poisoning, indirect injection) are LLM-judged — they reuse the same judge model as AI-agent scans. With no AI provider configured they simply skip; the heuristic probes still run, so a scan always produces a result.
Next steps
Red-team an AI agent
Probe the agents that consume these MCP servers for prompt injection and more.
Fit it into your pipeline
Where AI and MCP testing sit alongside the rest of your security pipeline.