get_scan
Get results of a previous middleBrick scan by its ID
LABSCO SUMMARY
Scans being retrievable by id is what turns a one-off check into something you can compare against later.
A security scan whose result exists only in the response is a snapshot nobody can cite. Storing them with ids means a finding can be referenced in a ticket, re-read after a fix, and compared against the next run — which is how scanning becomes a practice rather than an event. The surface is deliberately small. The important operational point is the obvious one: this actively probes an endpoint, so it belongs pointed at your own APIs or ones you have written permission to test.
What it is
A three-tool API security scanning client: run a scan against an endpoint, retrieve a past scan's results, and list what has been scanned before.
What you get
- scan_api scans an endpoint and returns findings with a risk score attached.
- get_scan retrieves a previous scan by its id, so results are addressable after the fact rather than only in the moment.
- list_scans returns the scan history, which is what makes a comparison over time possible.
Requirements
MIDDLEBRICK_API_KEY. Scanning an endpoint is an active test — run it against APIs you are authorised to test.
Setup effort
One command plus a key — npx -y @middlebrick/mcp-server, then supply credentials
USE CASES
01
Checking an endpoint before it ships
Scan it and read the findings with the risk score, on an API you are authorised to test.
02
Referring back to a finding
Retrieve the scan by id when the fix is being reviewed, rather than re-running and hoping it reproduces.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
list_scans
List previous middleBrick API security scans
scan_api
Scan an API endpoint for security vulnerabilities and get a risk score
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected.
Requires
- npx on PATH
- MIDDLEBRICK_API_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @middlebrick/mcp-serverMCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"middlebrick": {
"command": "npx",
"args": [
"-y",
"@middlebrick/mcp-server"
],
"env": {
"MIDDLEBRICK_API_KEY": "<YOUR_MIDDLEBRICK_API_KEY>"
}
}
}
}
