BreachSpider for developers
Check devices against known vulnerabilities from your own code
Send a vendor, a product and a version for each device. BreachSpider returns the CVEs that affect that exact version, ranked, with known-exploited flags, the fix where one is known, and links to the vendor advisories.
14 days, no card, no sales call.
The device API
correlate-cves
Resolves each device to a catalog product and returns the CVEs that affect its version. Every result says how it matched, how confident the resolution is, and what to do next.
correlate-cves/check
A cheap staleness check. Send the result hash you stored last time and learn which devices have new findings, without pulling every CVE again.
CVE detail
Look up any CVE by ID for the full record: scores, known-exploited status, affected versions, fixes and references.
- Deterministic matching. The same input gives the same answer. Matching and ranking use no AI.
- Built for OT and ICS. Version ranges from NVD plus vendor and CISA advisories for industrial vendors such as Siemens, Rockwell, Schneider, ABB and Moxa.
- Your devices stay yours. We count how many devices you check. We do not store the devices you submit.
POST /api/v1/assets/correlate-cves
Authorization: Bearer bs_live_...
{"assets": [
{"asset_id": "plc-7", "vendor": "Siemens",
"product": "SIMATIC S7-1500", "version": "2.8"}
]}
MCP server
A local, read only MCP server lets AI agents such as Claude Code, Claude Desktop and Cursor check devices and look up CVEs through the same API and the same trial key. Without a key it runs in demo mode on public examples.
1. Install pipx, then open a new terminal:
# macOS brew install pipx && pipx ensurepath # Debian / Ubuntu sudo apt install pipx && pipx ensurepath # Windows (PowerShell) py -m pip install --user pipx; py -m pipx ensurepath
2. Install the server:
pipx install breachspider-mcp
3. Add it to Claude Code, with your trial key in BREACHSPIDER_API_KEY:
claude mcp add breachspider -e BREACHSPIDER_API_KEY="$BREACHSPIDER_API_KEY" -- breachspider-mcp
Claude Code stores the key, and claude mcp get breachspider prints it, so don't run that while sharing your screen. Setup for Claude Desktop and Cursor, and running with uvx instead, are in the README.
- MCP server on GitHub: setup for every client, tools and privacy
- Python SDK on GitHub
- API docs
The free trial
A device sent to correlate-cves counts as one check. A device sent to the staleness check counts as a tenth of a check. The trial key is read only and stops working when the trial ends. One trial per organization.
When the trial ends, the API says so plainly and never returns a partial result without telling you. To keep going, we scope an agreement to your devices and your use.
Docs and SDK
- Quick start: your first call in a few minutes
- Correlate CVEs reference: request, response and ranking
- Windows Patch Level API: check Windows hosts against Microsoft's own patch data
- MCP server docs: tools, setup and privacy
- API keys and error codes
- Python SDK on GitHub
